-
Notifications
You must be signed in to change notification settings - Fork 820
feat: Emit per-tenant limit overrides as metrics #3785
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Add a new target (not enabled as part of "all") that can be used to expose per-tenant limit overrides as Prometheus metrics. These metrics are updated as runtime configuration is periodically reloaded. Exposing these metrics enables use cases like proactively alerting when tenants start to approach their limits, instead of letting them hit their limits and start to lose data. Fixes #1433 See also #2957 Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work. I'd suggest to simplify the design of OverridesExporter
, since it doesn't need to react on changing values immediately.
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You did great! 👏
What this PR does:
Add a new target (not enabled as part of "all") that can be used to
expose per-tenant limit overrides as Prometheus metrics. These metrics
are updated as runtime configuration is periodically reloaded.
Exposing these metrics enables use cases like proactively alerting when
tenants start to approach their limits, instead of letting them hit their
limits and start to lose data.
Which issue(s) this PR fixes:
Fixes #1433
See also #2957
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
Signed-off-by: Nick Pillitteri nick.pillitteri@grafana.com