instrument stacks

[brendangregg]

A stack field class could be included, with stack.kernel and stack.user for retrieving each stack back trace. This would allow quick identification of the reason events occurred: code path ancestry.

A minor detail: it doesn't matter if stacks are returned multi-line (easier to read) or single-line (easier to post process). Eg, for single line, frames can be separated by ';'.

(Stack trace data can also be easily fed into Flame Graphs...)

[lovasko]

Exactly, I was just exploring sysdig and was wondering if I could use the Flame graphs by @brendangregg 👍

Is there any plan for this?

[dsummersl]

+1!

[acornejo]

+1

[unlikely-leo]

Any movement on this issue? We'd be very interested in using sysdig to profile our staging clusters. @ashmere @mwitkow

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.