You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our use case is as follows.
We implement a third-party API (Bazel Remote Execution) and most of the requests have a well known identifier called the invocation ID. I would like to add the invocation ID to the generated spans so that it's easy to find traces by invocation ID.
My questions are:
(1) Is it already somehow possible to accomplish this without modifying the instrumentation code?
(2) Are you interested in this patch?
The text was updated successfully, but these errors were encountered:
Figured out how to do it without modifying the instrumentation code and it's apparently super simple.
Add another interceptor that retrieves the current span and adds an attribute.
Figured out how to do it without modifying the instrumentation code and it's super simple.
Add another interceptor that retrieves the current Spans and adds an attribute.
Heh, I was going to suggest this but I assumed you were looking for a more generic approach. I don't do much (read anything) with gRPC so I assumed there was a complication I was missing. Glad you've come to a working solution!
Our use case is as follows.
We implement a third-party API (Bazel Remote Execution) and most of the requests have a well known identifier called the invocation ID. I would like to add the invocation ID to the generated spans so that it's easy to find traces by invocation ID.
I patched our version of opentelemetry-go-contrib:
https://github.com/open-telemetry/opentelemetry-go-contrib/compare/main...vadimberezniker:context_hook?expand=1
My questions are:
(1) Is it already somehow possible to accomplish this without modifying the instrumentation code?
(2) Are you interested in this patch?
The text was updated successfully, but these errors were encountered: