Experiencing Alerting failure for Log analytics and Log Search Alerts – 02/21 – Resolved

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

Final Update: Sunday, 23 February 2020 06:20 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/23, 06:00 UTC. Our logs show the incident started on 02/21, 21:25 UTC and that during the 32 hours and 35 minutes that it took to resolve the issue Some customers may have experienced data access, missed or delayed alerts related errors in West US region .
  • Root Cause: The failure was due issues with one of our dependent service.
  • Incident Timeline: 32 Hours & 35 minutes - 02/21, 21:25 UTC through 02/23, 06:00 UTC
We understand that customers rely on Log Analytics and Log Search Alerts  as a critical service and apologize for any impact this incident caused.

-Anusha

Update: Saturday, 22 February 2020 23:28 UTC

We continue to investigate issues within Log Search Alerts. Root cause is not fully understood at this time. Some customers continue to experience data access, missed or delayed alerts related errors. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/21 21:25 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 02/23 05:30 UTC
-Leela

Update: Saturday, 22 February 2020 16:38 UTC

We continue to investigate issues within Log Search Alerts. Root cause is not fully understood at this time. Some customers continue to experience data access, missed or delayed alerts related errors. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/21 21:25 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 02/22 23:00 UTC
-Leela

Update: Saturday, 22 February 2020 12:33 UTC

We continue to investigate issues within Log Search Alerts. Root cause is not fully understood at this time. Some customers continue to experience data access, missed or delayed alerts related errors. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/21 21:25 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 02/22 17:00 UTC
-Rama

Update: Saturday, 22 February 2020 05:25 UTC

We continue to investigate issues within Log Search Alerts. Root cause is not fully understood at this time. Some customers continue to experience data access, missed or delayed alerts related errors. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/21 21:25 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 02/22 11:30 UTC
-Rama

Update: Saturday, 22 February 2020 01:14 UTC

We continue to investigate issues within Log Search Alerts and Log Analytics. Root cause has been isolated to one of the backend services becoming unhealthy.Some customers may experience data access, missed or delayed alerts related errors. We are working to establish the start time for the issue, initial findings indicate that the problem began at  02/21 21:25 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 02/22 05:30 UTC
-Subhash

Initial Update: Friday, 21 February 2020 23:31 UTC

We are aware of issues within Log Analytics and Log Search alerts and are actively investigating. Some customers may experience data access, missed or delayed alerts related errors.
  • Work Around: None
  • Next Update: Before 02/22 02:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anupama


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.