Final Update: Wednesday, 27 June 2018 06:10 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/27, 05:30 UTC. Our logs show the incident started on 06/26, 16:00 UTC and that during the 13 and a half hours that it took to resolve the issue some customers have stopped receiving alert emails..
We've confirmed that all systems are back to normal with no customer impact as of 06/27, 05:30 UTC. Our logs show the incident started on 06/26, 16:00 UTC and that during the 13 and a half hours that it took to resolve the issue some customers have stopped receiving alert emails..
- Root Cause: The failure was due to recent change in our email template.
- Incident Timeline: 13 Hours & 30 minutes - 06/26, 16:00 UTC through 06/27, 05:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Varun
Initial Update: Wednesday, 27 June 2018 05:17 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers would have stopped receiving alert emails.
We are aware of issues within Log Analytics and are actively investigating. Some customers would have stopped receiving alert emails.
- Work Around: Customers can directly check the alert status on the OMS Portal. Other actions like webhook/runbook/ITSM are not impacted, only the alert emails are impacted.
- Next Update: Before 06/27 07:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Varun