This article is contributed. See the original author and article here.
We’ve confirmed that all systems are back to normal with no customer impact as of 07/09, 19:14 UTC. Our logs show the incident started on 07/09, 17:56 UTC and that during the 1 hour 15 min that it took to resolve the issue some of customers in Australia SouthEast experienced intermittent data latency, data gaps and incorrect alert activation for Heartbeat, Perf, SecurityEvent and CommonSecurityLog data types.
- Root Cause: The issue was due to a infrastructure failure during deployment.
- Incident Timeline: 1 Hour & 15 minutes – 07/09, 17:56 UTC through 07/09, 19:14 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.