Home
%3CLINGO-SUB%20id%3D%22lingo-sub-830336%22%20slang%3D%22en-US%22%3EExperiencing%20Issues%20in%20Azure%20Log%20Analytics%20Services%20in%20UK%20South%20-%2008%2F29%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-830336%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Thursday%2C%2029%20August%202019%2021%3A27%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F29%2C%2020%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F29%2C%2019%3A31%20UTC%20and%20that%20during%20the%2044%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%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%3Ea%20subset%20of%20customers%20might%20have%20experienced%20issue%20in%20Log%20Search%20Alerts%20as%20well%20as%20querying%20the%20data%20in%20UK%20South.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%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%3EThe%20failure%20was%20due%20to%20load%20on%20our%20storage%20system%20which%20is%20responsible%20for%20data%20ingestion%20and%20query%20system%3C%2FSPAN%3E.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2044%20minutes%20-%2008%2F29%2C%2019%3A31%20UTC%26nbsp%3B%26nbsp%3Bthrough%2008%2F29%2C%2020%3A15%20UTC%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-Venkat%3CBR%20%2F%3E%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-830336%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 29 August 2019 21:27 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/29, 20:15 UTC. Our logs show the incident started on 08/29, 19:31 UTC and that during the 44 minutes that it took to resolve the issue a subset of customers might have experienced issue in Log Search Alerts as well as querying the data in UK South.
  • Root CauseThe failure was due to load on our storage system which is responsible for data ingestion and query system.
  • Incident Timeline: 44 minutes - 08/29, 19:31 UTC  through 08/29, 20:15 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Venkat