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.
Hi everyone,
I would like to use the routingprocessor to route my records to different exporters based on a resource attribute value.
Currently, the routingprocessor uses context to find the attribute.
Describe the solution you'd like
I'd like to add a new configuration option like attribute_source, which could be set to context or resource and would default to context to keep backwards compatibility. If set to resource, the processor would look for the attribute specified in from_attribute not in the context, but in resource attributes.
At the same time, I'd like to extend the scope of the processor from traces only to logs and metrics as well (this could be a separate pull request if that makes sense).
Describe alternatives you've considered
I don't really see any alternative.
Additional context
Not much
The text was updated successfully, but these errors were encountered:
**Description:** Add a feature to `routingprocessor` to route traces on resource attributes and make it configurable (retaining previous default to read from context).
**Link to tracking Issue:** Fixes#5538
**Testing:** Added unit tests.
**Documentation:** Changed README.
---
Huge shout-out to @astencel-sumo for this patch! 🙇
Is your feature request related to a problem? Please describe.
Hi everyone,
I would like to use the routingprocessor to route my records to different exporters based on a resource attribute value.
Currently, the routingprocessor uses context to find the attribute.
Describe the solution you'd like
I'd like to add a new configuration option like
attribute_source
, which could be set tocontext
orresource
and would default tocontext
to keep backwards compatibility. If set toresource
, the processor would look for the attribute specified infrom_attribute
not in the context, but in resource attributes.At the same time, I'd like to extend the scope of the processor from traces only to logs and metrics as well (this could be a separate pull request if that makes sense).
Describe alternatives you've considered
I don't really see any alternative.
Additional context
Not much
The text was updated successfully, but these errors were encountered: