-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Component(s)
service
Is your feature request related to a problem? Please describe.
We want to send the collector's internal telemetry to a backend that uses OIDC authentication. Right now the internal telemetry exporter does not have support for OIDC authentication.
Describe the solution you'd like
I'm looking for the ability to configure the exporter used for internal telemetry to use OIDC authentication.
Describe alternatives you've considered
There is a OIDC auth extension in contrib but this is only applicable to pipelines the collector is running, not the internal telemetry it is producing. The collector could scrape itself but it seems like it'd be better to have the collector's internal telemetry go directly to the backend rather than re-ingest the telemetry through a pipeline.
Additional context
Has anyone ran into this use case before? If so, what solution did you use?
The configuration and exporter used for internal telemetry comes from the OTel Go SDK. Specifically the configuration is here and the specific exporter used is here (either the HTTP or gRPC exporters depending on configuration, regardless of which the issue applies to both).
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.