Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1085210%22%20slang%3D%22en-US%22%3EExperiencing%20Query%20and%20Alerting%20failures%20for%20Azure%20Monitor%20services%20-%2001%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1085210%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%3EFinal%20Update%3C%2FU%3E%3A%20Thursday%2C%2002%20January%202020%2000%3A48%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20as%20of%2001%2F02%2C%2000%3A25%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F01%2C%2021%3A45%20UTC%20and%20that%20during%20the%202%20hours%20and%2040%20mins%20that%20it%20took%20to%20resolve%20the%20issue%2C%20some%20customers%20experienced%20data%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%20font-variant-numeric%3A%20normal%3B%20font-variant-east-asian%3A%20normal%3B%22%3Eaccess%20and%20alerting%20failures%3C%2FSPAN%3E.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%20font-variant-numeric%3A%20normal%3B%20font-variant-east-asian%3A%20normal%3B%22%3Ememory%20issue%20in%20underlying%20infrastructure%3C%2FSPAN%3E.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2040%20minutes%20-%2001%2F01%2C%2021%3A45%20UTC%20through%2001%2F02%2C%2000%3A25%20UTC%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Search%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-chandar%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%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%20Wednesday%2C%2001%20January%202020%2022%3A54%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Azure%20Monitor%20services%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3Equery%20and%20alerting%20failures%20against%20the%20data%20stored%20in%20West%20Europe%20and%20East%20US%20regions.%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20Retry%20your%20operation%20as%20needed.%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F02%2001%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Chandar%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1085210%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 02 January 2020 00:48 UTC

We've confirmed that all systems are back to normal as of 01/02, 00:25 UTC. Our logs show the incident started on 01/01, 21:45 UTC and that during the 2 hours and 40 mins that it took to resolve the issue, some customers experienced data access and alerting failures.
  • Root Cause: The failure was due to memory issue in underlying infrastructure.
  • Incident Timeline: 2 Hours & 40 minutes - 01/01, 21:45 UTC through 01/02, 00:25 UTC  
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-chandar

Initial Update: Wednesday, 01 January 2020 22:54 UTC

We are aware of issues within Azure Monitor services and are actively investigating. Some customers may experience query and alerting failures against the data stored in West Europe and East US regions. 
  • Work Around: Retry your operation as needed.
  • Next Update: Before 01/02 01:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Chandar