Home
%3CLINGO-SUB%20id%3D%22lingo-sub-897908%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2010%2F07%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897908%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%20Monday%2C%2007%20October%202019%2020%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E10%2F7%2C%2020%3A37%20UTC%3C%2FSPAN%3E.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F7%2C%2020%3A02%20UTC%20and%20that%20during%20the%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20few%20customers%20might%20have%20experienced%20alerting%20and%20query%20failures.%3CUL%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B%2035%20minutes%20-%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E10%2F7%2C%2020%3A02%20UTC%3C%2FSPAN%3E%20through%20%3CSPAN%20style%3D%22background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20box-sizing%3A%20border-box%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20%26amp%3Bquot%3BHelvetica%20Neue%26amp%3Bquot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E10%2F7%2C%2020%3A37%20UTC%3C%2FSPAN%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-Anupama%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%20Monday%2C%2007%20October%202019%2020%3A34%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CP%20style%3D%22margin-bottom%3A12.0pt%22%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%26quot%3BHelvetica%26quot%3B%2Csans-serif%3B%0Acolor%3Ablack%3Bbackground%3Awhite%22%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20in%20West%20Europe%20might%20experience%20alerting%20failures%20and%20query%20failures.%3C%2FSPAN%3E%3C%2FP%3E%0A%0A%3CUL%20type%3D%22disc%22%3E%0A%20%3CLI%20style%3D%22color%3A%20black%3B%20font-family%3A%3B%20font-size%3A%2010.5pt%3B%20font-style%3A%20normal%3B%20font-weight%3A%20400%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%26quot%3B%26quot%3B%26quot%3B%2Cserif%3Bmso-fareast-font-family%3A%0A%20%20%20%20%20%26quot%3BTimes%20New%20Roman%26quot%3B%22%3EWork%20Around%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3B%0A%20%20%20%20%20font-family%3A%26quot%3B%26quot%3B%26quot%3B%2Cserif%3Bmso-fareast-font-family%3A%26quot%3BTimes%20New%20Roman%26quot%3B%22%3E%3A%20none%3C%2FSPAN%3E%3C%2FLI%3E%0A%20%3CLI%20style%3D%22color%3A%20black%3B%20font-family%3A%3B%20font-size%3A%2010.5pt%3B%20font-style%3A%20normal%3B%20font-weight%3A%20400%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%26quot%3B%26quot%3B%26quot%3B%2Cserif%3Bmso-fareast-font-family%3A%0A%20%20%20%20%20%26quot%3BTimes%20New%20Roman%26quot%3B%22%3ENext%20Update%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3B%0A%20%20%20%20%20font-family%3A%26quot%3B%26quot%3B%26quot%3B%2Cserif%3Bmso-fareast-font-family%3A%26quot%3BTimes%20New%20Roman%26quot%3B%22%3E%3A%20Before%2010%2F07%2022%3A30%20UTC%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%0A%3CP%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%26quot%3BHelvetica%26quot%3B%2Csans-serif%3B%0Acolor%3Ablack%3Bbackground%3Awhite%22%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3B%0Afont-family%3A%26quot%3B%26quot%3B%26quot%3B%2Cserif%3Bcolor%3Ablack%22%3E%3CBR%20%2F%3E%20%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%26quot%3BHelvetica%26quot%3B%2Csans-serif%3B%0Acolor%3Ablack%3Bbackground%3Awhite%22%3E-Anupama%3C%2FSPAN%3E%3C%2FP%3E%0A%0A%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-897908%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 07 October 2019 20:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/7, 20:37 UTC. Our logs show the incident started on 10/7, 20:02 UTC and that during the 35 minutes that it took to resolve the issue few customers might have experienced alerting and query failures.
  • Incident Timeline:  35 minutes - 10/7, 20:02 UTC through 10/7, 20:37 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Anupama

Initial Update: Monday, 07 October 2019 20:34 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers in West Europe might experience alerting failures and query failures.

  • Work Around: none
  • Next Update: Before 10/07 22:30 UTC

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