Home
%3CLINGO-SUB%20id%3D%22lingo-sub-834093%22%20slang%3D%22en-US%22%3EExperiencing%20Metric%20Creation%20failure%20for%20Application%20Gateway%20resources%20-%2009%2F03%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834093%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%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2003%20September%202019%2013%3A48%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20with%20Metric%20alert%20creation%20on%20a%20subset%20of%20metrics%20for%20Application%20Gateways%20resource%20type.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Customers%20continue%20to%20experience%20metric%20alerts%20creation%20failure%20for%20a%20subset%20of%20metrics%20(Current%20Capacity%20Units%2C%20Current%20Compute%20Units%2C%20Backend%20Response%20Status%2C%20Client%20TLS%20Protocol%2C%20Bytes%20Sent%2C%20Bytes%20Received%2C%20Client%20RTT%2C%20Application%20Gateway%20Total%20Time%2C%20Backend%20Connect%20Time%2C%20Backend%20First%20Byte%20Response%20Time%2C%20Backend%20Last%20Byte%20Response%20Time)%20for%20Application%20Gateways%20resource%20type.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20on%2008%2F22.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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%2009%2F04%2014%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Rama%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%20Tuesday%2C%2003%20September%202019%2007%3A52%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20in%20creating%20metrics%20alerts%20on%20a%26nbsp%3B%20subset%20of%20metrics%20for%20Application%20Gateway%20resources%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20failures%20in%20creating%20metric%20alerts%20on%20a%20subset%20of%20metrics%20for%20Application%20Gateway%20resources.%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%2F03%2010%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Rama%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-834093%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 09 September 2019 08:05 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/08, 13:00 UTC. Our logs show the incident started on 08/22, 13:00 UTC and that during the 17 days that it took to resolve the issue customers who were trying to create metric alerts would have experienced failure for a subset of metrics (Current Capacity Units, Current Compute Units, Backend Response Status, Client TLS Protocol, Bytes Sent, Bytes Received, Client RTT, Application Gateway Total Time, Backend Connect Time, Backend First Byte Response Time, Backend Last Byte Response Time) for Application Gateways resource type. These metrics alerts were not live for customer but due to bad deployment these metrics were shown up in portal. We have now disabled the subset of metrics from portal.

  • Root Cause: The subset of metrics for Application Gateways resource type would not have shown up in portal as they were still in testing phase.
  • Incident Timeline: 17 days - 08/22, 13:00 UTC through 09/08, 13:00 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Rama

Update: Friday, 06 September 2019 10:38 UTC

We continue to investigate issues with Metric alert creation on a subset of metrics for Application Gateways resource type. Root cause is not fully understood at this time. Customers continue to experience metric alerts creation failure for a subset of metrics (Current Capacity Units, Current Compute Units, Backend Response Status, Client TLS Protocol, Bytes Sent, Bytes Received, Client RTT, Application Gateway Total Time, Backend Connect Time, Backend First Byte Response Time, Backend Last Byte Response Time) for Application Gateways resource type. We are working to establish the start time for the issue, initial findings indicate that the problem began on 08/22. We currently have no estimate for resolution.

  • Work Around: None
  • Next Update: Before 09/07 11:00 UTC
-Rama

Update: Wednesday, 04 September 2019 13:11 UTC

We continue to investigate issues with Metric alert creation on a subset of metrics for Application Gateways resource type. Root cause is not fully understood at this time. Customers continue to experience metric alerts creation failure for a subset of metrics (Current Capacity Units, Current Compute Units, Backend Response Status, Client TLS Protocol, Bytes Sent, Bytes Received, Client RTT, Application Gateway Total Time, Backend Connect Time, Backend First Byte Response Time, Backend Last Byte Response Time) for Application Gateways resource type. We are working to establish the start time for the issue, initial findings indicate that the problem began on 08/22. We currently have no estimate for resolution.

  • Work Around: None
  • Next Update: Before 09/05 13:30 UTC
-Rama

Update: Tuesday, 03 September 2019 13:48 UTC

We continue to investigate issues with Metric alert creation on a subset of metrics for Application Gateways resource type. Root cause is not fully understood at this time. Customers continue to experience metric alerts creation failure for a subset of metrics (Current Capacity Units, Current Compute Units, Backend Response Status, Client TLS Protocol, Bytes Sent, Bytes Received, Client RTT, Application Gateway Total Time, Backend Connect Time, Backend First Byte Response Time, Backend Last Byte Response Time) for Application Gateways resource type. We are working to establish the start time for the issue, initial findings indicate that the problem began on 08/22. We currently have no estimate for resolution.

  • Work Around: None
  • Next Update: Before 09/04 14:00 UTC
-Rama

Initial Update: Tuesday, 03 September 2019 07:52 UTC

We are aware of issues in creating metrics alerts on a  subset of metrics for Application Gateway resources and are actively investigating. Some customers may experience failures in creating metric alerts on a subset of metrics for Application Gateway resources.
  • Work Around: None
  • Next Update: Before 09/03 10:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Rama