Add eBPF CPU profiling path from stack sampling to Pyroscope export.#660
Merged
Conversation
polychrome56
force-pushed
the
main
branch
2 times, most recently
from
July 18, 2026 11:44
afb22cc to
5f450dd
Compare
Wire probe CGO and a minimal BCC symbolizer, and extend cgoreceiver to periodically encode pprof and push process_cpu profiles when ebpf_profiling.endpoint.url is set. Signed-off-by: 赵翔宇 <zhaoxiangyu@harmonycloud.cn>
J-lena
approved these changes
Jul 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add continuous eBPF CPU stack sampling and Pyroscope export to Kindling.
cgoreceiverperiodically builds gzip pprof and pushesprocess_cpuprofiles whenreceivers.cgoreceiver.ebpf_profiling.endpoint.urlis setpids: []samples all processes, non-emptypidsenables a host-PID whitelistdocs/ebpf_cpu_profiling.mdand deploy YAML examplesThis path is independent of the existing Camera On/OffCPU flame graph.
Related Issue
N/A
Motivation and Context
Enable continuous CPU flame graphs in open-source Kindling via Grafana Pyroscope, without depending on the Camera UI pipeline or a dynamic PID control plane.
How Has This Been Tested?
libkindling) with localagent-libsand BCC symbolizer wiringpprof,pyroscopeexporter,cgoreceiver)endpoint.urlempty) andpidsempty means capture-allprocess_cpuprofiles appear after ~15s (privileged agent required)