Update: Monday, 02 August 2021 04:12 UTC
***** REPOSTING COMMS AS NO UPDATE FROM ENGINEERING TEAM ****
Root cause has been isolated to
miss configuration of some of WUS2 log analytics backend clusters which was impacting the data ingestion leading to missing alerts and data. To address this issue we applied missing configuration to some of WUS2 Log analytics Backend servers.
The service is processing the backlog ingestion data which should take ~2 hours. Some customers may experience missing alerts and data and we estimate several hours before all missing alerts and data to be made available.
- Work Around: none
- Next Update: Before 08/02 03:30 UTC
-v-arishb
Update: Sunday, 01 August 2021 23:14 UTC
Root cause has been isolated to
miss configuration of some of WUS2 log analytics backend clusters which was impacting the data ingestion leading to missing alerts and data. To address this issue we applied missing configuration to some of WUS2 Log analytics Backend servers.
The service is processing the backlog ingestion data which should take ~2 hours. Some customers may experience missing alerts and data and we estimate several hours before all missing alerts and data to be made available.
- Work Around: none
- Next Update: Before 08/02 03:30 UTC
-v-arishb
Initial Update: Sunday, 01 August 2021 18:27 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delay in data ingestion into Log Analytics in West US2 .
- Work Around:
- Next Update: Before 08/01 22:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Subhash