JasonTokoph wrote:
Don't get me wrong. I have monitors in place for all of my systems, Linodes or otherwise. These monitors kicked off alerts that I needed. The issue is that I had no idea why the alerts were being generated.
Oh, sorry - I got the wrong impression from your earlier phrasing, which made it sound like you didn't have anything yourself to let you notice the outage even on your own Linodes.
For what it's worth, when my monitors fire, and after the obvious stuff like issues on the monitor's own connection or the network, first thing I do is check status.linode.com, and then if there is nothing there, get on IRC and lurk a bit or ask about it. I'm not a tweeter, so I rarely look there. Typically one of the two will give me the low down fairly quickly (IRC in particular gets busier during the larger outages, and at a minimum you can probably find out if you aren't alone), but I'm willing to accept some latency also since I may have actually noticed things myself first or the issue may be small enough not to prompt a status update.
Also, the good news is that now you know about status.linode.com for the future. I agree some additional links to it couldn't hurt, though it's a fairly common naming convention among providers in the last few years, so not a bad name to try by default. Also, depending on the outage, the main Linode site may not itself respond - e.g., if the recent outage had been in Texas, so depending on using a link from the main site won't always work (status.linode.com is hosted elsewhere).
Quote:
I'll be happy when a post mortem is in my inbox along with an apology for lack of communication.
Wouldn't necessarily wait for the inbox, but I'm sure some summary information will be posted or made available when possible. For example
http://www.linode.com/forums/viewtopic. ... 4778#24778 when there was an outage affecting a decent number of machines in the Newark DC last year.
-- David