%3CLINGO-SUB%20id%3D%22lingo-sub-1737935%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2010%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1737935%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Friday%2C%2002%20October%202020%2005%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F02%2C%2005%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F02%2C%2004%3A05%20UTC%20and%20that%20during%20the%201%20Hours%20%26amp%3B%2010%20minutes%20that%20it%20took%20to%20resolve%2C%20some%20customers%20may%20have%20experienced%20intermittent%20data%20latency%20and%20incorrect%20alert%20activation%20in%20Japan%20East%20Region.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20is%20due%20to%20configuration%20issues%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2010%20minutes%20-%2010%2F02%2C%2004%3A05%20UTC%20through%2010%2F02%2C%2005%3A15%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-Vamshi%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%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1737935%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 02 October 2020 05:41 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/02, 05:15 UTC. Our logs show the incident started on 10/02, 04:05 UTC and that during the 1 Hours & 10 minutes that it took to resolve, some customers may have experienced intermittent data latency and incorrect alert activation in Japan East Region.
  • Root Cause: The failure is due to configuration issues with one of our dependent service.
  • Incident Timeline: 1 Hours & 10 minutes - 10/02, 04:05 UTC through 10/02, 05:15 UTC.
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Vamshi