From e745072dce8803b9fcbccf2ff01388938dae5e38 Mon Sep 17 00:00:00 2001 From: Dan Fuller Date: Fri, 16 Oct 2026 17:56:54 -0700 Subject: [PATCH 1/2] docs(php): Add Symfony Scheduler crons setup Co-Authored-By: Claude --- platform-includes/crons/setup/php.symfony.mdx | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 platform-includes/crons/setup/php.symfony.mdx diff --git a/platform-includes/crons/setup/php.symfony.mdx b/platform-includes/crons/setup/php.symfony.mdx new file mode 100644 index 0000000000000..b967247f646aa --- /dev/null +++ b/platform-includes/crons/setup/php.symfony.mdx @@ -0,0 +1,25 @@ +## Symfony Scheduler + + + +Symfony Scheduler monitoring ships in the next release of `sentry/sentry-symfony`. + + + +The Symfony SDK can monitor the recurring messages of the [Symfony Scheduler](https://symfony.com/doc/current/scheduler.html) 6.4 or later. It sends a check-in when a worker starts a recurring message, and another when the message finishes or fails. (Please note, this creates a Cron Monitor for every recurring message, which counts against your quota.) + +Enable it in your bundle configuration: + +```yaml {filename:config/packages/sentry.yaml} +sentry: + scheduler: + enabled: true +``` + +The monitor slug is the schedule name, a name for the message, and the ID that Symfony gives the recurring message, for example `default-app-send-report-1a2b3c4d`. The name is the command for scheduled console commands, the service and method for scheduled services, and the class name for other messages. The ID changes when the message or its schedule changes, which creates a new monitor. + +`RedispatchMessage` isn't monitored; the message it redispatches is monitored when a worker consumes it. Retried messages, cancelled runs, and messages of anonymous classes don't send check-ins. + +To monitor other jobs, send check-ins with the PHP SDK as shown below. + + From 238d8b32f19b999ae981ef1766941816e57e2e22 Mon Sep 17 00:00:00 2001 From: Dan Fuller Date: Tue, 20 Oct 2026 10:58:18 -0700 Subject: [PATCH 2/2] docs(php): Update the Symfony Scheduler monitor slug format Co-Authored-By: Claude --- platform-includes/crons/setup/php.symfony.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-includes/crons/setup/php.symfony.mdx b/platform-includes/crons/setup/php.symfony.mdx index b967247f646aa..c1a8dd85c8e03 100644 --- a/platform-includes/crons/setup/php.symfony.mdx +++ b/platform-includes/crons/setup/php.symfony.mdx @@ -16,7 +16,7 @@ sentry: enabled: true ``` -The monitor slug is the schedule name, a name for the message, and the ID that Symfony gives the recurring message, for example `default-app-send-report-1a2b3c4d`. The name is the command for scheduled console commands, the service and method for scheduled services, and the class name for other messages. The ID changes when the message or its schedule changes, which creates a new monitor. +The monitor slug is the schedule name and a name for the message, for example `default-app-send-report`. The name is the command for scheduled console commands, the service and method for scheduled services, and the class name for other messages. When recurring messages in the same schedule have the same name, the ID that Symfony gives each recurring message is added to their slugs. That ID changes when the message or its schedule changes, which creates a new monitor. `RedispatchMessage` isn't monitored; the message it redispatches is monitored when a worker consumes it. Retried messages, cancelled runs, and messages of anonymous classes don't send check-ins.