Automated Materialize Replication Lag Alerts
Every few minutes, WebRun opens the Materialize console, checks the replication lag on every tracked source and materialized view against the limit you set, and the moment one falls behind it pings the on-call engineer on WhatsApp with the source and the lag figure, then books a short incident review on Google Calendar for the team.
How do I get alerted when Materialize replication lag crosses a limit?
WebRun checks replication lag on your Materialize sources and views every few minutes against the limit you set. The moment one falls behind, it pings the on-call engineer on WhatsApp with the source and the lag figure, then books a short incident review on Google Calendar, so a stale materialized view gets caught before anyone queries it.
- Replication lag gets caught within minutes instead of when a query looks wrong
- On-call engineers get the exact source and lag figure, not a vague alert
- Every breach comes with a booked review so it gets a proper follow-up
Built for Data platform engineers · Streaming data teams · Site reliability teams · 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
console.materialize.comin a real browser with your saved login - no setup, no API keys. -
1
Materialize - check replication lag
- Open the Materialize console and read replication lag for every tracked source
- Check lag on materialized views built from those sources
- Compare each figure against the limit you set
Done when Every tracked source and view has been checked against its lag limit.
-
2
WhatsApp - ping the on-call engineer
whatsapp.com
WebRun opens WhatsApp to ping the on-call engineer. - Message the on-call engineer naming the source or view and the current lag
- Include how long it has been over the limit
- Send only while the lag is still above the limit
Done when The on-call engineer has been pinged for this breach.
-
3
Google Calendar - book an incident review
calendar.google.com
WebRun opens Google Calendar to book an incident review. - Create a short incident review slot for the next available hour
- Title it with the source or view name
- Leave it for the on-call engineer to accept or move
Done when A review slot exists on the calendar for the breach.
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
What counts as a replication lag breach?
Whatever lag limit you set per source or view. Nothing is flagged until the actual lag figure crosses your line.
Does WebRun restart the source or rebuild the view?
No. It only reads lag figures from the Materialize console and sends alerts. Restarting a source or rebuilding a view stays with your engineers.
Will we get repeated pings while lag stays high?
No. It pings once when the breach starts, then again only if the lag recovers and breaches a second time later, so WhatsApp does not fill up with repeats.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.