Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1056212%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20in%20Log%20Analytics%20Workspaces%20-%2012%2F09%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1056212%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%2009%20December%202019%2018%3A43%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2012%2F09%2C%2018%3A34%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F09%2C%2017%3A27%20UTC%20and%20that%20during%20the%201%20hour%20and%207%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20could%20have%20experienced%20missing%20alerts%20in%20West%20Europe.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20bad%20configuration%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%207%20minutes%20-%2012%2F09%2C%2017%3A27%20UTC%20through%2012%2F09%2C%2018%3A34%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Metric%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Eric%20Singleton%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%20Monday%2C%2009%20December%202019%2018%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20a%20bad%20configuration%20which%20was%20impacting%20alerting.%20To%20address%20this%20issue%20we%20scaled%20out%20the%20deployment.%20Some%20customers%20may%20experience%20missing%20alerts%20in%20the%20West%20Europe%20Region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20none%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2012%2F09%2022%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Eric%20Singleton%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1056212%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 09 December 2019 18:43 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/09, 18:34 UTC. Our logs show the incident started on 12/09, 17:27 UTC and that during the 1 hour and 7 minutes that it took to resolve the issue customers could have experienced missing alerts in West Europe.
  • Root Cause: The failure was due to a bad configuration
  • Incident Timeline: 1 Hour & 7 minutes - 12/09, 17:27 UTC through 12/09, 18:34 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Update: Monday, 09 December 2019 18:08 UTC

Root cause has been isolated to a bad configuration which was impacting alerting. To address this issue we scaled out the deployment. Some customers may experience missing alerts in the West Europe Region.
  • Work Around: none
  • Next Update: Before 12/09 22:30 UTC
-Eric Singleton