search

draios / sysdig

Linux system exploration and troubleshooting tool with first class support for containers
http://www.sysdig.com/
Other
7.73k stars 726 forks source link

instrument stacks #43

Open brendangregg opened 10 years ago

brendangregg commented 10 years ago

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 commented 9 years ago

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

Is there any plan for this?

dsummersl commented 9 years ago

+1!

acornejo commented 8 years ago

+1

unlikely-leo commented 8 years ago

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

github-actions[bot] commented 1 year ago

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.