Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1171982%22%20slang%3D%22en-US%22%3EExperiencing%20failures%20in%20Alert%20creation%20for%20Metric%20Alerts%20-%2002%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1171982%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%20Thursday%2C%2013%20February%202020%2016%3A09%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F13%2C%2015%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F13%2C%2013%3A15%20UTC%20and%20that%20during%202%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20in%20WestUS2%20and%20CentralUS%20regions%20might%20have%20experienced%20issues%20while%20creating%20Metric%20Alerts%20during%20impact%20window.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20hours%20-%26nbsp%3B%2002%2F13%2C%2013%3A15%20UTC%20through%2002%2F13%2C%2015%3A15%20UTC%3C%2FLI%3E%0A%3C%2FUL%3E%3CDIV%3EWe%20understand%20that%20customers%20rely%20on%20Metric%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E-Santhosh%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Thursday%2C%2013%20February%202020%2014%3A52%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Metric%20Alerts%20and%20are%20actively%20investigating.%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%3ESome%20customers%20may%20experience%20failure%20in%20creating%20Metric%20Alerts%20during%20the%20impact.%3C%2FSPAN%3E%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%2002%2F13%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Santhosh%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-1171982%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 13 February 2020 16:09 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/13, 15:15 UTC. Our logs show the incident started on 02/13, 13:15 UTC and that during 2 hours that it took to resolve the issue some of customers in WestUS2 and CentralUS regions might have experienced issues while creating Metric Alerts during impact window.

  • Root Cause: The failure was due to issues with one of the dependent services.
  • Incident Timeline: 2 hours -  02/13, 13:15 UTC through 02/13, 15:15 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Santhosh

Initial Update: Thursday, 13 February 2020 14:52 UTC

We are aware of issues within Metric Alerts and are actively investigating. Some customers may experience failure in creating Metric Alerts during the impact.
  • Work Around: None
  • Next Update: Before 02/13 17:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Santhosh