Skip to content
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

Support Go binaries built with Bazel #1212

Open
RonFed opened this issue Oct 23, 2024 · 0 comments
Open

Support Go binaries built with Bazel #1212

RonFed opened this issue Oct 23, 2024 · 0 comments
Assignees

Comments

@RonFed
Copy link
Contributor

RonFed commented Oct 23, 2024

Currently, it seems we can't properly handle binaries built with Bazel.
Here is an example log from a client using the auto instrumentation on such a binary:

{"level":"info","ts":1729185294.8680952,"logger":"Instrumentation","caller":"[email protected]/instrumentation.go:150","msg":"target process analysis completed","pid":1553249,"go_version":"1.20.11","dependencies":{"std":"1.20.11"},"total_functions_found":13}

It seems we only managed to extract the Go version, without all the dependencies and their versions.

To parse the dependencies data we use buildinfo.Read. From the documentation for that function:

// Read returns build information embedded in a Go binary file
// accessed through the given ReaderAt. Most information is only available for
// binaries built with module support.

according to that comment - I guess the reason is the binary is "not built with module support".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants