%3CLINGO-SUB%20id%3D%22lingo-sub-353401%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20Custom%20Metrics%20from%20MDM%20-%2001%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353401%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jan%2027%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CDIV%3E%0A%20%20%20%3CDIV%3EFinal%20Update%3A%20Sunday%2C%2027%20January%202019%2011%3A10%20UTC%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%201%2F27%2C%2008%3A59%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%201%2F26%2C%2023%3A15%20UTC%20and%20that%20during%20the%20approximately%209%20hours%2044%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20all%20customers%20in%20Southeast%20Asia%20and%20West%20US%2C%20and%20~25%25%26nbsp%3B%20customers%20in%20East%20US%20will%20not%20be%20able%20to%20see%20(public%20preview)%20custom%20metrics%20between%20the%20start%20and%20end%20times%20of%20the%20incident.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%3CLI%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20a%20backend%20cluster%20becoming%20unhealthy.%3C%2FLI%3E%0A%20%20%20%20%20%3CLI%3EIncident%20Timeline%3A%209%20Hours%20%26amp%3B%2044%20minute%20-%201%2F26%2C%2023%3A15%20UTC%20through%201%2F27%2C%2008%3A59%20UTC%3C%2FLI%3E%0A%20%20%20%20%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20-Anmol%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%20%3CDIV%3E%0A%20%20%20%20%3CDIV%3E%0A%20%20%20%20%20%3CDIV%3EUpdate%3A%20Sunday%2C%2027%20January%202019%2005%3A31%20UTC%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20in%20West%20US%20also%20may%20experience%20Data%20Gaps%20in%20their%20custom%20metrics%20originating%20from%20MDM.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%20%20%3CLI%3EWork%20Around%3A%20none%3C%2FLI%3E%0A%20%20%20%20%20%20%20%3CLI%3ENext%20Update%3A%20Before%2001%2F27%2009%3A00%20UTC%3C%2FLI%3E%0A%20%20%20%20%20%20%3C%2FUL%3E-Anmol%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%20%20%20%3CDIV%3E%0A%20%20%20%20%20%20%3CDIV%3EInitial%20Update%3A%20Sunday%2C%2027%20January%202019%2001%3A17%20UTC%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20in%20Southeast%20Asia%20may%20experience%20Data%20Gaps%20in%20their%20custom%20metrics%20originating%20from%20MDM%20beginning%20at%2001%2F26%2023%3A20%20UTC%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%20%20%20%20%3CDIV%3E%0A%20%20%20%20%20%20%20%3CUL%3E%0A%20%20%20%20%20%20%20%20%3CLI%3EWork%20Around%3A%20none%3C%2FLI%3E%0A%20%20%20%20%20%20%20%20%3CLI%3ENext%20Update%3A%20Before%2001%2F27%2005%3A30%20UTC%3C%2FLI%3E%0A%20%20%20%20%20%20%20%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%20%3CBR%20%2F%3E%20-Venkat%3C%2FDIV%3E%0A%20%20%20%20%20%3C%2FDIV%3E%0A%20%20%20%20%3C%2FDIV%3E%0A%20%20%20%3C%2FDIV%3E%0A%20%20%3C%2FDIV%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-353401%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jan%2027%2C%202019%20Final%20Update%3A%20Sunday%2C%2027%20January%202019%2011%3A10%20UTCWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%201%2F27%2C%2008%3A59%20UTC.%3C%2FLINGO-TEASER%3E
First published on MSDN on Jan 27, 2019
Final Update: Sunday, 27 January 2019 11:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 1/27, 08:59 UTC. Our logs show the incident started on 1/26, 23:15 UTC and that during the approximately 9 hours 44 minutes that it took to resolve the issue, all customers in Southeast Asia and West US, and ~25%  customers in East US will not be able to see (public preview) custom metrics between the start and end times of the incident.
  • Root Cause: The failure was due to a backend cluster becoming unhealthy.
  • Incident Timeline: 9 Hours & 44 minute - 1/26, 23:15 UTC through 1/27, 08:59 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Anmol
Update: Sunday, 27 January 2019 05:31 UTC

We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers in West US also may experience Data Gaps in their custom metrics originating from MDM.
  • Work Around: none
  • Next Update: Before 01/27 09:00 UTC
-Anmol
Initial Update: Sunday, 27 January 2019 01:17 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers in Southeast Asia may experience Data Gaps in their custom metrics originating from MDM beginning at 01/26 23:20 UTC
  • Work Around: none
  • Next Update: Before 01/27 05:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Venkat