Final Update: Monday, 08 February 2021 17:05 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/08, 15:30 UTC. Our logs show the incident started on 02/08, 14:20 UTC and that during the 70 minutes that it took to resolve the issue customers experienced misfired log search alerts and possible latent ingestion.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 02/08, 15:30 UTC. Our logs show the incident started on 02/08, 14:20 UTC and that during the 70 minutes that it took to resolve the issue customers experienced misfired log search alerts and possible latent ingestion.
- Root Cause: The failure was due to an issue within compute resources after a backend update process completed which caused nodes to fail to initialize.
- Incident Timeline: 1 Hour & 10 minutes - 02/08, 14:20 UTC through 02/08, 15:30 UTC
-Jeff
Initial Update: Monday, 08 February 2021 15:08 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in Azure Portal and issues with missed or delayed Log Search alerts in Canada Central region.
-Deepika
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in Azure Portal and issues with missed or delayed Log Search alerts in Canada Central region.
- Work Around: NA
- Next Update: Before 02/08 17:30 UTC
-Deepika
Updated Feb 08, 2021
Version 3.0