🔍Console Errors Bot

Every ten minutes, a headless Chrome instance sweeps 40+ of Dusted's managed client sites, listening for the things users hit before anyone else notices: console errors, uncaught exceptions and failed network requests, each captured with its source location.

The hard part of monitoring real client sites isn't finding errors — it's not drowning in false ones. The bot carries a rules table of cookie-consent selectors covering a dozen consent frameworks, plus site-specific access flows that click through jurisdiction disclaimers on gated sites, all applied best-effort so a stale selector never turns into a phantom alert. Only genuine console errors page the team.

When something is really broken, a formatted Slack alert lands in the support channel naming each failing site with its top errors, and every run writes a timestamped JSON report for the archive. The whole thing is deliberately tiny — Puppeteer, native fetch and cron — with an end-to-end test path that injects a synthetic error to prove the alerting pipeline works.