---
title: "Sentry monitors"
manual: "Sentry Cron Monitor"
version: "2.2"
permalink: "https://docs.typo3.org/permalink/andersundsehr/sentry_cron_monitor:sentry-monitors@2.2"
source: "Usage/SentryMonitors.rst"
rendered: "2026-11-19T20:48:19+00:00"
---

# Sentry monitors {#sentry-monitors}

The extension creates a Sentry cron monitor for each TYPO3 Scheduler task.
Existing and newly added tasks require no task-specific Sentry code.

## Monitor identity {#monitor-identity}

For Scheduler tasks that execute console commands, the extension combines and
normalizes the command identifier and task UID before sending a check-in to
Sentry:

```text
<normalized-command-identifier>-uid-<task UID>
```

For example:

```text
aus-projectcenter-sync-absences-to-outlook-uid-26
```

Failures for this monitor appear in Sentry as:

```text
Cron failure: aus-projectcenter-sync-absences-to-outlook-uid-26
```

Other Scheduler task types use their normalized task title instead of a command
identifier. The UID distinguishes otherwise identical tasks. Renaming a task or
command changes the slug and can leave the previous monitor in Sentry.

## Schedule mapping {#schedule-mapping}

-   **Cron schedule**

    The extension passes a Scheduler cron expression to Sentry unchanged.

-   **Interval schedule**

    The extension converts the interval from seconds to whole minutes and
    rounds up. For example, 90 seconds becomes a two-minute Sentry schedule.

The configured [Configuration reference](https://docs.typo3.org/permalink/andersundsehr/sentry_cron_monitor:configuration-timezone@2.2) tells Sentry how to interpret the
monitor schedule.

## Alerts {#alerts}

Before each monitored run, the extension checks whether the matching Sentry
issue alert rule exists. It creates the rule when necessary. The rule sends
matching production failures to the configured Microsoft Teams channel.

## Muted monitors {#muted-monitors}

Use the Production-only [Delete muted cron monitors](https://docs.typo3.org/permalink/andersundsehr/sentry_cron_monitor:delete-muted-monitors-command@2.2) to preview or
delete muted cron monitors in the configured Sentry project. You can also run
the cleanup automatically as a TYPO3 Scheduler console-command task.
