Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job. Once implemented, it'll allow you to get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.


To begin monitoring your recurring, scheduled job:


The Sentry CLI uses your Monitor's

projectRepresents your service in Sentry and allows you to scope events to a distinct application.
DSNThe Data Source Name (DSN) key tells the Sentry SDK where to send events, ensuring they go to the right project.
to authorize check-ins. To set it up, export the SENTRY_DSN environment variable:

export SENTRY_DSN=

Alternatively, you can add it to your ~/.sentryclirc config:

dsn =

Learn more about the CLI's configuration file.

Job Monitoring

Use the Sentry CLI to run your job and notify you if it doesn't start when expected (missed) or if it exceeded its maximum runtime (failed).

sentry-cli monitors run <monitor_slug> -- <command> <args>

Usage examples:

sentry-cli monitors run my-monitor-slug -- python path/to/

Specifying Monitor Environments (Optional)

If your cron monitor runs in multiple environments you can use the -e flag to specify which Monitor Environment to send check-ins to.

sentry-cli monitors run -e dev my-monitor-slug -- node path/to/file.js
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").