We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ctx
This issue has already been mentioned in Slack, and it is posted here to track progress.
In the database/sql instrumentation, I found two pieces of code: https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/e6f3f3cab8[…]2/internal/pkg/instrumentation/bpf/database/sql/bpf/probe.bpf.c
get_Go_context(ctx, 2, 0, true, &go_context);
https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/e6f3f3cab8[…]2/internal/pkg/instrumentation/bpf/database/sql/bpf/probe.bpf.c
UPROBE_RETURN(queryDC, struct sql_request_t, sql_events, events, 3, 0, true)
In the entry probe, the context_pos is 2, but in the return probe the context_pos is 3? I suppose the position in the return probe is also 2?
Although I believe there is an error of ctx pos, currently the functionality is still working properly.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This issue has already been mentioned in Slack, and it is posted here to track progress.
In the database/sql instrumentation, I found two pieces of code:
https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/e6f3f3cab8[…]2/internal/pkg/instrumentation/bpf/database/sql/bpf/probe.bpf.c
https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/e6f3f3cab8[…]2/internal/pkg/instrumentation/bpf/database/sql/bpf/probe.bpf.c
In the entry probe, the context_pos is 2, but in the return probe the context_pos is 3? I suppose the position in the return probe is also 2?
Although I believe there is an error of ctx pos, currently the functionality is still working properly.
The text was updated successfully, but these errors were encountered: