Eden Federman

Hi @mrueg I'm currently working on switching from privileged pod to specific capabilities. Hope to have it ready in a few days. Thanks

Yes, you got it right. The container that contains async-profiler is built here: https://github.com/yahoo/kubectl-flame/blob/master/agent/docker/jvm/Dockerfile The fork repo is a workaround, back when I developed it async-profiler didn't work well with...

Hi @zhiyanliu Sorry for the late response. I haven't seen anything like that before, but from googling your error it looks like something in the Kubernetes cluster is preventing the...

Hi, can you please try version v0.6.0? We made a big refactoring regarding the way we calculate trace ids.

This is awesome! I opened [this issue](https://github.com/keyval-dev/opentelemetry-go-instrumentation/issues/23) for process discovery, hope to finish it in the next few days. You can track the donation process to the OpenTelemetry project [here](https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/2)

In addition to the eBPF solution there is also a code generation solution called instrgen: https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrgen cc @pdelewski

Hi @mariomac looks like some nice additions on top of the existing offsets tracker. I think you can just go ahead and submit a PR to the opentelemetry-go-instrumentation repo. I...

I don't think moving `instrgen` to `opentelemetry-go-instrumentation` is a good idea. From a user perspective, I expect all the repositories named `opentelemetry-XXX-instrumentation` will be an agent-like thing that does instrumentation...

The only thing shared between the eBPF instrumentation and the compiled time instrumentation is that they are both targeting Go applications. Everything else is different, the programming language the instrumentation...

Hi @CoderPoet We allocate memory in an area that is not affected by the GC. Recent changes like the addition of arenas should not have an effect on this.