This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Tuesday, 01 March 2022 16:45 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/1, 16:37 UTC. Our logs show the incident started on 3/1, 14:31 UTC and that during the 2 hours that it took to resolve the issue customers in East US using classic Application Insights (not Workspace based) may have experienced data latency and data loss which could lead to delayed, missed or misfired Alerts.
-Ian
We've confirmed that all systems are back to normal with no customer impact as of 3/1, 16:37 UTC. Our logs show the incident started on 3/1, 14:31 UTC and that during the 2 hours that it took to resolve the issue customers in East US using classic Application Insights (not Workspace based) may have experienced data latency and data loss which could lead to delayed, missed or misfired Alerts.
- Root Cause: The failure was due to sudden a spike in ingestion data leading to an Event Hub being overloaded.
- Incident Timeline: 2 Hours & 6 minutes - 3/1, 14:31 UTC through 3/1, 16:37 UTC
-Ian
Initial Update: Tuesday, 01 March 2022 16:18 UTC
We are aware of issues within Application Insights ingestion in East US and are actively investigating. Some customers using classic Application Insights resources (not Log Analytics based resources) may experience data latency and data loss which could lead to delayed, missed or misfired Alerts.
-Ian
We are aware of issues within Application Insights ingestion in East US and are actively investigating. Some customers using classic Application Insights resources (not Log Analytics based resources) may experience data latency and data loss which could lead to delayed, missed or misfired Alerts.
- Work Around: None
- Next Update: Before 03/01 19:30 UTC
-Ian