Final Update: Monday, 28 March 2022 22:35 UTC
We've confirmed that all systems are back to normal as of 3/28, 22:15 UTC however impacted customers would continue to see the data gaps for the impacted period. We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
We've confirmed that all systems are back to normal as of 3/28, 22:15 UTC however impacted customers would continue to see the data gaps for the impacted period. We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
- Root Cause: The failure was due to a code bug got deployed which impacted 2 data types.
- Incident Timeline: ~6 days - 3/23, 22:25 UTC through 3/28, 22:15 UTC
-Arvind Yadav
Update: Monday, 28 March 2022 20:22 UTC
Starting at 22:25 UTC on 23 Mar 2022, customers using Azure Log Analytics who may be seeing data gaps for two data types of custom logs and IIS logs. Customers relying on this data would have seen failures in various data reports, query and alerting configured. We understand this issue completely and a fix has been rolling out to mitigate the impact. The next update will be provided in 3 hours, or as events warrant.
Starting at 22:25 UTC on 23 Mar 2022, customers using Azure Log Analytics who may be seeing data gaps for two data types of custom logs and IIS logs. Customers relying on this data would have seen failures in various data reports, query and alerting configured. We understand this issue completely and a fix has been rolling out to mitigate the impact. The next update will be provided in 3 hours, or as events warrant.
- Work Around:
- Next Update: Before 03/28 23:30 UTC
Updated Mar 28, 2022
Version 2.0