Skip to content

Conversation

@florianl
Copy link
Member

@florianl florianl commented Oct 9, 2025

No description provided.

Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
@florianl florianl requested a review from a team as a code owner October 9, 2025 14:49
@florianl florianl marked this pull request as draft October 9, 2025 14:50
Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
@florianl florianl force-pushed the profilingmetrics-kernel branch from 8f4c949 to 5f2af53 Compare October 10, 2025 08:58
@florianl florianl marked this pull request as ready for review October 20, 2025 07:08
metricBeam = metric{name: "samples.beam.count", desc: "Number of samples executing Beam code (self)"}
metricUser = metric{name: "samples.user.count", desc: "Number of samples executing userspace code (self)"}
metricKernel = metric{name: "samples.kernel.count", desc: "Number of samples executing kernel code (self)"}
metricSyscall = metric{name: "samples.syscall.count", desc: "Number of samples executing syscall code (self)"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of adding one more metric, we can use the same method as metricNative: We know that there can not be multiple syscalls per stacktrace, so we can enrich metricKernel with the syscall name attribute.

We can do that inside classifyFrame (which we can rename to classifyFrames) and have it take an extra argument kernelCounts map[string]int64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants