Open takahiko-okada opened 5 months ago
This issue has not had any activity in the past 30 days, so the needs-attention
label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention
label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
What's wrong?
The following configuration should create logs under the
tenant_id
oftenant_a
.However, when I specify
X-Scope-OrgID: tenant_a
on Grafana Cloud's Loki Datasource, I don't get any logs returned, even the labels, because the logs seems to be created under thetenant_id
ofgrafana_alloy
.Problems:
tenant_id
on Alloy configuration becomes meaningless when we useloki.tenants
configuration at Loki Helm Chart instead of using the gateway basicAuthusername
andpassword
. My assumption is that Loki starts managing the logs/chunks/indexes usingloki.tenants[<index>].name
Steps to reproduce
values.yaml
, setloki.tenants
configuration instead of using the gateway basicAuthusername
andpassword
.values.yaml
, setloki.write.endpoint.tenant_id
to a different string from Loki Helm Chartloki.tenants[0].name
invalues.yaml
System information
Linux
Software version
Alloy Helm Chart v0.3.2, Loki Helm Chart v6.6.3
Configuration
Logs
No response