Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

London hackfest April 2017 - Live monitoring moodle sites

From MoodleDocs
Revision as of 13:35, 10 April 2017 by Tim Hunt (talk | contribs) (Created page with "Part of London hackfest April 2017. ==How do people monitor their live Moodle sites?== Some of those present shard how they monitor their live Moodle site, or do load-te...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Part of London hackfest April 2017.

How do people monitor their live Moodle sites?

Some of those present shard how they monitor their live Moodle site, or do load-testing before upgrades.

A lot of Nagios, but also some other things like ???.

There are at least two plugins for make more information from Moodle available in Nagios: https://moodle.org/plugins/tool_heartbeat & https://github.com/University-of-Strathclyde-LTE-Team/moodle-local_nagios.

A lot of people have moved from original MySQL to clones like Maria DB or Percona. Others use Postgres.

Most people doing load-testing seem to be using JMeter. There are scripts that can generate a JMeter script for users interacting with a particular course. A weakness is that JMeter only does the original PHP/HTML load + images, CSS & JS. It will not simulate any HTTP requests that are done by AJAX. You need to script those manually to get a realistic test.

It turns out that having JMeter to simulate realistic load is useful when you need to investigate & reproduce why your Moodle site crashed ...

How has your Moodle site crashed?

The above discussion also involved people sharing their horror stories of when your Moodle site crashed.

Better monitoring for web services