%3CLINGO-SUB%20id%3D%22lingo-sub-1374346%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20Issue%20in%20Azure%20portal%20for%20Log%20Search%20Alerts%20-%2005%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1374346%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%20Friday%2C%2008%20May%202020%2014%3A53%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F08%2C%2011%3A20%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F08%2C%2010%3A30%20UTC%20and%20that%20during%20the%20%3CSPAN%20style%3D%22color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20start%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20white-space%3A%20normal%3B%20widows%3A%202%3B%20word-spacing%3A%200px%3B%20-webkit-text-stroke-width%3A%200px%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20text-decoration-style%3A%20initial%3B%20text-decoration-color%3A%20initial%3B%20display%3A%20inline%20!important%3B%20float%3A%20none%3B%22%3E%3CSPAN%3E%26nbsp%3B50%20minutes%3C%2FSPAN%3E%3C%2FSPAN%3E%26nbsp%3Bthat%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20might%20have%20experienced%20missed%20Activity%20Log%20Alerts%2C%20Metric%20Alerts%2C%20Smart%20Detector%20Alerts%20in%20all%20regions.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20our%20back%20end%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2050%20minutes%20-%2005%2F08%2C%2010%3A30%20UTC%20through%2005%2F08%2C%2011%3A20%20UTC%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-Satya%3CBR%20%2F%3E%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-1374346%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 08 May 2020 14:53 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/08, 11:20 UTC. Our logs show the incident started on 05/08, 10:30 UTC and that during the  50 minutes that it took to resolve the issue some of customers might have experienced missed Activity Log Alerts, Metric Alerts, Smart Detector Alerts in all regions.
  • Root Cause: The failure was due to one of our back end service.
  • Incident Timeline: 50 minutes - 05/08, 10:30 UTC through 05/08, 11:20 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Satya