-
Notifications
You must be signed in to change notification settings - Fork 2
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
rename prometheus-agent inbitions to monitoring agent to be able to take alloy into account #1753
rename prometheus-agent inbitions to monitoring agent to be able to take alloy into account #1753
Conversation
This has to be synchronized with a change of labels on prometheus-rules, right? |
Oh, found the prometheus-rules PR here: giantswarm/prometheus-rules#1405 I wonder what will happen when releasing these, and whether it we need a deployment plan or a phased deployment? |
Yes I Linked this PR in the rules. I think the only thing we Can do is merge this and prometheus and sloth rules at the same time |
Well, we could have a non-breaking phased deployment that would do:
This would ensure we don't have a moment with no inhibitions and clusters firing lots of alerts. |
Sure. I'll create the pr tomorrow then |
…ake alloy into account
489ee70
to
2b8389f
Compare
@hervenicol as requested, I added new inhibitions to have a seamless upgrade |
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
Towards giantswarm/roadmap#3590.
We now use alloy as a monitoring agent so having the inhibition named prometheus-agent makes no sense.
This PR renames both inbititions about missing prometheus agent to monitoring agent.
Checklist
I have:
CHANGELOG.md