Robert Pająk

I have talked with our Product Manager and I am putting the summary below. We SHOULD have experimental features/instrumentation disabled by default. The documentation MUST say which instrumentations produce stable...

Can you double-check if the Go instrumentation and application containers share the process namespace? Reference: - https://github.com/open-telemetry/opentelemetry-go-instrumentation#instrument-an-application-in-kubernetes - https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/

Moving to GA.

@edeNFed bump 😉

Java congratulation: https://opentelemetry.io/docs/languages/java/automatic/configuration/#enable-only-specific-instrumentation

Removing from Beta project. I think it is good enough to test against the latest release for beta.

SIG meeting: - We could create containers with a given Go + library version that we want to test against. We should manually specify the versions (e.g. table driven tests)...

By @RonFed: > Adding support for multiple kernel versions in our e2e tests will greatly improve the eBPF code stability. I found a similar infrastructure we might find helpful in...

I do not think we should have any special handling for SIGKILL. More: https://itecnote.com/tecnote/linux-sigkill-signal-handling/ I see this bug as invalid. @thatsdone am I missing anything or can we close the...

No. I am not a maintainer.