-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate routing processor #36616
Comments
ZenoCC-Peng
pushed a commit
to ZenoCC-Peng/opentelemetry-collector-contrib
that referenced
this issue
Dec 6, 2024
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this issue
Dec 17, 2024
AkhigbeEromo
pushed a commit
to sematext/opentelemetry-collector-contrib
that referenced
this issue
Jan 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
No response
Describe the issue you're reporting
I believe the routing connector now supports all functionality that the processor supports, aside from the legacy
from_attribute
. This includes routing by grpc request headers, http request headers, resource context, span context, metric context, data point context, and log context. Additionally, routing is much more flexible because each routing table item may evaluate in a different context.The text was updated successfully, but these errors were encountered: