Final Update: Saturday, 11 February 2017 05:59 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 02/11, 04:47 UTC. Our logs show the incident started on 02/10, 19:08 UTC and that during the ~9 hours that it took to resolve the issue a very small subset of customers experienced alerting failures.
- Root Cause: The failure was due to issue with dependent service settings.
- Incident Timeline: 9 Hours & 18 minutes – 02/10, 19:08 UTC through 02/11, 04:26 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
Update: Saturday, 11 February 2017 03:23 UTC
We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers may experience Alerting issue . We are working to establish the start time for the issue, initial findings indicate that the problem began at Saturday, 11 February 2017 00:26 UTC. We currently have no estimate for resolution.
- Work Around: We have made changes which will not impact new alerting.
- Next Update: Before 02/11 07:30 UTC
Initial Update: Saturday, 11 February 2017 00:26 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Alerting failure for some of their alert rules belonging to apps which have had recent configuration changes. The following data types are affected: Availability, Metric.
- Next Update: Before 02/11 02:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.