Fix spurious DiscFilling alerts after reboots due to changing device names
This commit is contained in:
parent
1daf64a848
commit
b99318f2b4
1 changed files with 2 additions and 2 deletions
|
|
@ -229,7 +229,7 @@ prometheus_agent:
|
|||
group: nodeexporter
|
||||
alert: DiscFilling
|
||||
enabled: True
|
||||
expr: predict_linear(node_filesystem_free_bytes{fstype!~"tmpfs", job="node", instance="{{ inventory_hostname }}"}[12h], 24 * 3600) < 0
|
||||
expr: predict_linear((min by (instance, mountpoint) (node_filesystem_free_bytes{fstype!~"tmpfs", job="node", instance="{{ inventory_hostname }}"}))[12h:1m], 24 * 3600) < 0
|
||||
for: 5m
|
||||
labels:
|
||||
severity: warning
|
||||
|
|
@ -240,7 +240,7 @@ prometheus_agent:
|
|||
group: nodeexporter
|
||||
alert: DiscFilling
|
||||
enabled: True
|
||||
expr: predict_linear(node_filesystem_free_bytes{fstype!~"tmpfs", job="node", instance="{{ inventory_hostname }}"}[12h], 3 * 3600) < 0
|
||||
expr: predict_linear((min by (instance, mountpoint) (node_filesystem_free_bytes{fstype!~"tmpfs", job="node", instance="{{ inventory_hostname }}"}))[12h:1m], 3 * 3600) < 0
|
||||
for: 5m
|
||||
labels:
|
||||
severity: critical
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue