This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Saturday, 05 October 2019 00:48 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/5, 00:40 UTC. Our logs show the incident started on 10/4, 23:10 UTC and that during the 1.5 hours that it took to resolve the issue less than 2% of customers experienced data loss or ingestion latency.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 10/5, 00:40 UTC. Our logs show the incident started on 10/4, 23:10 UTC and that during the 1.5 hours that it took to resolve the issue less than 2% of customers experienced data loss or ingestion latency.
- Root Cause: The failure was due to dependent backend service degradation.
- Incident Timeline: 1 Hours & 30 minutes
-Jeff
Update: Saturday, 05 October 2019 00:41 UTC
Root cause has been isolated to a dependent service degradation which was impacting ingestion in Korea Central region. To address this issue we temporarily redirected traffic to a functioning region. Once dependent service was fixed, traffic was redirected back. Application Insights is now working as expected in Korea Central.
Root cause has been isolated to a dependent service degradation which was impacting ingestion in Korea Central region. To address this issue we temporarily redirected traffic to a functioning region. Once dependent service was fixed, traffic was redirected back. Application Insights is now working as expected in Korea Central.
- Next Update: Before 10/05 02:00 UTC
Initial Update: Friday, 04 October 2019 23:14 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Latency and Data Loss in Central Korea region.
Work Around: None
Next Update: Before 10/05 01:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff
Work Around: None
Next Update: Before 10/05 01:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff