moritz/infrapuzzle
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

monitoring: optimize alerts and mitigate fritzbox-exporter timeouts

Browse Source
This commit is contained in:
Moritz Graf
2026-07-11 07:40:06 +02:00
parent c5458821a7
commit bdabc56afe
10 changed files with 269 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/n8n/n8n.secret.yml
+7 -7
View File
@@ -146,15 +146,15 @@ extraManifests:
rules:
- alert: n8nInstanceDown
expr: up{job="mop-n8n"} == 0
for: 5m
for: 1h
labels:
severity: critical
annotations:
summary: "n8n instance is down or unresponsive"
description: "n8n scraper has failed for the last 5 minutes. The application might be frozen or crashed."
description: "n8n scraper has failed for the last 1 hour. The application might be frozen or crashed."
- alert: n8nPodRestarts
expr: rate(kube_pod_container_status_restarts_total{container="n8n"}[15m]) * 900 > 1
for: 5m
for: 1h
labels:
severity: warning
annotations:
@@ -162,17 +162,17 @@ extraManifests:
description: "n8n has restarted in the last 15 minutes. This might indicate liveness probe failures due to database issues or memory limit exhaustion."
- alert: n8nNodeEventLoopLag
expr: n8n_nodejs_eventloop_lag_seconds{job="mop-n8n"} > 1
for: 5m
for: 1h
labels:
severity: warning
annotations:
summary: "n8n event loop lag is high"
description: "n8n Node.js event loop lag has exceeded 1 second for the last 5 minutes. This can make the UI unresponsive and logins fail."
description: "n8n Node.js event loop lag has exceeded 1 second for the last 1 hour. This can make the UI unresponsive and logins fail."
- alert: n8nPodNotReady
expr: kube_pod_status_ready{condition="true", pod=~"mop-n8n-.*"} == 0
for: 5m
for: 1h
labels:
severity: critical
annotations:
summary: "n8n pod is not ready"
description: "n8n pod has been in non-ready state for more than 5 minutes. This is likely due to failing readiness probes (/healthz check failing, possibly database connection issues)."
description: "n8n pod has been in non-ready state for more than 1 hour. This is likely due to failing readiness probes (/healthz check failing, possibly database connection issues)."