-
Notifications
You must be signed in to change notification settings - Fork 826
Expose instance AZ in ring via Prometheus metric #4681
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
base: master
Are you sure you want to change the base?
Conversation
Name: "ring_availability_zone", | ||
Help: "The availability zone of the instance", | ||
}, []string{"az"}) | ||
zoneInfo.WithLabelValues(zone).Set(1) |
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.
If there is no zone (i.e. zone is empty string) should we skip on emitting this metric?
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.
yes I agree
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
Hello @roystchiang, thank you for opening this PR. There is a release in progress. As such, please rebase your CHANGELOG entry on top of the master branch and move the CHANGELOG entry to the top under Thanks, |
We are adding something similar with #6900 @roystchiang do you still wanna work on this or can we close? |
What this PR does:
Add a new metric
cortex_ring_availability_zone
for displaying which availability zone an instance is configured to run in. This helps with monitoring via Prometheus, and can help detect if there's an unbalance in AZ distribution.Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]