Skip to content

Commit

Permalink
refactor(alerts): make clear what replicamismatch alerts mean (#536)
Browse files Browse the repository at this point in the history
* refactor(alerts): make clear what replicamismatch alerts mean

Specifically mentioning that it is around the number of ready pods not
being what the desired count is should make it more clear, atleast to
me!

* single line -> multiple lines
  • Loading branch information
Harry Waye authored Aug 22, 2022
1 parent 75a3b7a commit 9395d52
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions charts/posthog/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1488,7 +1488,9 @@ prometheus:
severity: warning
annotations:
summary: Kubernetes ReplicasSet mismatch (instance {{ $labels.instance }})
description: "Deployment Replicas mismatch"
description: >
The number of ready pods in the Deployment's replicaset does
not match the desired number.
- alert: KubernetesDeploymentReplicasMismatch
expr: kube_deployment_spec_replicas != kube_deployment_status_replicas_available
Expand All @@ -1497,7 +1499,9 @@ prometheus:
severity: warning
annotations:
summary: Kubernetes Deployment replicas mismatch (instance {{ $labels.instance }})
description: "Deployment Replicas mismatch"
description: >
The number of ready pods in the Deployment does not match the
desired number.
- alert: KubernetesStatefulsetReplicasMismatch
expr: kube_statefulset_status_replicas_ready != kube_statefulset_status_replicas
Expand All @@ -1506,7 +1510,9 @@ prometheus:
severity: warning
annotations:
summary: Kubernetes StatefulSet replicas mismatch (instance {{ $labels.instance }})
description: "A StatefulSet does not match the expected number of replicas."
description: >
The number of ready pods in the StatefulSet does not match the
desired number.
- alert: KubernetesDeploymentGenerationMismatch
expr: kube_deployment_status_observed_generation != kube_deployment_metadata_generation
Expand Down

0 comments on commit 9395d52

Please sign in to comment.