ston1th/node_exporter
0
0
Fork 0
Code Issues Releases Activity

Make the severity of "critical" alerts configurable

Browse source 
This addresses the blissful scenario where single-node failures are
unproblematic. No reason to wake somebody up if a node is about to
screw itself up by filling the disk.

Signed-off-by: beorn7 <beorn@grafana.com>
This commit is contained in:
beorn7 2019-08-14 22:24:24 +02:00
commit 97ef113762
2 changed files with 17 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/node-mixin/alerts/alerts.libsonnet
View file

@ -37,7 +37,7 @@
||| % $._config,
'for': '1h',
labels: {
severity: 'critical',
severity: '%(nodeCriticalSeverity)s' % $._config,
},
annotations: {
summary: 'Filesystem is predicted to run out of space within the next 4 hours.',
@ -73,7 +73,7 @@
||| % $._config,
'for': '1h',
labels: {
severity: 'critical',
severity: '%(nodeCriticalSeverity)s' % $._config,
},
annotations: {
summary: 'Filesystem has less than 3% space left.',
@ -113,7 +113,7 @@
||| % $._config,
'for': '1h',
labels: {
severity: 'critical',
severity: '%(nodeCriticalSeverity)s' % $._config,
},
annotations: {
summary: 'Filesystem is predicted to run out of inodes within the next 4 hours.',
@ -149,7 +149,7 @@
||| % $._config,
'for': '1h',
labels: {
severity: 'critical',
severity: '%(nodeCriticalSeverity)s' % $._config,
},
annotations: {
summary: 'Filesystem has less than 3% inodes left.',