Final Update: Thursday, 07 July 2022 05:03 UTC
We've confirmed that all systems are back to normal with no customer impact as of 07/07, 03:00 UTC. Our logs show the incident started on 07/07, 00:00 UTC and that during the 3 hours that it took to resolve the issue some of the customers ingesting telemetry in China East 2 geographical region may have experienced intermittent data latency, data gaps and incorrect alert activation.
-Sai Kumar
We've confirmed that all systems are back to normal with no customer impact as of 07/07, 03:00 UTC. Our logs show the incident started on 07/07, 00:00 UTC and that during the 3 hours that it took to resolve the issue some of the customers ingesting telemetry in China East 2 geographical region may have experienced intermittent data latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to a backend dependent service becoming unhealthy.
- Incident Timeline: 3 Hours - 07/07, 00:00 UTC through 07/07, 03:00 UTC
-Sai Kumar
Initial Update: Thursday, 07 July 2022 04:34 UTC
We are aware of issues within Application Insights and are actively investigating. Some of the customers ingesting telemetry in China East 2 geographical region may experience intermittent data latency, data gaps and incorrect alert activation.
-Sai Kumar
We are aware of issues within Application Insights and are actively investigating. Some of the customers ingesting telemetry in China East 2 geographical region may experience intermittent data latency, data gaps and incorrect alert activation.
- Work Around: None
- Next Update: Before 07/07 08:00 UTC
-Sai Kumar
Updated Jul 07, 2022
Version 2.0
Azure-Monitor-Team
Microsoft
Microsoft
