Hacker News new | past | comments | ask | show | jobs | submit login

I haven’t written a status page in a while, but the rest of my infrastructure starts freaking out if it hasn’t heard from a service in a while. Why doesn’t their status page have at least a warning about things not looking good?



In my experience public status pages are "political" and no matter how they start tend to trend towards higher management control in some way... that leads to people who don't know, aren't in the thick of it, don't understand it, and / or are cautious to the point that it stops being useful.


Not only political, but with SLAs on the line they have significant financial and legal consequences as well. Most managers are probably happier keeping the ‘incident declaring power’ in as few a hands as possible to make sure those penalty clauses aren’t ever un-necessarily triggered.


That’s fraud in other industries.


Same with most corporate twitter feeds. I’d like to follow my public transit/airport/highway authority, but it’ll be 10 posts about Kelly’s great work in accounting for every service disruption.

And No, I don’t want to install a separate app to get push notifications about service disruptions for every service I use.


A good Twitter account is a wonderful thing....the bad ones hurt so bad.


Ugh. I guess that just goes to show that any metric can be politicized.


It's just Goodhart's law in effect: If a status page is used as a target metric in an SLA the status page ceases to be a useful measure.


Status pages are the progress bars of the cloud.


I worked on the networking side for years.

Now the web development side and I'm all "Wait a minute...are there any progress bars that are based on, anything real!?!?!"

I should have known...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: