-
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
httpheader extension: Expose HTTP headers as ClientInfo.Auth #6700
Conversation
|
This is an interesting approach, but I think it would make more sense to have a new field in the Then, the confighttp/configgrpc would populate it, in a similar way it does with the client IP: |
I agree, this is more of a band aid approach while waiting for the collector code to mature (and hopefully we can have these helpers upstream in the future). My use case is a bit different and this was a pain point for us with the http receivers, so wanted to send it in rather than having it sit in a private repo. |
@disq please provide the motivation for this. @jpkrohling do you know why this is useful? |
@bogdandrutu we're using OTLP basically as an analytics suite, to collect anonymous usage information (and crash/error reporting to an extent) on a CLI tool. Promscale/Grafana for reporting. This extension enables us to use a "geoip processor" to inject geolocation data into traces as the main collector runs behind a load balancer. I was thinking it might be useful for others. |
This has been requested a few times in the past, including here: open-telemetry/opentelemetry-collector#2401 |
I think we now have everything in place to accommodate this feature. Would you be willing to give it a try? |
I'll see what I can do, hopefully this week. |
Description: New auth extension to expose HTTP headers as ClientInfo.Auth fields, which then can be used in the processor pipeline, as in:
Documentation: