-
Notifications
You must be signed in to change notification settings - Fork 308
Profiling for specific process by labels, not all node processes #358
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
Comments
As a sampling based profiler, eBPF profiler is designed and architected to profile the whole system. Filtering, e.g. on a label, can be applied on post processing stages, the backend or UI. |
Look forward to the integration into OTel collector very much. |
@florianl Do we have roadmap for when integrate the profiler into OTel collector? |
@florianl , to your comment on limiting it to post processing, it would add overhead on the node given it will profile every single process. is it not possible to filter down to specific pods? |
With the merge of open-telemetry/opentelemetry-collector-releases#908 one big step was achieved to make profiling part of OTel collector. Profiling is still considered not stable in Open Telemetry, as there is still work ongoing. As far as I know, there is no fixed roadmap.
eBPF profiler is designed as whole system profiler. Benchmarks as real world deployments show, that it's overhead on profiling all processes is minimal and negligible. Adding filtering on the eBPF level would introduce some noticeable complexity and maybe race conditions. |
I am not sure if this feature is reasonable for this project, may be more proper when migrate this profiler into openTelemetry collector as profiling agent.
We plan to adopt continuous profiling for internal use. And the common use case is to select some specific pods to obtain profiling data instead of all kinds of processes in K8s node.
Invested several agents like Grafana Alloy/Parca/Pixie, all of them support the feature that only profiling specific pods. And as we move eBPF profiler into collector as agent, this should be a very reasonable requirement right?
The text was updated successfully, but these errors were encountered: