%3CLINGO-SUB%20id%3D%22lingo-sub-1991129%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2012%2F15%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1991129%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EFinal%20Update%3C%2FU%3E%3A%20Wednesday%2C%2016%20December%202020%2007%3A53%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%2F16%2C%2007%3A35%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F01%2C%2023%3A00%20UTC%20and%20that%20during%20the%2014%20days%208%20Hours%2035%20Minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20may%20have%20experienced%20duplicate%20notifications%20for%20unhealthy%20metric%20alerts%20that%20only%20contain%20non-ascii%20characters%20in%20the%20name%20of%20the%20alert.%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20We%20identified%20the%20issue%20was%20caused%20by%20a%20recent%20deployment%20that%20introduced%20a%20configuration%20incompatibility%20between%20dependent%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2014%20days%208%20Hours%20%26amp%3B%2035%20minutes%20-%2012%2F01%2C%2023%3A00%20UTC%20through%2012%2F16%2C%2007%3A35%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2016%20December%202020%2006%3A27%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20new%20feature%20rollout%20which%20was%20causing%20duplicate%20notification%20when%20resource%20was%20unhealthy%20for%20some%20customer%20in%20the%20azure%20portal.%20Specifically%2C%20any%20metric%20alert%20names%20with%20non%20ascii%20characters%20see%20this%20impact.%20To%20address%20the%20issue%2C%20we've%20started%20mitigation%20to%20disable%20the%20feature.%20Some%20customers%20may%20still%20continue%20to%20see%20notifications%20and%20we%20estimate%204%20hours%20before%20all%20is%20addressed.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EMitigation%20Steps%3C%2FU%3E%3A%20Redeploying%20with%20new%20feature%20to%20disable%20the%20alert%20notification%20is%20in%20progress%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2012%2F16%2010%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Vamshi%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%20Wednesday%2C%2016%20December%202020%2002%3A45%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20new%20feature%20rollout%20which%20was%20causing%20duplicate%20notification%20when%20resource%20was%20unhealthy%20for%20some%20customer%20in%20the%20azure%20portal.%20Specifically%2C%20any%20metric%20alert%20names%20with%20non%20ascii%20characters%20see%20this%20impact.%20To%20address%20the%20issue%2C%20we've%20started%20mitigation%20to%20disable%20the%20feature.%20Some%20customers%20may%20still%20continue%20to%20see%20notifications%20and%20we%20estimate%204%20hours%20before%20all%20is%20addressed.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EMitigation%20Steps%3C%2FU%3E%3A%20Redeploying%20with%20new%20feature%20disabled%20is%20in%20progress.%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2012%2F16%2007%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Vincent%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2015%20December%202020%2022%3A17%20UTC%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3ERoot%20cause%20has%20been%20isolated%20to%20new%20feature%20rollout%20which%20was%20causing%20duplicate%20notification%20when%20resource%20was%20unhealthy%20for%20some%20customer%20in%20the%20azure%20portal.%20Specifically%2C%20any%20metric%20alert%20names%20with%20non%20ascii%20characters%20see%20this%20impact.%20To%20address%20the%20issue%2C%20we've%20started%20mitigation%20to%20disable%20the%20feature.%20Some%20customers%20may%20continue%20to%20see%20notifications%20and%20we%20estimate%204%20hours%20before%20all%20is%20addressed.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3ERoot%20Cause%3A%20%3C%2FSPAN%3ENew%20feature%20rollout%20which%20was%20causing%20duplicate%20notification.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3E%26nbsp%3BIncident%20Timeline%3A%3C%2FSPAN%3E%26nbsp%3B%2014%20day%2023%20hours%20-%2012%2F01%2C%2023%3A00%20UTC%20through%20on%20going%2012%2F15%2C%2022%3A00%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3ENext%20Update%3A%3C%2FSPAN%3E%20Before%2012%2F16%2001%3A30%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E-Vincent%3C%2FDIV%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%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1991129%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 16 December 2020 07:53 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/16, 07:35 UTC. Our logs show the incident started on 12/01, 23:00 UTC and that during the 14 days 8 Hours 35 Minutes that it took to resolve the issue some of customers may have experienced duplicate notifications for unhealthy metric alerts that only contain non-ascii characters in the name of the alert.
  • Root Cause: We identified the issue was caused by a recent deployment that introduced a configuration incompatibility between dependent services.
  • Incident Timeline: 14 days 8 Hours & 35 minutes - 12/01, 23:00 UTC through 12/16, 07:35 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Vamshi

Update: Wednesday, 16 December 2020 06:27 UTC

Root cause has been isolated to new feature rollout which was causing duplicate notification when resource was unhealthy for some customer in the azure portal. Specifically, any metric alert names with non ascii characters see this impact. To address the issue, we've started mitigation to disable the feature. Some customers may still continue to see notifications and we estimate 4 hours before all is addressed.
  • Mitigation Steps: Redeploying with new feature to disable the alert notification is in progress
  • Next Update: Before 12/16 10:30 UTC
-Vamshi

Update: Wednesday, 16 December 2020 02:45 UTC

Root cause has been isolated to new feature rollout which was causing duplicate notification when resource was unhealthy for some customer in the azure portal. Specifically, any metric alert names with non ascii characters see this impact. To address the issue, we've started mitigation to disable the feature. Some customers may still continue to see notifications and we estimate 4 hours before all is addressed.
  • Mitigation Steps: Redeploying with new feature disabled is in progress.
  • Next Update: Before 12/16 07:00 UTC
-Vincent

Update: Tuesday, 15 December 2020 22:17 UTC

Root cause has been isolated to new feature rollout which was causing duplicate notification when resource was unhealthy for some customer in the azure portal. Specifically, any metric alert names with non ascii characters see this impact. To address the issue, we've started mitigation to disable the feature. Some customers may continue to see notifications and we estimate 4 hours before all is addressed.
    Root Cause: New feature rollout which was causing duplicate notification.
    Incident Timeline:  14 day 23 hours - 12/01, 23:00 UTC through on going 12/15, 22:00 UTC
    Next Update: Before 12/16 01:30 UTC

-Vincent