Experiencing Data Access Issue in Azure portal for Log Analytics - 10/02 - Resolved
Final Update: Thursday, 03 October 2019 03:55 UTC We've confirmed that all systems are back to normal with no customer impact as of 10/3, 03:45 UTC. Our logs show the incident started on 10/2, 23:45 UTC and that during the 4 hours that it took to resolve the issue any customers in USGov Virginia or services dependent on querying Azure Log Analytics data experienced an inability to query that data. Root Cause: The failure was due to a middle-tier system authentication failure. Incident Timeline: 4 Hours & 0 minutes We understand that customers rely on Azure Log Analytics and associated services as a critical service and apologize for any impact this incident caused. -Jeff Update: Thursday, 03 October 2019 01:39 UTC Root cause has been isolated to a middle tier authentication issue which is impacting the ability for customers and components to query log analytics data in USGov Virginia region. Engineers are working on isolating and updating authentication information. Work Around: None Next Update: Before 10/03 04:00 UTC -Jeff Update: Thursday, 03 October 2019 00:23 UTC We continue to investigate issues within Log Analytics in the USGov Virginia region. Root cause is not fully understood at this time. Customers in the region will continue to experience errors including 502 when attempting to query Log Analytics data. Initial findings indicate that the problem began at <10/02 ~23:45 UTC>. We currently have no estimate for resolution. Work Around: None Next Update: Before 10/03 02:30 UTC -Jeff Initial Update: Wednesday, 02 October 2019 23:56 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers may experience failed queries for data. Work Around: None at this time Next Update: Before 10/03 02:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -JeffExperiencing Data Access issue in Azure Portal for Log Analytics - 08/19 - Resolved
Final Update: Monday, 19 August 2019 09:19 UTC We've confirmed that all systems are back to normal with no customer impact as of 08/19, 07:15 UTC. Our logs show the incident started on 08/19, 05:50 UTC and that during the 1 hour 25 minutes that it took to resolve the issue 15% of customers in South Central US, France Central and North Europe regions experienced data access issues in the Azure Portal and degraded performance when queried through API. Root Cause: The failure was due to an issue with one of our dependent service. Incident Timeline: 1 hours 25 minutes - 08/19, 05:50 UTC through 08/19, 07:15 UTC We understand that customers rely on Azure Log Analytics and Log Search Alerts as a critical service and apologize for any impact this incident caused. -Anmol Initial Update: Monday, 19 August 2019 06:49 UTC We are aware of issues within Log Analytics and Log Search alert and are actively investigating. Some customers in South Central US may experience data access issue in the azure portal and when queried through API. Next Update: Before 08/19 09:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnmolExperiencing Alerting failure for Log Search Alerts - 08/09 - Resolved
Final Update: Friday, 09 August 2019 23:07 UTC We've confirmed that all systems are back to normal with no customer impact as of 8/9, 22:54 UTC. Our logs show the incident started on 8/9, 18:59 UTC and that during the 3 hours that it took to resolve the issue 1062 subscriptions (~16%) experienced delayed alerts that fired after the issue was mitigated. Root Cause: The failure was due to a burst of service health activity log events which increased the evaluation latency of the events. Scaling out the service mitigated the issue. Incident Timeline: 3 Hours & 55 minutes - 8/9, 18:59 UTC through 8/9, 22:54 UTC We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused. -IanExperiencing Alerting failure for Log Search Alerts in Mooncake - 06/28 - Resolved
Final Update: Friday, 28 June 2019 11:50 UTC We've confirmed that all systems are back to normal with no customer impact as of 06/28, 06:45 UTC. Our logs show the incident started on 06/28, 05:25 UTC and that during the 1 hour 20 minutes that it took to resolve the issue all the customers in China - Mooncake region experienced alerting failures. Root Cause: The failure was due to the issue in one of our dependent services. Incident Timeline: 1 Hour & 20 minutes - 06/28, 05:25 UTC through 06/28 06:45 UTC We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused. -AnmolExperiencing Alerting failure for Log Search Alerts - 04/29 - Resolved
Final Update: Monday, 29 April 2019 11:03 UTC We've confirmed that all systems are back to normal with no customer impact as of 04/29, 10:45 UTC. Our logs show the incident started on 04/29, 08:20 UTC and that during the 2 hours 25 minutes that it took to resolve the issue, Customers must have experienced Alerting failures for the alerts configured in the Australia - South East Region. Root Cause: The failure was due to the issues in one of our dependent services. Incident Timeline: 2 hours 25 minutes - 04/29, 04/29, 08:20 UTC through 04/29, 10:45 UTC We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused. -Monish Initial Update: Monday, 29 April 2019 10:34 UTC We are aware of issues within Log Search Alerts and are actively investigating. Customers may experience Alerting failures for the Alerts configured in the Australia - South East Region. Work Around: None Next Update: Before 04/29 14:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -MonishExperienced Alerting failure for Log Search Alerts in China Gov- 01/01 - Resolved
Final Update: Friday, 01 January 2021 15:42 UTC We've confirmed that all systems are back to normal with no customer impact as of 01/01, 15:30 UTC. Our logs show the incident started on 01/01, 08:20 UTC and that during the 7 Hours 10 Minutes that it took to resolve the issue some of customers may have experienced issues with delayed or wrongly fired Log Search alerts or experienced difficulties accessing data for resources hosted in China East Region. Root Cause: We identified the issue was caused by a configuration setting. Incident Timeline: 7 Hours & 10 minutes - 01/01, 08:20 UTC through 01/01, 15:30 UTC We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused. -Madhav Update: Friday, 01 January 2021 13:27 UTC We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired Log Search Alerts or experience difficulties accessing data for resources hosted in China East 2 region. Root Cause: The failure was due to a recent deployment in one of the backend services. Next Update: Before 01/01 15:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Madhav Initial Update: Friday, 01 January 2021 10:08 UTC We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired Log Search Alerts or experience difficulties accessing data for resources hosted in China East 2 region. Work Around: None Next Update: Before 01/01 13:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnmolExperiencing Delayed alerts issue in Azure Portal in East US2 and Central US - 05/19 - Resolved
Final Update: Tuesday, 19 May 2020 08:38 UTC We've confirmed that all systems are back to normal with no customer impact as of 5/18, 18:34 UTC. Our logs show the incident started on 5/18, 17:35 UTC and that during the 59 minutes that it took to resolve the issue some of customers may have experienced issues with delayed alerts in East US2 and Central US regions. Root Cause: The failure was due to an issue in one of our dependent services. Incident Timeline: 59 minutes - 5/18, 17:35 UTC through 5/18, 18:34 UTC We understand that customers rely on Azure Monitor Alerts as a critical service and apologize for any impact this incident caused. -MadhuriExperiencing Data Access Issue in Azure portal for Log Analytics - 01/31 - Resolved
Final Update: Saturday, 01 February 2020 00:44 UTC We've confirmed that all systems are back to normal with no customer impact as of 01/31, 22:56 UTC. Our logs show the incident started on 01/31, 20:30 UTC and that during the 2 hours 26 minutes that it took to resolve the issue some customers might have experienced issues while querying data or might have seen failures related to log search alerts. Root Cause: The failure was due to .recent configuration change on a dependent service was causing down stream impact to the service. Incident Timeline: 2 Hours & 26 minutes - 01/31, 20:30 UTC through 01/31, 22:56 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Subhash Initial Update: Friday, 31 January 2020 22:15 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers in West US may experience issues with Data access from Azure portal , query failures in Log Analytics and delayed or missed alerts in Log search alerts. Work Around: Next Update: Before 02/01 02:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Subhash