This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 17 June 2022 06:48 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/17, 06:03 UTC. Our logs show the incident started on 06/17, 03:18 UTC and that during the 2 hours and 45 minutes that it took to resolve the issue. Some customers ingesting telemetry in their Log Analytics Workspace in East US2 geographical region may have experienced intermittent data latency and incorrect alert activation.
.
We've confirmed that all systems are back to normal with no customer impact as of 06/17, 06:03 UTC. Our logs show the incident started on 06/17, 03:18 UTC and that during the 2 hours and 45 minutes that it took to resolve the issue. Some customers ingesting telemetry in their Log Analytics Workspace in East US2 geographical region may have experienced intermittent data latency and incorrect alert activation.
.
- Root Cause: The failure was due to backend dependencies become unhealthy..
- Incident Timeline: 2 Hours & 45 minutes - 06/17, 03:18 UTC through 06/17, 06:03 UTC
-Anmol
Initial Update: Friday, 17 June 2022 05:43 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in their Log Analytics Workspace in East US2 geographical region may experience intermittent data latency and incorrect alert activation.
-Anmol
We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in their Log Analytics Workspace in East US2 geographical region may experience intermittent data latency and incorrect alert activation.
- Work Around: None
- Next Update: Before 06/17 09:00 UTC
-Anmol