This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 06 October 2021 13:49 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/06, 13:35 UTC. Our logs show the incident started on 10/06, 09:14 UTC and that during the 4 hours and 21 minutes that it took to resolve the issue, some customers ingesting telemetry in their Log Analytics workspaces in East US region may have experienced intermittent data latency and incorrect alert activation.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 10/06, 13:35 UTC. Our logs show the incident started on 10/06, 09:14 UTC and that during the 4 hours and 21 minutes that it took to resolve the issue, some customers ingesting telemetry in their Log Analytics workspaces in East US region may have experienced intermittent data latency and incorrect alert activation.
- Root Cause: We determined that downstream impact from an Events Hub issue caused instances upon which Log Analytics relies on to become unhealthy. This resulted in impact for requests that landed in these instances.
- Incident Timeline: 4 Hours & 21 minutes - 10/06, 09:14 UTC through 10/6, 13:35 UTC
-Anmol
Initial Update: Wednesday, 06 October 2021 11:47 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in their Log Analytics workspaces in East US region may experience intermittent data latency and incorrect alert activation. We are currently investigating the issue.
-Anmol
We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in their Log Analytics workspaces in East US region may experience intermittent data latency and incorrect alert activation. We are currently investigating the issue.
- Work Around: None
- Next Update: Before 10/06 15:00 UTC
-Anmol