Janitor

Start by wiring Janitor into the places you depend on: your domains, APIs, and key pages. Add the URLs you care about, choose where you want checks to run from, and set how often they should run. Define what “healthy” means—expected status codes, required keywords on a page, latency budgets, and certificate freshness rules. Pick who gets notified and how: route alerts to Slack, email, or a webhook, add quiet hours, and set escalation rules for urgent issues. Use tags to group monitors by service and environment so owners see only what they need.

Day to day, keep an eye on the live health view to spot patterns and slowdowns before they explode. When something looks off, hit Run now to force an immediate recheck after a quick fix or rollback. Drill into a failing run to see the response body, timing breakdown, and regional differences that might signal a CDN edge problem or DNS propagation lag. Compare the last good run with the first failing run to isolate what changed. If the issue is content-related, scan for assets still loading over http and correct them to https to avoid browser warnings and lost conversions.

For incident response, let Janitor drive your first steps. When an alert fires, open the event and review request/response headers, captured TLS details, and the exact IP and resolver used, so you can confirm whether the problem is your app, your certificate chain, or your DNS. Pause noise during planned maintenance with a one-click window, then resume and trigger targeted bursts after deploys to validate hotfixes from multiple regions. Protect the front door by watching certificate expiration well in advance and by validating chains so an unexpected intermediate or mismatch doesn’t slip through. Lock down your name resolution by enforcing private resolvers and receiving alerts if lookups stray or if records like A, CNAME, NS, or MX change without a planned change ticket.

Non‑technical teams can use Janitor without touching code. Marketing can track campaign landing pages and receive a morning digest that confirms everything is live before ads go out. Product managers can follow core flows—signup, pricing, and help center—to make sure content loads securely and consistently. Commerce teams can monitor add‑to‑cart and checkout endpoints for availability and response speed, with alerts that reach the right channel instantly. Agencies and IT partners can group client sites, share read‑only status links, and provide weekly reliability summaries. Everyone gets a simple view of what broke, when it started, who is on point, and what to try next, so issues get resolved fast and stay fixed.