Skip to content
Nicoloye edited this page Jun 17, 2015 · 1 revision

Expressed fonctional needs:

Return informations about the system status & health with:

  • the fewer manual operation possible,
  • the minimum system requirements on the production environment
  • minimal impacts on the website lifecycle and performance.

Here is a draft list of awaited features as described in the "Preventive maintenance" meeting on 17th june 2015:

  • Core status (current version and last version comparison, applied patches, reason of these patches and warnings about updates)
  • Contrib modules (current version and last version comparison, applied patches, reason of these patches and warnings about updates)
  • Custom modules (description of the module behavior and contrib version dependencies for it to work as expected)
  • Periodical process status and statistics (cron tasks, queues processes)
  • Repository status (current branch or tag, local changes, maybe deployment features)
  • 404 and 500 errors summary
  • Watchdog summary (size of the watchdog file or DB, main entries categories, etc)
  • Display changes (through some plugin to grab any layout regression)
  • Backup features (incremental backup and backup validity checks)
  • Performances checks (load tests and performance stats)
  • Notification on trigger system (allowing for example to send a mail on a 404 or php error)

Technical implementation

Currently we designed a json structure that has already been modified a bit (not pushed yet) and a structure based on ctools plugins to allow the main module extension, this is subject to discussion.