Replies: 1 comment
-
👋 Zach ! Very late answer after a year. But you were right, OTEL is not mature enough and so the support is limited for Profiling. Pyroscope will be a backend like datadog to receive the data and visualize it later. You can follow work on the OTEL profiling side here open-telemetry/oteps#237. More than a year after you question this is still work in progress. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This might be a dumb question, because i'm totally new to Pyroscope, but I was wondering why the flame graphs from the profiler in the open telemetry examples are displayed separately from the other spans. Is it related to open telemetry not having finalized a spec for profiling yet?
For reference, what i'm trying to do is send profiling data from the Pyroscope agent to an open telemetry collector via OTLP, which should in turn send it to the observability backend (in my case Datadog). I'm not sure if this is possible with Pyroscope at the moment, and i"m pretty sure I don't have a complete/correct mental model for how Pyroscope fits into the open telemetry ecosystem yet. Any clarification would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions