%3CLINGO-SUB%20id%3D%22lingo-sub-716821%22%20slang%3D%22en-US%22%3EExperiencing%20Failure%20Anomaly%20Alerting%20Feature%20issue%20in%20Azure%20Portal%20-%2006%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-716821%22%20slang%3D%22en-US%22%3EFinal%20Update%3A%20Monday%2C%2024%20June%202019%2009%3A56%20UTCWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%206%2F23%2C%2009%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%206%2F1%2C%2008%3A00%20UTC%20and%20that%20during%20~22%20days%20that%20it%20took%20to%20resolve%20the%20issue%2C%20some%20customers%20would%20have%20impacted%20for%20Failure%20Anomaly%20Feature%20Alerts%20issue%20which%20would%20have%20caused%20no%20notification%20during%20impact%20duration.%20This%20issue%20would%20have%20impacted%20very%20limited%20set%20of%20customers%20who%20would%20have%20migrated%20from%20Classic%20to%20Modern%20Alerting%20experience%20during%20impact%20duration.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20our%20dependent%20service.%3CBR%20%2F%3EIncident%20Timeline%3A%2022%20Days%20%26amp%3Bamp%3B%201%20Hour%20-%206%2F1%2C%2008%3A00%20UTC%20through%206%2F23%2C%2009%3A00%20UTCWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Anmol%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-716821%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 24 June 2019 09:56 UTC

We've confirmed that all systems are back to normal with no customer impact as of 6/23, 09:00 UTC. Our logs show the incident started on 6/1, 08:00 UTC and that during ~22 days that it took to resolve the issue, some customers would have impacted for Failure Anomaly Feature Alerts issue which would have caused no notification during impact duration. This issue would have impacted very limited set of customers who would have migrated from Classic to Modern Alerting experience during impact duration.


Root Cause: The failure was due to an issue with one of our dependent service.
Incident Timeline: 22 Days & 1 Hour - 6/1, 08:00 UTC through 6/23, 09:00 UTCWe understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Anmol