easylinux/kube-prometheus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #1093 from ArthurSens/as/custom-alerts-description

Browse Source
This commit is contained in:
Paweł Krupa
2021-04-20 19:13:48 +02:00
committed by GitHub
parent 4839afb546 72b742d7e8
commit 752d1a7fdc
2 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
jsonnet/kube-prometheus/components/mixin/alerts/general.libsonnet
View File

@@ -7,7 +7,8 @@
{ {
alert: 'TargetDown', alert: 'TargetDown',
annotations: { annotations: {
message: '{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service }} targets in {{ $labels.namespace }} namespace are down.', summary: 'One or more targets are unreachable.',
description: '{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service }} targets in {{ $labels.namespace }} namespace are down.',
}, },
expr: '100 * (count(up == 0) BY (job, namespace, service) / count(up) BY (job, namespace, service)) > 10', expr: '100 * (count(up == 0) BY (job, namespace, service) / count(up) BY (job, namespace, service)) > 10',
'for': '10m', 'for': '10m',
@@ -18,7 +19,8 @@
{ {
alert: 'Watchdog', alert: 'Watchdog',
annotations: { annotations: {
message: ||| summary: 'An alert that should always be firing to certify that Alertmanager is working properly.',
description: |||
This is an alert meant to ensure that the entire alerting pipeline is functional. This is an alert meant to ensure that the entire alerting pipeline is functional.
This alert is always firing, therefore it should always be firing in Alertmanager This alert is always firing, therefore it should always be firing in Alertmanager
and always fire against a receiver. There are integrations with various notification and always fire against a receiver. There are integrations with various notification

6
manifests/kube-prometheus-prometheusRule.yaml
View File

@@ -15,21 +15,23 @@ spec:
rules: rules:
- alert: TargetDown - alert: TargetDown
annotations: annotations:
message: '{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service }} targets in {{ $labels.namespace }} namespace are down.' description: '{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service }} targets in {{ $labels.namespace }} namespace are down.'
runbook_url: https://github.com/prometheus-operator/kube-prometheus/wiki/targetdown runbook_url: https://github.com/prometheus-operator/kube-prometheus/wiki/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: 100 * (count(up == 0) BY (job, namespace, service) / count(up) BY (job, namespace, service)) > 10
for: 10m for: 10m
labels: labels:
severity: warning severity: warning
- alert: Watchdog - alert: Watchdog
annotations: annotations:
message: | description: |
This is an alert meant to ensure that the entire alerting pipeline is functional. This is an alert meant to ensure that the entire alerting pipeline is functional.
This alert is always firing, therefore it should always be firing in Alertmanager This alert is always firing, therefore it should always be firing in Alertmanager
and always fire against a receiver. There are integrations with various notification and always fire against a receiver. There are integrations with various notification
mechanisms that send a notification when this alert is not firing. For example the mechanisms that send a notification when this alert is not firing. For example the
"DeadMansSnitch" integration in PagerDuty. "DeadMansSnitch" integration in PagerDuty.
runbook_url: https://github.com/prometheus-operator/kube-prometheus/wiki/watchdog runbook_url: https://github.com/prometheus-operator/kube-prometheus/wiki/watchdog
summary: An alert that should always be firing to certify that Alertmanager is working properly.
expr: vector(1) expr: vector(1)
labels: labels:
severity: none severity: none