-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update context dynamically from attributes #34649
Comments
Just my 2 cents. I do not think that is possible make a new OTTL function (for the
I think the best way is having a dedicated processor, which makes people aware of its purpose with a clear documentation and use cases (dealing with the Context). Extending the Time ago I discussed this topic with @jpkrohling |
+1 for this need, we faced similar situation where we need to
|
Please consider attending a SIG meeting to discuss this. |
+1 I'm having the same problem currently. Is there anything against integrating https://github.com/springernature/o11y-otel-contextprocessor/tree/main/otelcol-dev/contextprocessor to contrib? |
I have updated the example with a similar configuration we are using in production as a gateway role. You can always create your own distribution of the otelcol binary with this processor. |
Component(s)
No response
Is your feature request related to a problem? Please describe.
We would need to have a way to define tenants from attributes. The
headerssetterextension
can automatically set tenants (or other headers) from the context, but there is not way to modify/update the context. See #27901 for more details.Describe the solution you'd like
We are not sure about the solution. Potential solutions are:
groupbyattrprocessor
(or other processor) to group resources with a new context.The problem is the context it needs to be changed is the connection context, "one level up" of the resource context.
Describe alternatives you've considered
Right now we are using a custom processor to overcome this limitation. This processor was not developed to be committed to Otel repos, it started as a PoC and now we are using it internally. If agreed, we are happy to integrated in Otel Contrib.
Additional context
No response
The text was updated successfully, but these errors were encountered: