%3CLINGO-SUB%20id%3D%22lingo-sub-1129634%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20loss%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2001%2F25%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1129634%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%20Saturday%2C%2025%20January%202020%2003%3A23%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20at%201%2F24%2C%2021%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%201%2F24%2C%2020%3A40%20UTC%20and%20that%20during%201%20hour%2015%20min%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20in%20Central%20India%20experienced%20data%20loss%20in%20heartbeat%20events.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20incorrect%20configuration%20value%20during%20migration%20of%20heartbeat%20datatype.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2015%20minutes%20-1%2F24%2C%2020%3A40%20UTC%20through%201%2F24%2C%2021%3A55%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%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%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1129634%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 25 January 2020 03:23 UTC

We've confirmed that all systems are back to normal at 1/24, 21:55 UTC. Our logs show the incident started on 1/24, 20:40 UTC and that during 1 hour 15 min that it took to resolve the issue customers in Central India experienced data loss in heartbeat events.

  • Root Cause: The failure was due to incorrect configuration value during migration of heartbeat datatype.
  • Incident Timeline: 1 Hour & 15 minutes -1/24, 20:40 UTC through 1/24, 21:55 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Anupama