Auto-upsert Sentry cron monitors for the tasks

[amureki]

Hey 👋

This PR mirrors voiio/dramatiq-crontab#186

Sentry introduced an ability to automatically create cron monitors in case the monitor config is provided along with the payload:
https://docs.sentry.io/platforms/python/crons/#configuring-cron-monitors

In case we are positive that Sentry is used within the project, instead of simply sending the signal, we can upsert the config right away to reduce the amount of manual work.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.85%. Comparing base (0a31c4f) to head (07694b3).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
+ Coverage   98.59%   98.85%   +0.25%     
==========================================
  Files           5        6       +1     
  Lines         142      174      +32     
==========================================
+ Hits          140      172      +32     
  Misses          2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Adds support for automatically upserting Sentry cron monitor configuration when sentry-sdk is available, reducing manual Sentry monitor setup for scheduled tasks.

Changes:

• Build and attach monitor_config (schedule + timezone) when wrapping tasks with sentry_sdk.crons.monitor.
• Add _monitor_config() helper to translate crontab strings and IntervalTrigger into Sentry cron config payloads.
• Extend tests to validate monitor_config is passed for crontab and interval schedules.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
crontask/__init__.py	Generates Sentry monitor configuration and passes it to monitor() when available.
tests/test_tasks.py	Adds tests/fixture to validate Sentry monitor_config integration for cron + interval schedules.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codingjoe]

Thanks @amureki, let's make this spectecular!

[codingjoe]

Sorry, I previously missed something.

[codingjoe]

@amureki FYI: https://discord.com/channels/621778831602221064/1496192154702315560

[codingjoe]

@amureki I chatted with sentry. This should be fine now. However, please be so kind and double check my amendment. Pretty cool idea. I stared working on something realed. Good things to come 😁

[amureki]

Awesome, thanks for wrapping it up! LGTM

[codingjoe]

@amureki I thought about this while sleeping. I think we need to disable the sentry checking, if it's based on an unsupported trigger. So not only no upsert, but no checking. You shouldn't have a monitor on those anyway. Especially if they are sub-minute, this would result in crazy telemetry overhead. Thoughts?

[amureki]

@amureki I thought about this while sleeping. I think we need to disable the sentry checking, if it's based on an unsupported trigger. So not only no upsert, but no checking. You shouldn't have a monitor on those anyway. Especially if they are sub-minute, this would result in crazy telemetry overhead. Thoughts?

That probably would make sense, yes. But would you still want to have it in the same PR or separately?

[codingjoe]

Na, let's get it right now. @amureki what do you think?