Burrow + Oh Dear

Ingest Oh Dear monitoring signals into Burrow alongside CMS events, deploys, and billing. When a site goes down, Burrow's timeline shows what changed before the outage and what happened after the fix.

Request early access Read the docs

[ Capabilities ]

Monitoring with operational context

Oh Dear pings show 'site is down.' Burrow's timeline shows the deploy that happened 10 minutes before the outage, the form submissions that stopped, and the Slack alert that triggered the fix. Context, not just status.

Mixed hosting, one view

Oh Dear monitors sites across any host. Burrow captures Oh Dear signals alongside WordPress, Shopify, GitHub, and Stripe events — so your agency's monitoring view covers every client system, not just sites with a specific monitoring agent.

Incident context for client reports

Monthly digests can include: 'Site X had 23 minutes of downtime on March 7, caused by a hosting migration. Resolved within the hour. Uptime for the month: 99.95%.' That narrative builds client confidence.

Uptime monitoring tells you the site is down. Burrow tells you why it went down and what happened while it was.

Oh Dear is one of the best site health monitoring tools available — uptime checks, SSL monitoring, broken link detection, DNS health, mixed content scanning. It answers the critical question: “Is the site reachable right now?”

But for agencies managing 30-50+ client sites, “is it reachable?” is the starting point, not the whole story. When Oh Dear pages your developer at 2am because Client X’s site is down, the next question is always: “What changed?” Did someone push a deploy? Did a plugin update break something? Did the hosting provider have an incident?

Burrow puts Oh Dear monitoring signals in context. The same client timeline that shows “downtime detected at 2:14am” also shows “GitHub deploy at 2:01am” and “form.submitted events stopped at 2:15am.” The incident narrative writes itself.

After recovery, the monthly client digest includes: “Site X experienced 23 minutes of downtime on March 7, triggered by a deployment conflict. Resolved within the hour. Uptime for the month: 99.95%. Form submissions: 187 (no data lost during incident).” That’s a professional incident summary assembled from real events — not reconstructed from memory during the next client call.

Oh Dear detects. Burrow contextualizes. Together, your agency runs fewer fire drills.

Form monitoring use case | Agency operations use case

Frequently asked questions

Does Burrow replace Oh Dear?

No. Oh Dear remains your monitoring vendor — uptime checks, SSL monitoring, broken links, DNS health. Burrow is where monitoring events meet the rest of your operational data. Use Oh Dear for detection and Burrow for the narrative layer.

What Oh Dear signals does Burrow capture?

Uptime check results, downtime alerts, and recovery events. The specific signals depend on your Oh Dear webhook configuration to Burrow.

Can I use a different monitoring tool?

Yes. Burrow's API accepts events from any monitoring vendor. If you use UptimeRobot, Pingdom, or a custom health check system, send events through the Burrow API. Oh Dear is a named integration; monitoring in general is a supported event category.

What about false positives?

Oh Dear handles detection and deduplication. Burrow receives the signals Oh Dear sends. Filter noisy alerts at the Oh Dear level before they flow into your Burrow timeline.

How does this help with incident response?

When Oh Dear reports a site down, Burrow's timeline shows what happened before and after — the GitHub deploy 10 minutes prior, the form submissions that stopped, the recovery event. Post-incident reviews write themselves from the timeline.

Your agency's work deserves to be seen.

We're onboarding agencies in small cohorts to keep the quality high. Request early access and we'll be in touch.

Request early access Read the docs

Self-funded · Independent · Built for the long term