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
I would like to be able to use this type of filter like so that i may be able to route all spans/traces to one exporter but for another exporter only receive a subset of the spans within a trace
I've looked through the various suggestions proposed in open-telemetry/opentelemetry-collector#2310 and did not find anything relevant. Everything is related to filtering at the trace level, not at the span level.
I understand this may result in incomplete traces but believe that this is something we can live with initially even if we cannot cover remapping spans in a first implementation to help control scope of the change.
I see several people requesting similar functionality
Is your feature request related to a problem? Please describe.
We need a feature to allow for dropping/filtering spans from third party services which are out of our control.
Describe the solution you'd like
Being able to use a syntax similar to the logs and metrics filterprocessor would be useful.
I would like to be able to use this type of filter like so that i may be able to route all spans/traces to one exporter but for another exporter only receive a subset of the spans within a trace
Describe alternatives you've considered
I've looked through the various suggestions proposed in open-telemetry/opentelemetry-collector#2310 and did not find anything relevant. Everything is related to filtering at the trace level, not at the span level.
I did read that at a SIG this was discussed and resulted in some additional work being identified.
I understand this may result in incomplete traces but believe that this is something we can live with initially even if we cannot cover remapping spans in a first implementation to help control scope of the change.
I see several people requesting similar functionality
The text was updated successfully, but these errors were encountered: