Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions Documentation/Usage/SentryMonitors.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,7 @@ Sentry monitors
===============

The extension creates a Sentry cron monitor for each TYPO3 Scheduler task.
Starting a task manually in the TYPO3 Scheduler backend creates an additional
monitor instead of using the monitor for scheduled executions. Running the task
with ``scheduler:execute`` uses the scheduled monitor. Existing and newly added
tasks require no task-specific Sentry code.
Existing and newly added tasks require no task-specific Sentry code.

Monitor identity
================
Expand Down
15 changes: 0 additions & 15 deletions Documentation/Usage/TaskExecution.rst
Original file line number Diff line number Diff line change
Expand Up @@ -25,21 +25,6 @@ A developer or operator can run one configured Scheduler task by UID:

vendor/bin/typo3 scheduler:execute --task=<task-uid>

``scheduler:run`` and ``scheduler:execute`` use the same Sentry monitor for the
same task.

Manual execution in the TYPO3 backend
=====================================

Starting a task manually in the TYPO3 Scheduler backend creates an additional
Sentry cron monitor instead of using the monitor for its scheduled executions.

.. important::

The extension monitors a console command only when it runs as a configured
TYPO3 Scheduler task. Running a Symfony command directly does not pass
through this extension.

Check-in results
================

Expand Down