-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
New component: pprofreceiver #38260
Labels
Accepted Component
New component has been sponsored
Comments
I am happy to sponsor this. |
We explicitly self-telemetry going through the Collector pipelines when it comes to metrics, traces and logs. Why should profiles be different? |
The pprof extension can be used to enable the collector to emit profiles... i would expect this to eventually be configurable through |
atoulme
added a commit
that referenced
this issue
Mar 5, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This is a PR for the skeleton of a pprofreceiver. See #38260
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The purpose and use-cases of the new component
With support for profiles as a native signal for the collector, it would be nice if the collector could emit profiles of itself or any other pprof enabled process and export pprof profiles.
Example configuration for the component
Telemetry data types supported
profiles
Code Owner(s)
@MovieStoreGuy @atoulme
Sponsor (optional)
@MovieStoreGuy
Additional context
No response
The text was updated successfully, but these errors were encountered: