%3CLINGO-SUB%20id%3D%22lingo-sub-1399404%22%20slang%3D%22en-US%22%3EIssues%20in%20multiple%20services%20in%20Application%20insights%20in%20Central%20India%20-%2005%2F18%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1399404%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2018%20May%202020%2014%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Azure%20Monitor%20in%20the%20Central%20India%20region%20and%20are%20actively%20investigating.%20Some%20customers%20using%20Log%20Analytics%20and%20Application%20Insights%20services%20in%20this%20region%20may%20face%20ingestion%20failures%2C%20data%20latency%2C%20data%20access%20issues%20and%20failures%20in%20CRUD%20operations%20on%20their%20Applications%20or%20Workspaces.%20Customers%20using%20Log%20Search%20Alerts%20may%20face%20missed%20or%20delayed%20alerts%20and%20customers%20may%20also%20face%20issues%20using%20VM%20Insights.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F18%2018%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Madhuri%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1399404%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EService%20Map%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESmart%20Diagnostics%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Final Update: Monday, 18 May 2020 22:58 UTC


We've confirmed that all systems are back to normal as of 05/18, 22:28 UTC. Our logs show the incident started on 05/18, 12:41 UTC and that during 6 hours 30 minutes that it took to resolve the issue, customers might have experienced ingestion failures, data latency issues, data access issues, failures in CRUD operations on their Applications or Workspaces, delayed or missed or misfired log search alerts in Central India region.


•Root Cause: The failure was due to a disturbance to the regional utility power provider, which impacted Azure Monitoring Services in Central India region. 

•Incident Timeline: 6 Hours & 30 minutes – 05/18, 12:41 UTC through05/18, 19:11 UTC


We understand that customers rely on Azure Monitoring Services as critical services and apologize for any impact this incident caused.

-Sindhu



Update: Monday, 18 May 2020 18:38 UTC

We continue to investigate issues within Azure Monitoring Services. Issue is due to Azure outage in Central India region. Initial root cause points to a disturbance to the regional utility power provider. Data center technicians are working on restoring IT equipment. Customers may continue to experience ingestion failures, data latency issues, data access issues, failures in CRUD operations on their Applications or Workspaces, delayed or missed or misfired log search alerts in Central India region. We currently have no estimate for resolution.

Work Around: None

Next Update: Before 05/18 23:00 UTC

-Sindhu


Initial Update: Monday, 18 May 2020 14:08 UTC

We are aware of issues within Azure Monitoring Services. Customers may experience ingestion failures, data latency issues, data access issues, failures in CRUD operations on their Applications or Workspaces, delayed or missed or misfired log search alerts in Central India region.

Work Around: None.

Next Update: Before 05/18 18:30 UTC

 

We are working hard to resolve this issue and apologize for any inconvenience.

-Madhuri