-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[kube-prometheus-stack] multi tenant alert routing #1274
[kube-prometheus-stack] multi tenant alert routing #1274
Conversation
Signed-off-by: Robert N <[email protected]> Signed-off-by: Robert Nemeti <[email protected]>
9326018
to
857cc34
Compare
@@ -18,7 +18,7 @@ name: kube-prometheus-stack | |||
sources: | |||
- https://github.com/prometheus-community/helm-charts | |||
- https://github.com/prometheus-operator/kube-prometheus | |||
version: 18.0.0 | |||
version: 18.0.2 |
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.
adding new feature should raise chart minor version
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.
@monotek , thanks for the feedback. updated the minor version.
Signed-off-by: Robert Nemeti <[email protected]>
bump |
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.
Two things worth noting:
- You've made changes in file that are generated. These changes will be overwritten.
- I've proposed an alternative solution to probably solve your problem. See my comment in kube-state alert routing in multi tenant cluster #1231 (comment)
@@ -29,7 +29,10 @@ spec: | |||
description: '{{`{{`}} printf "%.4g" $value {{`}}`}}% of the {{`{{`}} $labels.job {{`}}`}}/{{`{{`}} $labels.service {{`}}`}} targets in {{`{{`}} $labels.namespace {{`}}`}} namespace are down.' | |||
runbook_url: {{ .Values.defaultRules.runbookUrl }}alert-name-targetdown | |||
summary: One or more targets are unreachable. | |||
expr: 100 * (count(up == 0) BY (job, namespace, service) / count(up) BY (job, namespace, service)) > 10 | |||
expr: |- | |||
{{ .Values.defaultRules.expressionPrefix }} |
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.
This is a change in a generated file (see the comment at the top of the file). When the next rules-sync is executed, your changes will be reverted.
thanks for the proposed solution. closing this. |
Signed-off-by: Robert N [email protected]
What this PR does / why we need it:
allow alert routing in multi tenant clusters to different teams
Which issue this PR fixes
(optional, in
fixes #<issue_number> (, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes for your reviewer:
hey @vsliouniaev , @bismarck, @gianrubio , @gkarthiks, @scottrigby, @Xtigyro, would you be so kind to review this change. Thanks in advance.
Cheers,
Robert
Checklist
[prometheus-couchdb-exporter]
)