-
Notifications
You must be signed in to change notification settings - Fork 484
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
[metrics-generator] overrides per tenant do not work for metrics-generator #3462
Comments
Are there any relevant logs that might help? At first glance I'm not seeing anything wrong with your config. We use the overrides all the time internally so it generally works. Can you review metrics to help narrow down the issue. Are the distributors still sending spans to the generators? Are spans being dropped for any reason? One sharp edge that might be causing this is that if an per tenant override block is matched than the entire block is used for that tenant (including all 0s). Tempo does not override at the field level. |
Dear @joe-elliott, thanks for checking my configuration. I tried the legacy and the new config way with the overrides per tenant, but from the moment an override is used on the metrics_generator it seems to stop working. I'll try to set the log level to debug to see If I can find any more relevant logs. Since the only change is the small overrides part, and traces still seem to come trough, I think no spans are dropped. is there a way to check this? |
After the change to the broken code, I indeed see all lines like rpc error: code = ResourceExhausted desc = RATE_LIMITED: ingestion rate limit (0 bytes) exceeded while adding 923 bytes for user tracing-apps-app-dev Why does it start doing this while I only wanted to override metrics_generator... |
With this config it works, so when you override, make sure you override everything... Thanks @joe-elliott for the solution. |
Thanks for following up! @knylander-grafana can we make sure this is documented somewhere? this has caught multiple people before. |
WIll do! I'll create a doc issue: #3462 |
Describe the bug
I'm trying to use the runtime config to override per tenant configuration, but it does not work.
When leaving the config (tempo.yaml) like this, it works fine.:
The logs of the metrics generator show lines like this: level=info ts=2024-03-05T09:46:15.602380169Z caller=registry.go:232 tenant=tracing-apps-app-dev msg="collecting metrics" active_series=1227
From the moment I change the config to:
tempo.yaml:
overrides.yaml:
the metrics generator doesn't seem to do anything anymore.
For who knows what reason, it keeps working if I do this change and only restart the deployment of the metrics-generator.
Until I remove the namespace, then it's broken.
On an other cluster I tried to use the runtime-config from the first time, and there it never worked.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect that the metrics generator would generate metrics for the tenant tracing-apps-app-dev and sent it to the mimir instance of prometheus-apps-app-dev
Environment:
not working config:
working config:
Additional Context
I need the tenant overrides config since in prd we have multiple tenants.
I found an issue with the same problem, but it got auto closed.
#3032
The text was updated successfully, but these errors were encountered: