This project is not covered by Drupal’s security advisory policy.
Multisite Status Dashboard aggregates the health of many Drupal sites into one screen. It polls remote sites that run the Multisite Status Report module, then shows their Drupal version, pending security releases, available updates, PHP version and cron status at a glance — so you can spot the site that needs attention immediately.
Features
- Single fleet overview: one table with a per-site status badge (green / amber / red), Drupal core version and update status, number of security updates, number of available updates, PHP version, last cron run and when the data was last checked.
- Managed sites as configuration entities: add, edit and remove monitored sites through the UI; definitions are exportable with your configuration.
- Secure HMAC client: each request to a remote site is signed locally with that site's shared secret using
HMAC-SHA256; the secret is never sent over the wire, matching the verification done by Multisite Status Report. - Background polling: data is fetched on cron through a queue and cached, keeping the dashboard fast and resilient. A Refresh now button triggers an immediate update via the Batch API.
- Clear failure reporting: unreachable sites or sites that never returned data are highlighted, with the last error preserved for context.
- Core-only and lightweight: built on Guzzle (already in core), the key/value store, queue and Batch APIs — no external services.
Use it when you run or maintain several Drupal sites and want a centralized, always-current picture of which ones are out of date or insecure, without logging in to each one.
Post-Installation
- Install and enable Multisite Status Report on each site you want to monitor, and note its key identifier and shared secret.
- On the central site, go to Administration → Configuration → Web services → Multisite Status Dashboard → Monitored sites (
/admin/config/services/multisite-status-dashboard/sites) and add each remote site with its base URL (HTTPS), key identifier and secret. - Open the dashboard at Administration → Reports → Multisite status (
/admin/reports/multisite-status). - Let cron populate the data, or click Refresh now for an immediate fetch.
Fetched results are stored in the key/value store (not in configuration), so volatile runtime data is never written to your exported config. Because the per-site secret is stored in configuration, consider overriding it in settings.php or using Config Ignore/Split for production.
Additional Requirements
Drupal core only. Each monitored site must run the Multisite Status Report module and be reachable over HTTPS from the dashboard site.
Recommended modules/libraries
- Multisite Status Report — required on every monitored site; this dashboard consumes its endpoints.
- Config Ignore / Config Split — to keep per-site secrets out of shared configuration.
Similar projects
Site Guardian (with its dashboard client) provides comparable fleet monitoring but relies on URL-key authentication. Multisite Status Dashboard pairs with Multisite Status Report's header-based HMAC signing, so secrets never appear in URLs, and stores monitored sites as exportable configuration entities.
Supporting this Module
Issue reports, feature requests and patches are welcome in the project's issue queue. Sponsorship links can be added here.
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.- Project categories: Administration tools, Developer tools, Security
- Created by fkatsukawa on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
