This article is contributed. See the original author and article here.
Final Update: Tuesday, 12 January 2021 22:44 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 01/12, 22:28 UTC. Our logs show the incident started on 01/12, 20:35 UTC and that during the 1 hours & 54 minutes that it took to resolve the issue only 24 subscriptions of customers experienced connectivity failures when attempting to establish connections to Log Analytics ingestion endpoint. Additionally, customers may have also experienced their Log Search alerts missing or fired incorrectly..
-Arish B
We’ve confirmed that all systems are back to normal with no customer impact as of 01/12, 22:28 UTC. Our logs show the incident started on 01/12, 20:35 UTC and that during the 1 hours & 54 minutes that it took to resolve the issue only 24 subscriptions of customers experienced connectivity failures when attempting to establish connections to Log Analytics ingestion endpoint. Additionally, customers may have also experienced their Log Search alerts missing or fired incorrectly..
- Root Cause: The failure was due to a
certificate configuration issue in a recent deployment preventing customers from establishing connections to the Log Analytics ingestion endpoint.. - Incident Timeline: 1 hours & 54 minutes – 01/12, 20:35 UTC through 01/12, 22:28 UTC
-Arish B
Update: Tuesday, 12 January 2021 21:53 UTC
Root cause has been isolated to a certificate configuration issue in a recent deployment which resulted in Log analytics not accepting OMS ingestion data. To address this issue we are deploying a corrected certificate to the Brazil region. Some customers may experience residual affect and we estimate 1 hour before all data loss or connection issue is addressed.
Start time: 2021-01-12 20:35 UTC
- Work Around: None
- Next Update: Before 01/13 00:00 UTC
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments