Final Update: Friday, 17 June 2022 20:00 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/17, 20:00 UTC. Our logs show the incident started on 06/16, 15:30 UTC and that during the 28.02 hours that it took to resolve the issue 97% of customers experienced intermittent data latency and incorrect alert activation in Canada Central region.
-Shwetha
We've confirmed that all systems are back to normal with no customer impact as of 6/17, 20:00 UTC. Our logs show the incident started on 06/16, 15:30 UTC and that during the 28.02 hours that it took to resolve the issue 97% of customers experienced intermittent data latency and incorrect alert activation in Canada Central region.
- Root Cause: A recent deployment introduced an incorrect configuration causing the data latency and incorrect alert activation to occur.
- Incident Timeline: 28 Hours & 2 minutes - 6/16, 15:30 UTC through 6/17, 19:32 UTC
- Mitigation: Fixed the incorrect configuration in order to mitigate the issue.
-Shwetha
Update: Friday, 17 June 2022 11:49 UTC
Root cause has been isolated to configuration error which was impacting Log Analytics .To address this issue reverting the configuration changes that we made. Some customers may continue to experience intermittent data latency and incorrect alert activation.
Root cause has been isolated to configuration error which was impacting Log Analytics .To address this issue reverting the configuration changes that we made. Some customers may continue to experience intermittent data latency and incorrect alert activation.
Issue was started on 2022/06/16 15:30 UTC.
- Work Around: None
- Next Update: Before 06/17 18:00 UTC
Updated Jun 17, 2022
Version 3.0
Azure-Monitor-Team
Microsoft
Microsoft
