Show if any application is effected by service level health problem
Today (02/22/2013.) there was a global problem effecting storage access via https. These changes effected a part of our application. It took our team a large amount of time to figure out the problem was not with our current application and changes we made on it recently, but was due to a global service problem. The management portal worked perfectly, all systems seamed to be live, and we where able to access the storage via http from our local environement (because that was the predefined protocol in our settings). But one of our runtime applications had a https connection string setting which did not work for hours at that point. We could have saved a lot of time if the health problem could have been visible via the management portal and not only a separate web site.
István Hartung
shared this idea
There are now a few ways to understand service health events:
1. All service health incidents are recorded in the Azure Activity Log, scoped to incidents that impact resources in your subscription.
2. In the Azure Portal, under the “Monitor” blade there is now a dedicated section for Service Health.
3. Using Azure Activity Log Alerts you can configure an alert on service health events to receive a notification when any service health incident occurs.
