3 ms·

they really need two dashboards. one for people that want something useful and one for people that want to be lied to.

CoolGuySteve 10y ago
A lot of the time, services outages seem localized to specific datacenters and subnets, or some relatively small subset of nodes. I suspect even Amazon doesn't know there's a problem sometimes. I would be happy if they just added a status indicator to each running node indicating that there's some local problem.
- amichal 10y ago
  They do.. its called Cloudwatch. https://aws.amazon.com/cloudwatch/details/#amazon-ec2-monitoring https://aws.amazon.com/cloudwatch/details/#amazon-ec2-monito...
  - CoolGuySteve 10y ago
    That's not quite what I want though, what I want to know is if the SQS/Dynamo/etc server is functioning correctly for that node. I am almost always confident the node itself is functional from my own metrics.
    - ckozlowski 10y ago
      You might be interested in the Personal Health Dashboard then: https://aws.amazon.com/premiumsupport/phd/ https://aws.amazon.com/premiumsupport/phd/
    - amichal 10y ago
      I meant you could deduce/monitor/alert on the behavior of any of the services relevant to you (i don't use SQS but metrics for it are there apparently). These have been way more helpful to me and i often show copy pastes of graphs to clients to explain problems. ckozlowski mentioned Personal Health Dashboard which I never knew about as an alternative I should check out. However, I agree with the fundamental premise that status.aws.amazon.com is useless except for National News scale events. Other commenters have taught me that the status page is a regional-level view, manually updated which is something I hadn't considered and makes me understand why it might be useless. One other thing I tried was to subscribe to the RSS feeds (on the status page) for the region/services I was interested in. I eventually turned them off as they where way too noisy, often alerting to things that didn't actually have an effect on my usage.
    - deleted 10y ago
      [deleted]

A lot of the time, services outages seem localized to specific datacenters and subnets, or some relatively small subset of nodes. I suspect even Amazon doesn't know there's a problem sometimes. I would be happy if they just added a status indicator to each running node indicating that there's some local problem.

amichal 10y ago
They do.. its called Cloudwatch. https://aws.amazon.com/cloudwatch/details/#amazon-ec2-monitoring https://aws.amazon.com/cloudwatch/details/#amazon-ec2-monito...
- CoolGuySteve 10y ago
  That's not quite what I want though, what I want to know is if the SQS/Dynamo/etc server is functioning correctly for that node. I am almost always confident the node itself is functional from my own metrics.
  - ckozlowski 10y ago
    You might be interested in the Personal Health Dashboard then: https://aws.amazon.com/premiumsupport/phd/ https://aws.amazon.com/premiumsupport/phd/
  - amichal 10y ago
    I meant you could deduce/monitor/alert on the behavior of any of the services relevant to you (i don't use SQS but metrics for it are there apparently). These have been way more helpful to me and i often show copy pastes of graphs to clients to explain problems. ckozlowski mentioned Personal Health Dashboard which I never knew about as an alternative I should check out. However, I agree with the fundamental premise that status.aws.amazon.com is useless except for National News scale events. Other commenters have taught me that the status page is a regional-level view, manually updated which is something I hadn't considered and makes me understand why it might be useless. One other thing I tried was to subscribe to the RSS feeds (on the status page) for the region/services I was interested in. I eventually turned them off as they where way too noisy, often alerting to things that didn't actually have an effect on my usage.
  - deleted 10y ago
    [deleted]