Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backends able to receive OTLP profile signals #287

Open
christophe-kamphaus-jemmic opened this issue Dec 27, 2024 · 2 comments
Open

Backends able to receive OTLP profile signals #287

christophe-kamphaus-jemmic opened this issue Dec 27, 2024 · 2 comments

Comments

@christophe-kamphaus-jemmic

Which backends are able to receive the OTLP profile signals?

I know that the opentelemetry-collector is able to receive it, but where can it forward it for storage and analysis?

@JLowe-N
Copy link

JLowe-N commented Jan 3, 2025

I have been able to forward it to Grafana Pyroscope.
image
Although I have not had much luck with getting Python symbols.

Currently I have a Debian Bookworm application container running many Python services, among other things.
This is running on an Azure VM with Docker Enginer.
Alongside the application container I have an OTEL Collector (Contrib) container. That OTEL Collector then also exports to the OTLP endpoint for Pyroscope (default port 4040). Pyroscope can be queried from Grafana itself.

@cforce
Copy link

cforce commented Jan 17, 2025

Does the eBpf profile agent needs to run on the same host as the otel collector which is grpc otlp profile signal server for the agent? How can I configure network interface/ip and port for the agent or which other options I have?
I

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants