This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 26 January 2022 18:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/26, 18:00 UTC. Our logs show that the incident started on 01/26, 16:55 UTC and that during the 1 hour & 5 minutes that it took to resolve the issue some of customers using Azure Monitor or Azure Sentinel might have experienced delayed or missed Log Search Alerts and issues accessing data in UK South region.
-Saika
We've confirmed that all systems are back to normal with no customer impact as of 01/26, 18:00 UTC. Our logs show that the incident started on 01/26, 16:55 UTC and that during the 1 hour & 5 minutes that it took to resolve the issue some of customers using Azure Monitor or Azure Sentinel might have experienced delayed or missed Log Search Alerts and issues accessing data in UK South region.
- Root Cause: The failure was due to an issue in one of our backend services.
- Incident Timeline: 1 Hour & 5 minutes - 01/26, 16:55 UTC through 01/26, 18:00 UTC
-Saika
Initial Update: Wednesday, 26 January 2022 18:25 UTC
We are aware of issues within Log Analytics and are actively investigating. Some of the customers using Azure Monitor or Azure Sentinel may experience delayed or missed Log Search Alerts and issues accessing data in UK South region.
We are aware of issues within Log Analytics and are actively investigating. Some of the customers using Azure Monitor or Azure Sentinel may experience delayed or missed Log Search Alerts and issues accessing data in UK South region.
- Work Around: None
- Next Update: Before 01/26 21:30 UTC
-Saika