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
We currently have two ways to instrument the opentelemetry-go global API. These should be unified into a single probe. If the global API being used is a version prior to the auto/sdk package integration the original otelglobal instrumentation should be used. Otherwise, the autosdk instrumentation should be used.
The text was updated successfully, but these errors were encountered:
This "merge" isn't needed. Based on #1405 all we will need to do is keep the autosdk probe as is and instrument the newSpan function to "turn on" the use of auto/sdk in the global API. The current global instrumentation will continue to work if the code-path is not changed based on this flag setting.
We will need to work out how to instrument (*tracer).newSpan only for versions > 1.32 of otel. That can be included in #1399 as an action item.
We currently have two ways to instrument the opentelemetry-go global API. These should be unified into a single probe. If the global API being used is a version prior to the
auto/sdk
package integration the originalotelglobal
instrumentation should be used. Otherwise, theautosdk
instrumentation should be used.The text was updated successfully, but these errors were encountered: