Final Update: Monday, 15 February 2021 14:04 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/15, 14:02 UTC. Our logs show the incident started on 02/15, 11:30 UTC and that during the 2 hours 32 Minutes that it took to resolve the issue some customers may have seen errors but it will not impact any data access, ingestion or alerting.
-Vamshi
We've confirmed that all systems are back to normal with no customer impact as of 02/15, 14:02 UTC. Our logs show the incident started on 02/15, 11:30 UTC and that during the 2 hours 32 Minutes that it took to resolve the issue some customers may have seen errors but it will not impact any data access, ingestion or alerting.
- Root Cause: The failure was due to some config changes into one of our dependent services.
- Incident Timeline: 2 Hours & 32 minutes - 02/15, 11:30 UTC through 02/15, 14:02 UTC
-Vamshi
Initial Update: Monday, 15 February 2021 13:10 UTC
We are aware of issues within Azure Monitor Service and are actively investigating. Some customers may see errors but it will not impact any data access, ingestion or alerting. Errors are caused by some config changes but not impacting any scenario. We have been working to fix the cause of error and provide an update in 2 hours.
-Mohini
We are aware of issues within Azure Monitor Service and are actively investigating. Some customers may see errors but it will not impact any data access, ingestion or alerting. Errors are caused by some config changes but not impacting any scenario. We have been working to fix the cause of error and provide an update in 2 hours.
- Work Around: None.
- Next Update: Before 02/15 17:30 UTC
-Mohini
Updated Feb 15, 2021
Version 4.0