-
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
Loki Receiver + HeaderSetter + Loki Exporter Issue #31847
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Can you share a minimal configuration file that depicts the issue? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm removing Loki exporter from the equation, as I'm confident this would affect any other exporter as well. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/loki, extension/headerssetter, receiver/loki
Describe the issue you're reporting
I'm trying to deploy a Loki collector agent that collect logs from network agents on a Loki endpoint and forward them on several Loki backend.
The agents correctly send Authorization header and X-Scope-OrgID header to the collector. The collector is expected to forward these headers to Loki backend for proper tenant assignment of logs.
The idea is the same here but with a Loki receiver and multiple exporters.
I'm still not sure if possible to add multiple Loki exporter, but by first test it seems that with the adapted above setup Loki backend is not receiving Authorization and X-Scope-OrgID headers when using a Loki receiver while correctly receiving header when using the otlp receiver.
The text was updated successfully, but these errors were encountered: