Mario Macias

Hi @trask ! Yes, our `DOCKER_TOKEN_EBPF_INSTRUMENTATION` is working well for interactions with Docker Hub.

I endorse this helm chart creation. The previous `opentelemetry-ebpf` helm chart belongs ot the `opentelemetry-network` project, which at the moment has 0% feature overlap with `opentelemetry-ebpf-instrumentation` (both can provide network...

@TylerHelmuth sure! @ittai-coralogix is regularly joining the opentelemetry-ebpf-instrumentation weekly SIG meetings and we are in touch about this issue.

Thanks for the suggestion @cforce ! BTW, Grafana Beyla is already integrated with Grafana Alloy, providing a similar functionality to what you are suggesting https://grafana.com/blog/2024/05/21/how-to-use-grafana-beyla-in-grafana-alloy-for-ebpf-based-auto-instrumentation/

I think this fixes this task, at least partially: https://github.com/grafana/beyla/pull/1069

Isn't "generic_tracer" too generic name? If we have to change this name to avoid other confunsion/duplicities, I would maybe choose a name that describes what instruments and where are the...

It mostly LGTM, thanks for the great work! I have a proposal for some improvements with respect to memory (as previously stated by @grcevski ). They don't have to be...

Upstream fix: https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/pull/33

Even if Marc couldn't become a maintainer I wonder if he could at least grant him merge rights. He is actively working on porting some improvements from Beyla to the...

Hi @trask! Definitely removing the _Require branches to be up to date before merging_ setting would help 💯 . Since we are currently in "development/unstable" status, I think we can...