Kubernetes Job not starting warning
>>>
kube_job_status_active
== 0 and
kube_job_status_failed
== 0 and
kube_job_status_succeeded
== 0 and (
time
() -
kube_job_status_start_time
) > 600
The alert triggers when a Kubernetes Job exists but its kube_job_status_active, kube_job_status_failed, and kube_job_status_succeeded metrics are all zero and the job's start time is more than 600 seconds ago, indicating the job has not started within the first 10 minutes after creation.
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 slow completion
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