Home
%3CLINGO-SUB%20id%3D%22lingo-sub-658906%22%20slang%3D%22en-US%22%3ERe%3A%20Experiencing%20Alerting%20Failure%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2005%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658906%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20still%20seeing%20no%20tracing%20log%20in%20my%20app%20insight.%20The%20last%20log%20was%20from%205%2F28%2F2019%2C%206%3A05%3A03%20PM.%20Is%20this%20issue%20still%20going%20on%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-657489%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20Failure%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2005%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-657489%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%20Thursday%2C%2030%20May%202019%2006%3A11%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F30%2C%2006%3A11%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F28%2C%2021%3A20%20UTC%20and%20that%20during%20the%202%20hours%2010%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20~3%25%20of%20subscriptions%20got%20impacted%20and%20experienced%20data%20gaps%20in%20availability%20results.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2010%20minutes%20-%2005%2F28%2C%2021%3A20%20UTC%20through%2005%2F28%2C%2023%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%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-Sindhu%3CBR%20%2F%3E%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-657489%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 30 May 2019 06:11 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/30, 06:11 UTC. Our logs show the incident started on 05/28, 21:20 UTC and that during the 2 hours 10 minutes that it took to resolve the issue ~3% of subscriptions got impacted and experienced data gaps in availability results.
  • Root Cause: The failure was due to issue in one of our backend services.
  • Incident Timeline: 2 Hours & 10 minutes - 05/28, 21:20 UTC through 05/28, 23:30 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Sindhu

1 Comment
Occasional Visitor

I am still seeing no tracing log in my app insight. The last log was from 5/28/2019, 6:05:03 PM. Is this issue still going on?