Skip to content
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

Closed
djaglowski opened this issue Dec 2, 2024 · 0 comments · Fixed by #36692
Closed

Deprecate routing processor #36616

djaglowski opened this issue Dec 2, 2024 · 0 comments · Fixed by #36692

Comments

@djaglowski
Copy link
Member

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.

@djaglowski djaglowski added the needs triage New item requiring triage label Dec 2, 2024
@evan-bradley evan-bradley removed the needs triage New item requiring triage label Dec 4, 2024
ZenoCC-Peng pushed a commit to ZenoCC-Peng/opentelemetry-collector-contrib that referenced this issue Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants