Experiencing Data Access issues for Azure Monitor – 09/17 – Resolved

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Final Update: Saturday, 18 September 2021 03:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/18, 03:40 UTC. Our logs show that the incident started on 09/17, 19:45 UTC and that during the 7 hours & 55 minutes that it took to resolve the issue some of the customers experienced issues querying their data which can cause delayed or misfired alerts and web tests failures.
  • Root Cause: The failure was due to unhealthy backend Traffic Manger probe.
  • Incident Timeline: 7 Hours & 55 minutes - 09/17, 19:45 UTC through 09/18, 03:40 UTC
We understand that customers rely on Application Insights and Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Saika

Update: Saturday, 18 September 2021 03:14 UTC

We are continuing to work on mitigation steps. Some customers in East US and West Europe regions may still experience issues querying their data which can cause delayed or misfired alerts and web tests failures.
  • Work Around: None
  • Next Update: Before 09/18 06:30 UTC
-Saika

Update: Saturday, 18 September 2021 00:24 UTC

Root cause has been isolated to a backend Traffic Manger probe that became unhealthy which was impacting Application Insights and Azure Log Analytics. To address this issue we are continuing to work on mitigation steps. Some customers may still experience issues querying their data which can cause delayed or misfired alerts.
  • Work Around: None
  • Next Update: Before 09/18 03:30 UTC
-Saika

Update: Friday, 17 September 2021 21:31 UTC

We continue to investigate issues within Application Insights and Azure Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience issues querying their data which can cause delayed or misfired alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 09/17 ~07:45 UTC. We currently have no estimate for resolution.
  • Work Around: none
  • Next Update: Before 09/18 01:00 UTC
-Ian

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.