Moodle™ fleet monitoring
Know about problems before your users do.
Your Moodle site checks itself only when someone looks. Sentinel watches it continuously — from the outside and the inside — and tells you the moment something needs attention.
5-minute setup · no agents on your server · cancel any time
from: Sentinel <alerts@…> · 02:14
⚠ learn.brightpath.org — site down
Unreachable since 02:11 (3 consecutive failures). We'll tell you when it recovers.
How it works
Five minutes. No agents, no firewall changes.
Install the free plugin
Install the open-source Sentinel plugin (local_sentinel, GPLv3) on your Moodle site — it's useful on its own, and you control exactly what data is shared.
Paste one connection code
We send you a one-line provisioning code. Paste it into the plugin's Connect page — that's the whole setup.
We start watching
Uptime checks every 5 minutes, full health snapshots on a schedule, alerts the moment something changes — and a weekly report in your inbox.
Why monitoring, not just a plugin
A plugin can answer. Only a service can notice.
The free Sentinel plugin shows you everything about your site — when you load the page. Four things can't be delivered from inside the site at all:
01 / AttentionSomeone is watching at 2am
Everything the plugin can tell you exists only when someone loads the page. Nobody loads an admin page at 2am, on vacation, or during the week a TLS certificate quietly expires. Sentinel's product is noticing — it works when no one is paying attention.
02 / Vantage pointWatching from the outside
A plugin runs inside the site — when the site is down, the plugin is down with it. Uptime, response time, "down since 3:12am", maintenance-vs-outage classification: these are impossible locally, not withheld.
03 / MemoryRemembering what changed
Every plugin page load is amnesiac. Trends, uptime percentages, "what changed since last month", a record you can show an auditor — Sentinel remembers; a plugin sees only now.
04 / ContextKnowledge beyond your site
Security-release classification, PHP/database/OS end-of-life dates, Moodle release requirements, your whole fleet on one page — and a human organization watching it for you, accountable for it.
"The plugin is a blood-pressure cuff; the service is the cardiologist who checks the readings daily and calls you."
What you get
Everything that should wake someone up — and nothing that shouldn't.
Security currency
You'll know as soon as your site is behind on a Moodle security release. Same for expiring TLS certificates, stalled cron, and failing backups.
Uptime, done honestly
Checks every 5 minutes, with maintenance windows correctly excluded — an alert, not a surprise, when the site goes down at 2am.
Stack end-of-life
PHP, database, and operating system lifecycles tracked against published end-of-life dates — you hear about it months before it's urgent.
A weekly report you'll read
Uptime, security status, pending updates, active-user numbers, backups, certificates, and everything that changed that week. If you answer to a board or an auditor, this is the page you forward.
Alerts that resolve themselves
When an issue clears, you're told that too. No dashboards to babysit, no noise — email only when something changes.
You control the data
Operational facts only — versions, check results, counts. No course content, no user names or emails, and you can withhold any category from sharing.