This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Tuesday, 13 October 2020 05:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/13, 05:25 UTC. Our logs show the incident started on 10/12, 23:55 UTC and that during the 5 hours & 30 minutes that it took to resolve the issue, some customers may have experienced delay in platform metrics delivered to customer storage, customer Event Hub, or Log Analytics via Diagnostic Settings.
-Deepika
We've confirmed that all systems are back to normal with no customer impact as of 10/13, 05:25 UTC. Our logs show the incident started on 10/12, 23:55 UTC and that during the 5 hours & 30 minutes that it took to resolve the issue, some customers may have experienced delay in platform metrics delivered to customer storage, customer Event Hub, or Log Analytics via Diagnostic Settings.
- Root Cause: The failure was due to configuration issues with one of our dependent services
- Incident Timeline: 5 Hours & 30 minutes - 10/12, 23:55 UTC through 10/13, 05:25 UTC
-Deepika
Initial Update: Tuesday, 13 October 2020 05:17 UTC
We are aware of issues within Azure Monitor Essentials and are actively investigating. Some customer using Azure Monitor may experience delay in platform metrics delivered to customer storage, customer Event Hub, or Log Analytics via Diagnostic Settings across all regions.
-Rama
We are aware of issues within Azure Monitor Essentials and are actively investigating. Some customer using Azure Monitor may experience delay in platform metrics delivered to customer storage, customer Event Hub, or Log Analytics via Diagnostic Settings across all regions.
- Next Update: Before 10/13 09:30 UTC
-Rama