Drupal sites deserve monitoring with structure
Drupal is often used where content and reachability count: editorial portals, association and government sites, universities, multi-domain projects and agency-maintained installations. The live24h Health Center makes monitoring tangible for exactly that – directly in the Drupal backend under Reports → live24h Health Center.
Important to understand: the module is a configuration helper, not a monitoring engine. It scans your site, shows a Website Health Score, suggests matching checks and creates them in live24h with a single click. The ongoing 24/7 checks then run on the live24h platform from multiple regions – not on your Drupal installation.
Where the Health Center helps most
| Use case | live24h benefit |
|---|---|
| Editorial content site | Homepage, robots.txt, sitemap and indexability are monitored systematically. |
| Portal or government site | SSL, domain, DNS and reachability give a traceable operational baseline. |
| Multi-domain project | SSL, domain and DNS signals are protected in a structured way per live domain. |
| Active cron and queue operation | Cron hooks and queue workers are monitored as a heartbeat instead of stopping silently. |
| Transactional emails | MX, SPF, DKIM and DMARC become a visible monitoring topic. |
| Relaunch or deployment | Critical pages and SEO signals are verifiable right after go-live. |
Benefits by audience
- Site operators and admins see at a glance how well their Drupal site is protected and create the most important checks in a few minutes.
- Editorial and content sites protect homepage, sitemap and indexability so content stays reachable and discoverable.
- Operators with active cron or queues make background processes visible with a heartbeat, instead of learning about silent stops weeks later.
- Agencies and maintainers set up monitoring right after project handover and deliver a repeatable operational baseline per client.
- EU and GDPR customers benefit from the ongoing checks running EU-hosted on the live24h platform.
Note for shop projects: Drupal core is a CMS without commerce. A dedicated commerce area is therefore hidden and not shown as a locked suggestion.
A simple flow
- Store the API key in the Drupal module and test the connection.
- In the backend, open Reports → live24h Health Center.
- Analyse the site (scan).
- Review the Website Health Score.
- Select the recommended checks – locked suggestions stay visible and are marked “Pro and up”.
- Create the checks in live24h with a single click.
Installation and requirements
The module is installed via Composer and then enabled:
composer require live24h/drupal-adapter
drush en live24h_health_center
Alternatively, enable the module via the module list in the backend. You’ll find the settings under Configuration → Services → live24h Health Center.
Requirements: Drupal 10 or 11, PHP 8.1 to 8.3 and an outbound connection to https://api.live24h.eu. The module is available now as a direct download from live24h; a listing on drupal.org will follow.
Frequently asked questions
Does the module run the monitoring itself? No. The module is a configuration helper: it scans the site and creates checks. The ongoing 24/7 monitoring is handled by the live24h platform from multiple regions.
Does the module support Drupal Commerce? Drupal core is a CMS without a shop, so the commerce area is hidden. The focus is on pages/SEO, SSL/domain/DNS, mail deliverability and a cron and queue heartbeat.
What does the module cost? Nothing – it’s included free in every live24h plan. The scope of the checks depends on the plan you’ve booked.
Can I monitor cron and queues? Yes. Drupal cron hooks and queue workers can be protected as a heartbeat so silent background stops are noticed in time.