Symfony apps deserve monitoring beyond the homepage
Symfony isn’t a shop or a CMS, but the foundation of many custom applications and APIs. For such projects, it’s not just homepage reachability that counts, but also the expiry date of the certificate and domain as well as the health of background processing: Messenger workers and Scheduler tasks that can stall unnoticed.
The live24h bundle makes these risks tangible directly in your Symfony app. Important here: the bundle is a configuration helper, not a monitoring engine. It scans your app, shows a Website Health Score, suggests matching checks and creates them in live24h with a single click. The actual 24/7 checks then run on the live24h platform. The bundle is mounted at /admin/live24h (to be secured by the host behind a role and firewall); you’ll find the Health Center at /admin/live24h/health.
Where the bundle helps most
| Use case | live24h benefit |
|---|---|
| Custom app or API | Homepage, /robots.txt and sitemap are suggested as reachability checks. |
| Publicly reachable routes | Important endpoints are monitored systematically instead of at random. |
| TLS and domain | Certificate and domain expiry become checks – with timely warnings. |
| Messenger processing | Transports and workers can be protected as a heartbeat. |
| Scheduler tasks | Recurring tasks are monitored understandably as a worker heartbeat. |
| Mail sending | MX, SPF, DKIM and DMARC are made visible informationally. |
Benefits by audience
The focus is where outages become expensive in a Symfony app: on reachable routes, valid certificates and running workers. Everything stays plan-aware and visible – locked suggestions are marked “Pro and up” instead of being hidden.
- Symfony developers and teams: reachability, SSL, domain and workers are protected without a manual checklist – straight from the app.
- DevOps and operators: the same flow runs in the Health Center or headless via a console command and fits into existing deploy pipelines.
- Teams with background processing: Messenger transports and Scheduler tasks become part of operational monitoring, instead of only showing up when there’s a backlog.
- EU and GDPR customers: the ongoing checks are operated on the EU-hosted live24h platform.
- Agencies : monitoring becomes a repeatable standard across multiple Symfony apps.
A simple flow
- Store the API key in the Symfony project and test the connection.
- Open the Health Center at
/admin/live24h/healthor use the console command. - Analyse the app.
- Review the Website Health Score.
- Select the recommended checks.
- Create the checks in live24h with a single click.
- Enable alerts, Status Page and reports.
Installation and requirements
The bundle is available as a direct download from live24h and is installed via Composer:
composer require live24h/symfony-adapter
Then register the bundle in config/bundles.php, import the routing and secure the path /admin/live24h behind a role via security access_control. Requirements: Symfony 6.4 LTS and PHP 8.1 or newer as well as an outbound connection to https://api.live24h.eu. A listing in the Packagist marketplace will follow; the exact steps are described in the setup guide
.
Frequently asked questions
Is the bundle itself the monitoring engine? No. The bundle is a configuration helper: it scans the app, shows the Health Score and creates the recommended checks. The ongoing 24/7 checks are handled by the live24h platform.
Do I need a shop or a CMS? No. The bundle is intended for custom Symfony applications and APIs – with no commerce or CMS modules at all.
Can I monitor Messenger workers and the Scheduler? Yes. Messenger transports and Scheduler tasks are discovered at build time and can be protected as a worker heartbeat (dead man’s switch). This option is opt-in.
What does the bundle cost? Nothing – it’s included free in every live24h plan. The scope depends on the plan you’ve booked. Locked suggestions stay visible and are marked “Pro and up”.