%3CLINGO-SUB%20id%3D%22lingo-sub-2109794%22%20slang%3D%22en-US%22%3EData%20Gap%20issue%20in%20Azure%20Monitor%20Service%20-%2002%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2109794%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Monday%2C%2001%20February%202021%2011%3A34%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F01%2C%2011%3A20%20UTC.%26nbsp%3BWe%20have%20been%20tracking%20an%20issue%20in%20Azure%20Monitor%20services%20which%20may%20have%20impacted%20a%20subset%20of%20customers%20in%20regions%20Norway%20East%2C%20UAE%20North%2C%20Brazil%20South%26nbsp%3B%20East%2C%20Germany%20West.%20Affected%20customers%20may%20have%20experienced%20some%20data%20gaps%20for%20their%20data%20ingested%20to%20some%20of%20Azure%20Monitor%20solutions%20but%20impact%20is%20very%20minimal.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20configuration%20changes%20in%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Service%20Map%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Mohini%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%20Monday%2C%2001%20February%202021%2010%3A28%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20been%20tracking%20an%20issue%20in%20Azure%20Monitor%20services%20which%20might%20have%20impacted%20a%20subset%20of%20customers%20in%20regions%20Norway%20East%2C%20UAE%20North%2C%20Brazil%20South%20East%2C%20Germany%20West.%20Affected%20customer%20might%20see%20some%20data%20gaps%20for%20their%20data%20ingested%20to%20some%20of%20Azure%20Monitor%20solutions%20but%20impact%20is%20very%20minimal.%20We%20provide%20more%20information%20about%20this%20issue%20as%20we%20progress%20the%20investigation.%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%2002%2F02%2010%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Mohini%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2109794%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EService%20Map%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 01 February 2021 11:34 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/01, 11:20 UTC. We have been tracking an issue in Azure Monitor services which may have impacted a subset of customers in regions Norway East, UAE North, Brazil South  East, Germany West. Affected customers may have experienced some data gaps for their data ingested to some of Azure Monitor solutions but impact is very minimal.
  • Root Cause: The failure was due to configuration changes in one of our dependent service.
We understand that customers rely on Service Map as a critical service and apologize for any impact this incident caused.

-Mohini

Initial Update: Monday, 01 February 2021 10:28 UTC

We have been tracking an issue in Azure Monitor services which might have impacted a subset of customers in regions Norway East, UAE North, Brazil South East, Germany West. Affected customer might see some data gaps for their data ingested to some of Azure Monitor solutions but impact is very minimal. We provide more information about this issue as we progress the investigation.
  • Work Around: None
  • Next Update: Before 02/02 10:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Mohini