Kubernetes CronJob too long warning
>>>
kube_job_status_start_time
> 0 and
absent
(
kube_job_status_completion_time
) and (
time
() -
kube_job_status_start_time
) > 3600
The alert fires when a CronJob has a Job with kube_job_status_start_time > 0, no kube_job_status_completion_time (i.e., the Job is still running), and the elapsed time (time() - kube_job_status_start_time) exceeds 3600 seconds (1 hour). In that case the CronJob is considered to be taking too long.
Exporters Used
Related Alerts
Kubernetes API client errors
Kubernetes API server errors
Kubernetes API server latency
Kubernetes Container oom killer
Kubernetes CronJob suspended
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 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