Add Devfiler to README
Devfiler is now an open-source project under Elastic and we should refer to it from this project's README.
Note that this sets a precedent. If we link an elastic project in the readme, we should link every other project that may do the same in the future.
Note that this sets a precedent. If we link an elastic project in the readme, we should link every other project that may do the same in the future.
That's fine with me, we can have a separate section listing all such projects (AFAIK right now there's only devfiler as a standalone desktop app). The aim of listing it in the README is primarily to help eBPF profiler users and developers get up and running with a minimum of effort.
If we link an elastic project in the readme, we should link every other project that may do the same in the future.
I think we can do a list for open source projects based as people submit PRs or we discover such things. Definitely having documentation / links on how to get a fast start on the profiler should be included.
Trying to see profiles from real apps is a tribal knowledge. At the same time it's a must for people who want to try out and adopt OTel profiling without setting up complex OTel collectors with third party backends. What's more the OTel profiles signal is unstable so choosing the right OTel collector distro and version is another challenge. You must know the history of the project to realize that there used to be Devfiler available for download, which is now open sourced by Elastic.
That said, I'd love to see tools such as Devfiler in the README or some other docs. Another example is OpenTelemetry Collector eBPF Profiling Distribution, which I think hasn't been released yet. Thus, I had to build my own artifact just to test opentelemetry-ebpf-profiler.