luweglarz
luweglarz
Hey guys, came across this issue because I am facing the same problems with unknown symbols when the frame pointers are omitted, but then I saw this [PR](https://github.com/grafana/pyroscope/pull/3799), does this...
Awesome! excited to test it !
Hey! Is there any plan to be able to run the java component without root? only using capabilities
I think these caps allow us to avoid running Alloy as privileged but we still need to run it as root as it is enforced by the pyroscope.java component, I...
Hello guys, thanks for the good work! I'm really looking forward for the implementation of otel ebpf profiler Alloy, do we have an estimate on when this could be released?...
What I mean by memory profiling is something similar to what we get when profiling Go applications, the memory that is currently in-use by the process, this is why I...
So I assume that every allocators would need to be attached to their specific usdt probe and handled differently? I thought we could rely on the classic ones like malloc...
Hi @simonswine FYI, when ingesting uprobe profiles from [opentelemetry-ebpf-profiler ](https://github.com/open-telemetry/opentelemetry-ebpf-profiler) I am getting this kind of flamegraph with those user symbols: ``` '--uprobe-link=/lib/x86_64-linux-gnu/libc.so.6:write' '--uprobe-link=/lib/x86_64-linux-gnu/libc.so.6:malloc' ```
Hi @clayton-cornell , resolved conflict on changelog
Hello guys, is this feature gonna be implemented one day or it won't be necessary after Opentelemetry-ebpf-profiler handling ?