Automated Snowplow Bad Rows Rate Alerts
Every morning, WebRun opens the Snowplow pipeline dashboard, checks yesterday's bad rows rate against your normal range, books a pipeline review slot on Google Calendar when it spikes past that range, and posts the full numbers to Microsoft Teams.
How do I catch a Snowplow bad rows rate spike early?
WebRun checks the Snowplow pipeline's bad rows rate every morning, books a review slot on the data team's Google Calendar when it spikes past your normal range, and posts the full numbers to Microsoft Teams. Data platform teams catch a rising bad rows rate before it snowballs into gaps in downstream event data.
- A bad rows spike gets a booked review slot the same morning
- The team sees the trend in Teams without opening the dashboard
- Normal day to day noise never triggers a false alarm
Built for data platform teams · data engineering teams · analytics engineering teams
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
snowplow.ioin a real browser with your saved login - no setup, no API keys. -
1
Snowplow - check the bad rows rate
- Open the Snowplow pipeline dashboard
- Read yesterday's total events and bad rows count
- Calculate the bad rows rate and compare it to your normal range
Done when Yesterday's bad rows rate is calculated and compared.
-
2
Google Calendar - book a review slot
WebRun opens Google Calendar to book a review slot. - If the rate spiked past normal range, open Google Calendar
- Find the next open working hours slot for the data team
- Book a pipeline review titled with the spike's size
Done when A spike has a booked review slot on the calendar.
-
3
Microsoft Teams - post the numbers
WebRun opens Microsoft Teams to post the numbers. - Open the data platform channel in Microsoft Teams
- Post yesterday's bad rows rate and the trend
- Include the review slot time if one was booked
Done when The team has yesterday's bad rows numbers in Teams.
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 events causing bad rows?
No. It only reads the bad rows count and rate from the pipeline dashboard. Fixing a schema or tracker issue stays a manual task.
What counts as a spike?
A bad rows rate outside the normal range you set for your pipeline. Ordinary day to day noise does not trigger a review booking.
Does it check every event in detail?
No. It reads the aggregate bad rows count and rate the dashboard already reports, not individual event payloads.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.