Automated Percona Database Health Alerts
Every few minutes, WebRun checks your Percona Monitoring and Management dashboards for replication lag or slow query alerts crossing the threshold you set, and the moment one fires it texts the on-call DBA through Twilio with the database and the figure, then saves the alert detail to Google Drive so the incident has a written record from the start.
How do I get texted immediately when a monitored database has a problem?
WebRun checks your Percona Monitoring and Management dashboards every few minutes for replication lag or slow query alerts. The moment one crosses the threshold you set, it texts the on-call DBA through Twilio with the database and the figure, and saves the alert to Google Drive, so a database issue gets a person's attention within minutes.
- Database issues get a text within minutes instead of being found at the next check
- Every alert has a saved record instead of a lost dashboard notification
- Repeat incidents on the same database are easy to spot in the archive
Built for Database administrators · Site reliability teams · Data platform engineers · On-call engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
percona.comin a real browser with your saved login - no setup, no API keys. -
1
Percona - check database health alerts
percona.com
WebRun opens Percona to check database health alerts. - Open Percona Monitoring and Management and check active alerts across monitored databases
- Read replication lag and slow query alerts against the thresholds you set
- Capture the database, the metric, and the current figure
Done when Every active alert has been captured with its detail.
-
2
Twilio - text the on-call DBA
twilio.com
WebRun opens Twilio to text the on-call DBA. - Text the on-call DBA naming the database and the alert
- Include the current figure against the threshold
- Send only while the alert is still active
Done when The on-call DBA has been texted for this alert.
-
3
Google Drive - save the alert record
drive.google.com
WebRun opens Google Drive to save the alert record. - Save the alert detail to the database incidents folder
- Name the file with the database and the date
- Keep prior alerts in place for pattern review
Done when This alert's record is saved to Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun fix the database issue itself?
No. It only detects and reports the alert. Investigating replication lag or a slow query stays with your on-call DBA.
What counts as an alert worth texting about?
Whatever thresholds you have set in Percona Monitoring and Management for replication lag and query performance. Nothing is texted until an alert actually fires.
Will we get repeated texts for the same ongoing issue?
No. It texts once when the alert fires, then again only if it clears and fires a second time, so Twilio does not fill up with repeats of the same open incident.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.