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

New component: pprofreceiver #38260

Open
atoulme opened this issue Feb 27, 2025 · 3 comments
Open

New component: pprofreceiver #38260

atoulme opened this issue Feb 27, 2025 · 3 comments
Labels
Accepted Component New component has been sponsored

Comments

@atoulme
Copy link
Contributor

atoulme commented Feb 27, 2025

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

receivers:
  pprof/self: # no configuration
  pprof/somegoprocess:
    endpoint: 127.0.1.1:8000

Telemetry data types supported

profiles

Code Owner(s)

@MovieStoreGuy @atoulme

Sponsor (optional)

@MovieStoreGuy

Additional context

No response

@atoulme atoulme added needs triage New item requiring triage Sponsor Needed New component seeking sponsor labels Feb 27, 2025
@MovieStoreGuy
Copy link
Contributor

I am happy to sponsor this.

@atoulme atoulme added Accepted Component New component has been sponsored and removed Sponsor Needed New component seeking sponsor needs triage New item requiring triage labels Feb 28, 2025
@mx-psi
Copy link
Member

mx-psi commented Mar 3, 2025

could emit profiles of itself

We explicitly self-telemetry going through the Collector pipelines when it comes to metrics, traces and logs. Why should profiles be different?

@codeboten
Copy link
Contributor

The pprof extension can be used to enable the collector to emit profiles... i would expect this to eventually be configurable through service::telemetry::profiles. Maybe I'm missing something

atoulme added a commit that referenced this issue Mar 5, 2025

Unverified

The email in this signature doesn’t match the committer email.
<!--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
Labels
Accepted Component New component has been sponsored
Projects
None yet
Development

No branches or pull requests

4 participants