Classify cAdvisor startup noise
This commit is contained in:
@@ -95,3 +95,11 @@ monitoring-grafana.*grafana-amazonprometheus-datasource not found
|
||||
# Re-check: if the message references an existing/running container, if
|
||||
# Prometheus target health fails, or if broader cAdvisor errors appear.
|
||||
monitoring-cadvisor.*failed to collect filesystem stats.*var/lib/docker/containers/[0-9a-f]{64}
|
||||
|
||||
# cAdvisor startup lines that match the generic "oom" / "failed" grep.
|
||||
# Why: "oom_event" is a metric name printed during startup, and Unraid loop
|
||||
# devices can disappear while cAdvisor enumerates block devices.
|
||||
# Re-check: if cAdvisor target health fails or these messages appear outside
|
||||
# container startup together with missing container metrics.
|
||||
monitoring-cadvisor.*enabled metrics:.*oom_event
|
||||
monitoring-cadvisor.*stat failed on /dev/loop[0-9]+ with error: no such file or directory
|
||||
|
||||
Reference in New Issue
Block a user