-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for golang auto-instrumentation #908
Comments
Golang auto-instrumentation has been donated open-telemetry/opentelemetry-go-instrumentation#2 |
@pavolloffay @open-telemetry/operator-maintainers @open-telemetry/operator-approvers if the community is willing, I would like to start working on this. |
@TylerHelmuth I'll be happy to help if needed |
@edeNFed sounds good! I'm sure I'll have some questions once I get started. |
Please assign this to me. |
Question: will we want to build our own version of the go auto-instrumentation agent like we do for the other languages or will it be acceptable to use the image published by opentelemetry-go-instrumentation? |
As discussed in the SIG meeting today, we'll move forward with using an image published from open-telemetry/opentelemetry-go-instrumentation instead of building our own. This decision is made based on the increased complexity of the go auto instrumentation due to eBPF and the necessary offsets json file we would have to manage if we had our own image. |
The https://github.com/keyval-dev/opentelemetry-go-instrumentation could be used for golang auto-instrumentation.
From the object management perspective it would be better if the project was part of the CNCF/OTEL community.
cc) @edeNFed
The text was updated successfully, but these errors were encountered: