Experiencing Data Correctness Issue in Azure Portal for Trace Data Type - 04/13 - Resolved


Final Update: Wednesday, 13 April 2016 21:35 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/13, 20:58 UTC. Our logs show the incident started on 5th April  and during the incident customers experienced incorrect count and chart for Trace data type.
  • Root Cause: The failure was due to change in request query pattern caused by recent change on UX side.

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Avinash


Update: Wednesday, 13 April 2016 20:44 UTC

Root cause has been isolated to one the recent deployment which had changes to query pattern. To address this issue we hotfixed the related service to handle change in query format . Hotfix deployment currently in progress.
  • Work Around: None
  • Next Update: Before 04/13 23:00 UTC

-Avinash


Initial Update: Wednesday, 13 April 2016 18:37 UTC

We are aware of issues within Application Insights and are actively investigating. Customers who have enabled Trace data type might see incorrect Trace count in Azure Portal. The Traces will still be displayed correctly but the Trace count would probably be incorrect. The following data types are affected: Trace.
  • Work Around: None
  • Next Update: Before 04/13 22:00 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Vamshi


Skip to main content