Kubernetes Job slow completion critical
>>>
kube_job_spec_completions
-
kube_job_status_succeeded
-
kube_job_status_failed
> 0
The rule subtracts the number of succeeded and failed pods from the total completions a Job is configured to run (kube_job_spec_completions). If the result is greater than 0, there are still pending pods, meaning the Job hasn’t finished within the expected time, which triggers the alert.
Exporters Used
Related Alerts
Kubernetes API client errors
Kubernetes API server errors
Kubernetes API server latency
Kubernetes Container oom killer
Kubernetes CronJob suspended
Kubernetes CronJob too long
Kubernetes DaemonSet misscheduled
Kubernetes DaemonSet rollout stuck
Kubernetes Deployment generation mismatch
Kubernetes Deployment replicas mismatch
Kubernetes HPA metrics unavailability
Kubernetes HPA scale inability
Kubernetes HPA scale maximum
Kubernetes HPA underutilized
Kubernetes Job failed
Kubernetes Job not starting
Kubernetes Node disk pressure
Kubernetes Node memory pressure
Kubernetes Node network unavailable
Kubernetes Node not ready
Kubernetes Node out of pod capacity
Kubernetes Node scheduling disabled
Kubernetes PersistentVolume error
Kubernetes PersistentVolumeClaim pending
Kubernetes Pod not healthy
Kubernetes ReplicaSet replicas mismatch
Kubernetes StatefulSet down
Kubernetes StatefulSet generation mismatch
Kubernetes StatefulSet replicas mismatch
Kubernetes StatefulSet update not rolled out
Kubernetes Volume full in four days
Kubernetes Volume out of disk space
Kubernetes client certificate expires next week
Kubernetes client certificate expires soon
Kubernetes pod crash looping