From 598d6779cd999ffba73c35ba17494669ddfbc140 Mon Sep 17 00:00:00 2001
From: Aleksandar Topuzovic <aleksandar.topuzovic@gmail.com>
Date: Tue, 14 Nov 2017 14:36:22 +0000
Subject: [PATCH] Alert on daemonset problems
* If any of the rules is active > 10m
* If all daemonsets are not ready
* If all daemonsets are not scheduled
* If some are miss scheduled
---
assets/prometheus/rules/kubelet.rules.yaml | 27 ++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/assets/prometheus/rules/kubelet.rules.yaml b/assets/prometheus/rules/kubelet.rules.yaml
index 1aa5f84c..03ea03da 100644
--- a/assets/prometheus/rules/kubelet.rules.yaml
+++ b/assets/prometheus/rules/kubelet.rules.yaml
@@ -47,3 +47,30 @@ groups:
description: Kubelet {{$labels.instance}} is running {{$value}} pods, close
to the limit of 110
summary: Kubelet is close to pod limit
+ - alert: K8SDaemonSetsNotScheduled
+ expr: kube_daemonset_status_desired_number_scheduled - kube_daemonset_status_current_number_scheduled
+ > 0
+ for: 10m
+ labels:
+ severity: warning
+ annotations:
+ description: A number of daemonsets are not scheduled.
+ summary: Daemonsets are not scheduled correctly
+ - alert: K8SDaemonSetsNotRunning
+ expr: kube_daemonset_status_desired_number_scheduled - kube_daemonset_status_number_ready
+ > 0
+ for: 10m
+ labels:
+ severity: warning
+ annotations:
+ description: A number of daemonsets are not ready.
+ summary: Daemonsets are not ready
+ - alert: K8SDaemonSetsMissScheduled
+ expr: kube_daemonset_status_number_misscheduled > 0
+ for: 10m
+ labels:
+ severity: warning
+ annotations:
+ description: A number of daemonsets are running where they are not supposed
+ to run.
+ summary: Daemonsets are not scheduled correctly
--
GitLab