r1viollet

:wave: Thanks for the feedback. **The anonymous frames** - It seems the profiler is not matching the debug information for your libc. This is not too important as the base...

Could you try the main branch with `container-id` information ? This will allow you to understand which containers are responsible for different parts of the flamegraph. There is a side...

That would be great! My question is basically if the current `container-id` information is enough for you to slice the profiles in the relevant dimensions.

This was released. You now have a `container-id` filter in the side panel on the right hand side.  This ID can be used in the infrastructure view to match...

The next item you discussed was PID filtering. Is this still something required ? The UI filtering mechanism already provides a way to do this.

Latest release `v0.17.1` greatly improves the performances of the sidecar approach. I would recommend upgrading.

I started looking into this working from @aristotelhs 's pointers. I could not find dwarf information within the jitdump. It seems llvm does not emit it through jitdump. It is...

Possible improvements: - A C++ type could wrap and drop resources.

If the first command is working, it should be a dupe of this issue: https://github.com/DataDog/ddprof/issues/283 It should not relate to #276 which now seems to be an issue with JITDump....

The bug is that we only follow the initial TID. If it happens that nothing happens in that given TID, we won't be showing anything. Erlang might not be easy...