Add Cron Monitor check-in data to Sentry Dashboards

Problem Statement

We use Sentry Cron Monitoring to track multiple scheduled jobs within the same Sentry project. In our case, one project contains many different cron jobs, each represented by a separate monitor slug.

Currently, we can see the status of each cron job in the Cron Monitoring view, for example whether a job is OK, Missed, Timed Out, or Failed. However, we cannot build a single Sentry Dashboard widget that shows all cron monitors together and groups them by monitor slug.

What we need is a central dashboard overview where we can quickly answer:

Which cron jobs ran successfully?

Which cron jobs were missed?

Which cron jobs timed out?

Which cron job belongs to the problem?

Is everything healthy across all scheduled jobs in this project?

At the moment, the available dashboard datasets include Errors, Spans, Logs, Application Metrics, Issues, Releases, etc., but Cron Monitor check-in data does not seem to be available as a dashboard dataset. This means we cannot group or filter dashboard widgets by fields such as monitor.slug, check-in status, schedule, or runtime.

Because of this, teams have to either check the Cron Monitoring page manually monitor by monitor, or build an external custom dashboard using the Sentry API. This makes it harder to provide a shared operational overview for non-technical users and support teams.

It would be very helpful if Sentry Dashboards supported Cron Monitoring data directly, for example with widgets such as:

Cron monitor status table grouped by monitor slug

Count of OK, Missed, Timed Out, and Failed check-ins

Runtime trends per monitor

Filters for project, environment, monitor slug, and schedule

A health overview showing whether all scheduled jobs are currently running correctly

This would allow teams to use Sentry as a single central monitoring dashboard for scheduled jobs, not only for application errors and issues.

Solution Brainstorm

No response

Product Area

Unknown

No files, tests, or entry points are named. Start by locating the dashboard dataset and widget implementations, then trace how Cron Monitoring check-in data is represented. Done should include dashboard access to monitor slugs and check-in statuses, with the requested grouping and filtering behavior covered by tests.