This article is contributed. See the original author and article here.
Final Update: Monday, 14 June 2021 13:29 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 06/14, 13:15 UTC. Our logs show the incident started on 06/14 07:10 UTC and that during the 6 hours & 5 Minutes that it took to resolve the issue, some customers may have experienced issues ingesting telemetry in Log Analytics Workspace and may have experienced intermittent data latency, data gaps and incorrect alert activation in North Europe region.
-Rahul
We’ve confirmed that all systems are back to normal with no customer impact as of 06/14, 13:15 UTC. Our logs show the incident started on 06/14 07:10 UTC and that during the 6 hours & 5 Minutes that it took to resolve the issue, some customers may have experienced issues ingesting telemetry in Log Analytics Workspace and may have experienced intermittent data latency, data gaps and incorrect alert activation in North Europe region.
- Root Cause: The failure was due to an issue with our dependent service.
- Incident Timeline: 6 Hours & 5 minutes – 06/14, 07:10 UTC through 06/14, 13:15 UTC
-Rahul
Initial Update: Monday, 14 June 2021 11:51 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in North Europe region may experience intermittent data latency, data gaps and incorrect alert activation.
-Rahul
We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in North Europe region may experience intermittent data latency, data gaps and incorrect alert activation.
- Work Around: None
- Next Update: Before 06/14 16:00 UTC
-Rahul
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments