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
Is your feature request related to a problem? Please describe.
It would be nice to point out that you can export traces to multiple exporters, this is handy if transitioning from one vendor/OSS project to another for the tracing backend. You might want to export to both during the transitional phase.
Describe the solution you'd like
An example where tracing is exported to 2 backends or more.
Describe alternatives you've considered
n/a
Additional context
This is with the presumption that it is possible to export traces to multiple backends. I guess with multiple tracer.addSpanProcessor();s?
The text was updated successfully, but these errors were encountered:
NB: Before opening a feature request against this repo, consider whether the feature should/could be implemented in the other OpenTelemetry client libraries. If so, please open an issue on opentelemetry-specification first.
Is your feature request related to a problem? Please describe.
It would be nice to point out that you can export traces to multiple exporters, this is handy if transitioning from one vendor/OSS project to another for the tracing backend. You might want to export to both during the transitional phase.
Describe the solution you'd like
An example where tracing is exported to 2 backends or more.
Describe alternatives you've considered
n/a
Additional context
This is with the presumption that it is possible to export traces to multiple backends. I guess with multiple
tracer.addSpanProcessor();
s?The text was updated successfully, but these errors were encountered: