I suggest you ...

expose a Service Availability API.

Build an API that exposes the data that is used by the Service Availability dashboard, so that we can build monitoring applications (e.g. WinPhone7) to keep an eye on things. I know about the RSS feed for the services, but it's largely ad-hoc, and pretty unparseable programmatically. Ideally, this is something that just returns Red/Yellow/Green for a DC+Service combination, and a comment if it's not all Green. Clearly, if everything is going well, it's heavily cacheable, and only when it's changed would you need to break that cache.

131 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Adam HoffmanAdam Hoffman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Daniel EggertDaniel Eggert commented  ·   ·  Flag as inappropriate

        Two additional points: The site should include a node that is independent from Azure itself, so that if the internal service is unreachable, then it can still be reached (For example, use DNS redundancy for independence.)

        Secondly, in addition to status provide attributes, such as outage start time (UTC), severity, ETA (UTC), scale, error code, etc. A simple API call could return just status, but these other attributes could provide non-Azure hosted (on-prem, other) with the option of migrating away until service is restored.

      • Alexander BatishchevAlexander Batishchev commented  ·   ·  Flag as inappropriate

        This is true. While you can read RSS or intercept Web API responses, underlying data is not designed to be machine-parsed. For instance, timestamp is not a separate field but included into incident text description, etc. etc.

      Feedback and Knowledge Base