DEV Community

Evangelist Naval
Evangelist Naval

Posted on Originally published at Medium

How I get a status page alert when the green badge still lies

I used to treat a vendor status page like the official score. Green pill. All Systems Operational. Tab closed. Back to blaming our deploy.

Then a payments vendor failed in slow motion for 40 minutes and the hero line never left green. API Operational. Dashboard Operational. Webhooks sat on a tiny yellow Degraded for nine minutes. Someone scrubbed the yellow from the incident history before lunch.

Checkout was already dead. Support was already in all caps. The status page was doing its real job: looking calm.

The hero badge is comms

A status page is a webpage. It is not your monitor. A person or a flaky aggregator decides when the big pill turns red. They flip that headline last.

The useful movement is smaller and earlier:

  • a subcomponent row with a boring name (webhooks, EU-west ingest)
  • an incident banner that shows up, then Resolved in 12 minutes with no writeup
  • Last updated jumping while the badge stays green
  • a maintenance note that never hit the email list

If you only look at the hero, you are reading a press release.

Feeds missed the flicker

I subscribed to Atom. I subscribed to email. I still missed it.

The feed publishes incidents. It does not publish "we flipped Webhooks back to Operational and deleted the yellow." Email waits for a paragraph and a customer-success tone. Hitting refresh on status.vendor.com at 2am is a hobby, not a system.

Google Alerts ignore a same-URL rewrite. Screenshot tools fire when a banner animates. You wanted the sentence that changed.

Watch the public status URL

You do not need their PagerDuty. You need the page they already publish.

Paste the status URL. Ask a watcher when component state changes, when a banner appears, when Operational is no longer the only word on the page.

I use AyeWatch for that. Free Preview is $0 with 3 topics and 6 lifetime runs. Pro is $9 a month.

When it fires I open the page, copy the component row, drop it in the incident channel. Beats a 20-person thread about whether it is us.

Two or three vendors

Watch the ones that can take you down. Payments. Auth. Email. The CDN. If a status page has not moved in a year, you probably do not actually depend on them.

Skip the marketing homepage. Watch /status, status.vendor.com, or the Atlassian Statuspage subdomain they hid in the footer.

The green lie is the default. Alert on the text, not the vibe of the badge.

Originally published on Medium: https://medium.com/@evangelist67/how-to-get-a-status-page-alert-when-green-still-lies-ef0b9e230020

Top comments (0)