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
There are a number of features that we are definitely going to provide for all HTTP instrumentation modules:
Context Propagation.
Distributed Tracing, which builds on top of the previous feature.
Metrics based on the Spans created for DT.
But there is now way at the moment to enforce that at least certain span and metric tags are present on all integrations. One thing that is worth noting is Brave's HttpTracing which kind of resonates with what I think we should have, just with a broader scope.
The text was updated successfully, but these errors were encountered:
I'm closing this issue because it is either too old to be relevant or stale. Stop by our Github Discussions section and drop a message if you need any additional help with the topic.
There are a number of features that we are definitely going to provide for all HTTP instrumentation modules:
But there is now way at the moment to enforce that at least certain span and metric tags are present on all integrations. One thing that is worth noting is Brave's HttpTracing which kind of resonates with what I think we should have, just with a broader scope.
The text was updated successfully, but these errors were encountered: