Home
%3CLINGO-SUB%20id%3D%22lingo-sub-880505%22%20slang%3D%22en-US%22%3EExperiencing%20Ingestion%20Latency%20in%20Azure%20portal%20for%20Metric%20Alerts%20in%20SEAU%20-%2009%2F28%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880505%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%2028%20September%202019%2011%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%2009%2F28%2C%2010%3A48%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F28%2C%2007%3A15%20UTC%20and%20that%20during%20the%203%20hours%20%26amp%3B%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20of%20some%20customers%20experienced%20Alerting%20failure%20due%20to%20Ingestion%20Latency%20in%20South%20East%20Australia.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20back-end%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2035%20minutes%20-%2009%2F28%2C%2007%3A15%20UTC%20through%2009%2F28%2C%2010%3A48%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-Naresh%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%3EInitial%20Update%3C%2FU%3E%3A%20Saturday%2C%2028%20September%202019%2008%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Metric%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20ingestion%20latency%20causing%20alerting%20failure%20in%20South%20East%20Australia.%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%2009%2F28%2012%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Naresh%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-880505%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 28 September 2019 11:03 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/28, 10:48 UTC. Our logs show the incident started on 09/28, 07:15 UTC and that during the 3 hours & 35 minutes that it took to resolve the issue of some customers experienced Alerting failure due to Ingestion Latency in South East Australia.
  • Root Cause: The failure was due to issue in back-end service.
  • Incident Timeline: 3 Hours & 35 minutes - 09/28, 07:15 UTC through 09/28, 10:48 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Naresh

Initial Update: Saturday, 28 September 2019 08:41 UTC

We are aware of issues within Metric Alerts and are actively investigating. Some customers may experience ingestion latency causing alerting failure in South East Australia.
  • Work Around: None
  • Next Update: Before 09/28 12:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Naresh