andersundsehr / sentry_cron_monitor

2.1.3 2026-09-01 12:52 UTC

Requires

• php: ~8.3.0 || ~8.4.0 || ~8.5.0
• sentry/sentry: ^4.15.2
• typo3/cms-core: ^13.4 || ^14.3
• typo3/cms-scheduler: ^13.4 || ^14.3

Requires (Dev)

• phpunit/phpunit: ^12.5.33
• pluswerk/grumphp-config: ^10.1.3 || ^11
• saschaegerer/phpstan-typo3: ^2.1.1 || ^3.1.0
• ssch/typo3-rector: ^3.6.2
• typo3/testing-framework: ^9.6.1

GPL-2.0-or-later

Published on Packagist.org on 2026-09-01 12:53 UTC

README

What does this extension do?

When a scheduler task runs:

• It will create a monitor and an alert in Sentry for the given scheduler task if there is none yet.
• It will send a check-in status to Sentry to indicate whether the task was successful or not.
• If the task fails, it will send a status error to Sentry, and the alert (only in Production) from the cron monitor will send a notification to the configured Microsoft Teams channel. Example:

Requirements

• Microsoft Teams Integration in Sentry + add App to (standard) Channel to get $integrationIdMsTeams in Sentry: Microsoft Teams integration

• Successful Integration in Channel:

  

• ⚠️ The first channel must always be named General; otherwise, it will not work! All other channels created after the first one can be given any name.

Extension Configuration

1. Integration ID for Microsoft Teams in Sentry: $integrationIdMsTeams
   • You can get this from the URL of the Microsoft Teams Integration in Sentry when you hover over Configure.
2. Organization Name in Sentry: $orgName
3. Name of the Microsoft Teams channel for notifications: $teamsChannelName
4. Authorization token for the Sentry API: $authToken
   • You can create this token in the User Auth Tokens in Sentry.
   • Make sure to grant read and write permissions to alerts.
5. Timezone for cron monitors: $timezone
   • Example: Europe/Berlin

Tip

• If a cron monitor is triggering too many false positives, increase the failure tolerance in Sentry.

Documentation

The complete documentation is available in the TYPO3 documentation.