Automated Imply Ingestion Lag Alerts
Every few minutes, WebRun checks your Imply cluster's ingestion lag and query latency against the limits you set, and the moment either crosses the line it pings the on-call engineer on WhatsApp with the datasource and the numbers, then books a short incident review on Google Calendar for the team.
How do I get alerted when Imply ingestion lag or query latency breaches a limit?
WebRun checks your Imply cluster's ingestion lag and query latency every few minutes against the limits you set. The moment a datasource breaches either one, it pings the on-call engineer on WhatsApp with the exact figures, then books a short incident review on Google Calendar, so a lagging pipeline gets caught before queries turn stale.
- Ingestion lag gets caught within minutes instead of when a dashboard goes stale
- On-call engineers get the exact breached metric, not just a generic alert
- Every breach comes with a booked review so it gets a proper follow-up
Built for Data platform engineers · Site reliability teams · Analytics 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
imply.ioin a real browser with your saved login - no setup, no API keys. -
1
Imply - check ingestion lag and query latency
imply.io
WebRun opens Imply to check ingestion lag and query latency. - Open the Imply console and read ingestion lag for each datasource
- Read query latency across recent queries
- Compare both against the limits you set
Done when Every datasource has been checked against its lag and latency limits.
-
2
WhatsApp - ping the on-call engineer
whatsapp.com
WebRun opens WhatsApp to ping the on-call engineer. - Send a message to the on-call engineer naming the datasource and the breached metric
- Include the current lag or latency figure against the limit
- Send only while the breach is still active
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 datasource 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 lag or latency breach?
Whatever limits you set for ingestion lag and query latency per datasource. Nothing is flagged until a reading actually crosses your line.
Does WebRun restart nodes or change cluster settings?
No. It only reads metrics from the Imply console and sends alerts. Cluster configuration and scaling stay in your engineers' hands.
Will we get pinged again if the lag keeps climbing?
It pings once per breach, then again only if the metric recovers and breaches a second time, so WhatsApp does not fill up with repeats of the same open issue.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.