This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Saturday, 23 October 2021 05:19 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/23, 05:05 UTC. Our logs show the incident started on 10/22, 22:30 UTC and that during the 6 hours & 35 minutes that it took to resolve the issue some customers may have experienced intermittent data latency, partial query result and incorrect alert activation in West US 2 region.
-Vyom
We've confirmed that all systems are back to normal with no customer impact as of 10/23, 05:05 UTC. Our logs show the incident started on 10/22, 22:30 UTC and that during the 6 hours & 35 minutes that it took to resolve the issue some customers may have experienced intermittent data latency, partial query result and incorrect alert activation in West US 2 region.
- Root Cause: The failure was due to an issue with dependent service.
- Incident Timeline: 6 Hours & 35 minutes - 10/22, 22:30 UTC through 10/23, 05:05 UTC
-Vyom
Update: Saturday, 23 October 2021 02:23 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time.
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time.
Customers ingesting telemetry in their Log Analytics Workspace in West US 2 geographical region during 10/22 starting from 22:30 UTC may have experienced intermittent data latency, partial query result and incorrect alert activation
- Work Around: none
- Next Update: Before 10/23 05:30 UTC