Skip to content

Commit a1a9eda

Browse files
Artur Rodriguesarturhoo
authored andcommitted
Clarify pod status in useful queries
Signed-off-by: Artur Rodrigues <[email protected]>
1 parent fecc78f commit a1a9eda

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/pod-metrics.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,17 +67,17 @@ For example:
6767

6868
* For Pods in `Terminating` state: `count(kube_pod_deletion_timestamp) by (namespace, pod) * count(kube_pod_status_reason{reason="NodeLost"} == 0) by (namespace, pod)`
6969

70-
Here is an example of a Prometheus rule that can be used to alert on a Pod that has been in the `Terminated` state for more than `5m`.
70+
Here is an example of a Prometheus rule that can be used to alert on a Pod that has been in the `Terminating` state for more than `5m`.
7171

7272
```yaml
7373
groups:
7474
- name: Pod state
7575
rules:
76-
- alert: PodsBlockInTerminatingState
76+
- alert: PodsBlockedInTerminatingState
7777
expr: count(kube_pod_deletion_timestamp) by (namespace, pod) * count(kube_pod_status_reason{reason="NodeLost"} == 0) by (namespace, pod) > 0
7878
for: 5m
7979
labels:
8080
severity: page
8181
annotations:
82-
summary: Pod {{$labels.namespace}}/{{$labels.pod}} block in Terminating state.
82+
summary: Pod {{$labels.namespace}}/{{$labels.pod}} blocked in Terminating state.
8383
```

0 commit comments

Comments
 (0)