Sentry Cron Monitoring is currently in open beta and subject to change. Help us make it better by letting us know what you think. Respond on GitHub or write to us at firstname.lastname@example.org.
Starting with v2.16.1 of the Sentry CLI, the ability to monitor check-ins using an auth
tokenIn search, a key-value pair or raw search term. Also, a value used for authorization.
for authorization has been deprecated. Read on to learn how to update your CLI and use your
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.
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:
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>
sentry-cli monitors run my-monitor-slug -- python path/to/file.py
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").