%3CLINGO-SUB%20id%3D%22lingo-sub-1351550%22%20slang%3D%22en-US%22%3EData%20Latency%20and%20Data%20Gaps%20Issue%20for%20Log%20Analytics%20and%20Service%20Map%20-%2004%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1351550%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%2001%20May%202020%2000%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F30%2C%2022%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F30%2C%2018%3A50%20UTC%20and%20that%20during%20the%204%20hours%205%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20in%20South%20UK%20region%20might%20have%20experienced%20data%20latency%20and%20data%20gap%20issues%20for%20Log%20Analytics%20and%20Service%20Map.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20the%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20%26amp%3B%205%20minutes%20-%2004%2F30%2C%2018%3A50%20UTC%20through%2004%2F30%2C%2022%3A55%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20and%20Service%20Map%20as%20a%20critical%20services%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Leela%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2030%20April%202020%2023%3A11%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20investigating%20issues%20within%20Log%20Analytics%20and%20Service%20Map.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20data%20latency%20and%20data%20gaps%20issues%20in%20South%20UK.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2004%2F30%20~18%3A50%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20details%3D%22%22%20or%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F01%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Leela%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-1351550%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EService%20Map%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 01 May 2020 00:03 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/30, 22:55 UTC. Our logs show the incident started on 04/30, 18:50 UTC and that during the 4 hours 5 minutes that it took to resolve the issue some of customers in South UK region might have experienced data latency and data gap issues for Log Analytics and Service Map.
  • Root Cause: The failure was due to the issue in one of our dependent services.
  • Incident Timeline: 4 Hours & 5 minutes - 04/30, 18:50 UTC through 04/30, 22:55 UTC
We understand that customers rely on Azure Log Analytics and Service Map as a critical services and apologize for any impact this incident caused.

-Leela

Update: Thursday, 30 April 2020 23:11 UTC

We are investigating issues within Log Analytics and Service Map. Root cause is not fully understood at this time. Some customers continue to experience data latency and data gaps issues in South UK. We are working to establish the start time for the issue, initial findings indicate that the problem began at 04/30 ~18:50 UTC. We currently have no estimate for resolution.
  • Work Around:
  • Next Update: Before 05/01 03:30 UTC
-Leela