Update: Monday, 19 July 2021 20:25 UTC
Service Map in East Japan has had extended data latency. This is due to a new deployment with updated endpoints that were not reflected in a downstream portion of the service. To address this issue we are updating the endpoints which should bring in all the latent data. This could have caused errors when viewing network dependency map as well as data latency in your VMComputer, VMProcess, VMBoundPort and VMConnection tables in your Log Analytics Workspaces. This latency could also have caused missed or misfired alerts if you are using the tables listed.
Service Map in East Japan has had extended data latency. This is due to a new deployment with updated endpoints that were not reflected in a downstream portion of the service. To address this issue we are updating the endpoints which should bring in all the latent data. This could have caused errors when viewing network dependency map as well as data latency in your VMComputer, VMProcess, VMBoundPort and VMConnection tables in your Log Analytics Workspaces. This latency could also have caused missed or misfired alerts if you are using the tables listed.
- Work Around: none
- Next Update: Before 07/19 22:30 UTC
