Make the severity of "critical" alerts configurable
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.
||| % $._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.',
||| % $._config,
'for': '1h',
labels: {
- severity: 'critical',
+ severity: '%(nodeCriticalSeverity)s' % $._config,
},
annotations: {
summary: 'Filesystem has less than 3% space left.',
||| % $._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.',
||| % $._config,
'for': '1h',
labels: {
- severity: 'critical',
+ severity: '%(nodeCriticalSeverity)s' % $._config,
},
annotations: {
summary: 'Filesystem has less than 3% inodes left.',
