-
Notifications
You must be signed in to change notification settings - Fork 298
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
Comments
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? |
can elasticsearch receive the OTLP profile signal from otel collector ? |
Not yet, no. But we are working on profiles support for the elasticsearch collector exporter. |
opentelemetry-ebpf-profiler needs to run on the host which should be observed, while the opentelemetry-collector / profiling backend able to receive the OTLP signals can run on another host.
cf. https://github.com/open-telemetry/opentelemetry-ebpf-profiler?tab=readme-ov-file#running |
Thanks Since I posted this issue I have also come across https://github.com/metrico/qryn which claims to be able to ingest Opentelemetry profiling signals and being compatible with Pyroscope API (so usable from Grafana). I haven't tried it yet though. |
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?
The text was updated successfully, but these errors were encountered: