You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(docker-stats,podman-stats): replace per-container perfdata with aggregates
- Remove per-container cpu_usage and mem_usage perfdata (too dynamic,
containers come and go)
- Add aggregate perfdata: containers_running, cpu
- podman-stats: switch to JSON output via podman stats --format
'{{json .}}' for precise numeric values; add block_input,
block_output, images, net_rx, net_tx, ram perfdata
- Use CRIT (not UNKNOWN) on return codes != 0 across all four plugins
- Align States section in all READMEs
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,8 @@ Monitoring Plugins:
132
132
* by-ssh: add missing `--verbose` parameter
133
133
* cpu-usage: fix false 100% readings on Windows with 64+ cores caused by all-zero CPU time samples from psutil ([#626](https://github.com/Linuxfabrik/monitoring-plugins/issues/626))
134
134
* docker-stats: fix memory perfdata using CPU thresholds instead of memory thresholds
135
+
* docker-stats: replace per-container perfdata with aggregate metrics (containers, cpu)
136
+
* podman-stats: use `podman stats --format '{{json .}}'` for precise numeric values; aggregate perfdata includes block I/O and network I/O totals
135
137
* file-age: handle `FileNotFoundError` race condition when files disappear on busy file systems
Copy file name to clipboardExpand all lines: check-plugins/docker-stats/README.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,19 +83,20 @@ myconti_ds_1 ! 0.0 ! 11.42
83
83
84
84
## States
85
85
86
-
Alerts if
86
+
* CRIT on `docker info` or `docker stats` return codes != 0
87
+
* WARN if any container cpu usage is above the warning cpu threshold during the last n checks (default: 5)
88
+
* CRIT if any container cpu usage is above the critical cpu threshold during the last n checks (default: 5)
89
+
* WARN or CRIT if any container memory usage is above the memory thresholds
87
90
88
-
* any container memory usage is above the memory thresholds
89
-
* any container cpu usage is above the cpu thresholds during the last n checks (default: 5)
91
+
CPU usage is normalized by dividing by the number of host CPUs, so 100% means all host CPUs are fully utilized. On an 8-core system, a container using one core at full capacity would show 12.5%. Memory usage is relative to the container's memory limit if one is set, otherwise relative to the total host memory.
Copy file name to clipboardExpand all lines: check-plugins/podman-stats/README.md
+15-8Lines changed: 15 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,19 +84,26 @@ myconti_ds_1 ! 0.0 ! 11.42
84
84
85
85
## States
86
86
87
-
Alerts if
87
+
* CRIT on `podman info` or `podman stats` return codes != 0
88
+
* WARN if any container cpu usage is above the warning cpu threshold during the last n checks (default: 5)
89
+
* CRIT if any container cpu usage is above the critical cpu threshold during the last n checks (default: 5)
90
+
* WARN or CRIT if any container memory usage is above the memory thresholds
88
91
89
-
* any container memory usage is above the memory thresholds
90
-
* any container cpu usage is above the cpu thresholds during the last n checks (default: 5)
92
+
CPU usage is normalized by dividing by the number of host CPUs, so 100% means all host CPUs are fully utilized. On an 8-core system, a container using one core at full capacity would show 12.5%. Memory usage is relative to the container's memory limit if one is set, otherwise relative to the total host memory.
0 commit comments