SigNoz
Docs
PricingCustomers
Get Started - Free
Docs
IntroductionContributingMigrate from DatadogSigNoz API
OpenTelemetry
What is OpenTelemetryOpenTelemetry Collector GuideOpenTelemetry Demo
Community
Support
Slack
X
Launch Week
Changelog
Dashboard Templates
DevOps Wordle
Newsletter
KubeCon, Atlanta 2025
More
SigNoz vs DatadogSigNoz vs New RelicSigNoz vs GrafanaSigNoz vs Dynatrace
Careers
AboutTermsPrivacySecurity & Compliance
SigNoz - Open Source Datadog Alternative
SigNoz
All systems operational
HIPAASOC-2
SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

Kubernetes CronJobs Dashboard

This dashboard provides current state and recent run visibility for Kubernetes CronJobs and the Jobs they create. It uses metrics emitted by the k8sclusterreceiver so it works with any Kubernetes distribution.

To use this dashboard, install K8s Infra in your cluster so the cluster collector emits CronJob and Job metrics. Follow the Install K8s Infra guide. For a complete CronJob monitoring walkthrough that includes a sample CronJob, see Monitor Kubernetes CronJobs.

Dashboard Preview

Kubernetes CronJobs Dashboard
Kubernetes CronJobs Dashboard

Dashboards → + New dashboard → Import JSON

What This Dashboard Monitors

This dashboard is split into two areas:

  • Current state: the Jobs Kubernetes still keeps in the cluster (controlled by successfulJobsHistoryLimit and failedJobsHistoryLimit on the CronJob)
  • Recent runs: the Job executions SigNoz observed during the selected time range

Current State

  • Current Active CronJob Count: number of CronJobs with at least one active Job right now
  • Current Successful, Failed, Desired Success, and Max Parallel Pod Counts: per-Job pod state aggregated across the selected scope
  • Current Job Status: time-series view of active CronJobs vs successful and failed pods
  • Current Desired Success vs Parallel Limit: scheduling constraints applied to currently kept Jobs
  • Current Active, Successful, and Failed Pods by Job: per-Job breakdown of pod state
  • Current Desired Success vs Parallel Limit by Job: per-Job scheduling constraints

Recent Runs in Selected Time Range

  • Job Run Count: total Job runs SigNoz observed
  • Successful Job Run Count: Jobs that completed at least one successful pod
  • Failed Job Run Count: Jobs that recorded at least one failed pod
  • Peak Concurrent Job Count: the highest number of CronJob runs seen at the same time
  • Recent Job Run Details: per-Job table with successful pods, failed pods, desired successful pods, max parallel pods, and the latest sample timestamp

Metrics Used

The dashboard uses these metrics from the k8sclusterreceiver:

  • k8s.cronjob.active_jobs: active Jobs for a CronJob
  • k8s.job.active_pods: active pods for a Job
  • k8s.job.successful_pods: successfully completed pods for a Job
  • k8s.job.failed_pods: failed pods for a Job
  • k8s.job.desired_successful_pods: desired successful pod count for a Job
  • k8s.job.max_parallel_pods: maximum parallel pod limit for a Job

Dashboard Variables

This dashboard includes four hierarchical variables for filtering:

  • k8s.cluster.name: filter by Kubernetes cluster (multi-select)
  • k8s.namespace.name: filter by namespace (multi-select, depends on cluster)
  • k8s.job.name: filter by Job execution name (multi-select, depends on cluster and namespace)
  • k8s.cronjob.name: filter by CronJob name (multi-select, depends on cluster and namespace)

Use k8s.cronjob.name to look across all runs for one CronJob, and k8s.job.name to focus on one specific execution.

Related Dashboards

  • Kubernetes Cluster Metrics
  • Kubernetes Pod Metrics (Detailed)
  • Kubernetes Node Metrics (Detailed)

Last updated: May 27, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.

Prev
Kubernetes Node Metrics (Detailed)
Next
Key Operations
On this page
Dashboard Preview
What This Dashboard Monitors
Current State
Recent Runs in Selected Time Range
Metrics Used
Dashboard Variables
Related Dashboards

Is this page helpful?

Your response helps us improve this page.