Monitoring multiple Drupal sites for core, module, and theme security status
Some general health monitoring would be nice but we’re using a couple uptime checkers, Monit and the proprietary (but no-cost for light use) Uptime Robot service to get the most basic “is my site up” info.
The real need Agaric has is to know which modules are installed on each site without having to keep a manual list of them. We were moving toward having everything built on a Drutopia base, which is another solution: So long as our various codebases, just a handful of different ones, are up-to-date security-wise, then all the sites are. But then we picked up several Drupal 7 maintenance projects, and the previous system (manual lists and just knowing what modules we’ve installed )
I knew i’d read about it before, and fortunately it is being maintained (new 2019 release) and improved (the big ones from 2017):
Drupal Remote Dashboard, https://www.drupal.org/project/drd
And such comprehensive, on-Drupal.org, documentation!
https://www.drupal.org/docs/8/modules/drupal-remote-dashboard/getting-started-0/first-installation
With https://www.drupal.org/project/drd_agent being the module that goes on D6, D7, and D8 sites that are being monitored.
Also-rans, that unfortunately are easier to find:
- https://www.drupal.org/project/monitoring - promises to be a comprehensive system but very much piece it together yourself approach, with some parts you need to implement yourself, and not good enough documentation for me to even be sure how much we would have to implement ourselves. I think the main issue is it’s geared for pulling all sorts of information from your Drupal site, not actually seeing this info in some central location. I’m not opposed to its philosophy, that an established monitoring tool should be used for that, but… a Drupal-to-Drupal solution (or any central monitoring solution that’s not “figure it out yourself”) sure is attractive
- Warden: https://www.drupal.org/project/warden on sites and https://github.com/teamdeeson/warden on a central server. This seems great also, maybe it’s the perfect balance between DRD simplicity and Monitoring sensible structure.
- drupal.org/project/dashboard_connector but years after the blog announcing it key parts are not released (as Free Software or, for that matter, at all)
- drupal.org/project/module_status - extra info about the issues from Drupal issue queues potentially affecting your site (meant for one site at a time)
Another possibility occurs (to wolcen) to use the report functionality (ahem…nearly completed!) in drutopia_hosting [it iterates all the sites on each server and slurps up version and other info from each], along with this drush module https://github.com/liip/LiipDrushVersionManagerCommand which performs the version checking to determine out of date modules. Unfortunate it seems drush pm routines used to do this and seem not to any longer.