Experiencing Data Latency for Azure Log Analytics - 07/15 - Resolved
Final Update: Friday, 15 July 2022 09:07 UTC
We've confirmed that all systems are back to normal with no customer impact as of 7/15, 09:00 UTC. Our logs show the incident started on 7/14, 19:00 UTC and that during the 14 hours that it took to resolve the issue some of customers using Log Analytics may have experienced latency in the data ingestion and missed or delayed log search alerts.
-Ashok
We've confirmed that all systems are back to normal with no customer impact as of 7/15, 09:00 UTC. Our logs show the incident started on 7/14, 19:00 UTC and that during the 14 hours that it took to resolve the issue some of customers using Log Analytics may have experienced latency in the data ingestion and missed or delayed log search alerts.
- Root Cause: An increase in load caused a backend service to become unhealthy.
- Incident Timeline: 14 Hours - 7/14, 19:00 UTC through 7/15, 09:00 UTC
-Ashok
Update: Friday, 15 July 2022 04:14 UTC
We continue to investigate issues within Log Analytics. Some customers continue to experience latency in data ingestion. Initial findings indicate that the problem began at 07/14 ~07:00 UTC. We are continuing our investigation to determine possible mitigation steps.
We continue to investigate issues within Log Analytics. Some customers continue to experience latency in data ingestion. Initial findings indicate that the problem began at 07/14 ~07:00 UTC. We are continuing our investigation to determine possible mitigation steps.
- Work Around: None
- Next Update: Before 07/15 06:30 UTC
Update: Friday, 15 July 2022 02:01 UTC
We continue to investigate issues within Azure Log Analytics. Some customers continue to experience latency in data ingestion. Initial findings indicate that the problem began at 07/14 ~07:00 UTC. We are continuing our investigation to determine possible mitigation steps.
We continue to investigate issues within Azure Log Analytics. Some customers continue to experience latency in data ingestion. Initial findings indicate that the problem began at 07/14 ~07:00 UTC. We are continuing our investigation to determine possible mitigation steps.
- Work Around: None
- Next Update: Before 07/15 04:30 UTC
Update: Friday, 15 July 2022 00:49 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience latency in the data ingestion. Initial findings indicate that the problem began at 07/14 ~07:00 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience latency in the data ingestion. Initial findings indicate that the problem began at 07/14 ~07:00 UTC. We currently have no estimate for resolution.
- Work Around: None
- Next Update: Before 07/15 02:00 UTC
Published on:
Learn moreRelated posts
Creating AI-Powered Power Apps Using Azure OpenAI (2026 Guide)
Introduction Artificial Intelligence is rapidly transforming the way businesses build applications. Traditional business apps required users t...
6 hours ago
How to Integrate ChatGPT with Dynamics 365 Using Azure Functions (Complete 2026 Guide)
Introduction Artificial Intelligence is transforming enterprise applications, and Microsoft Dynamics 365 is no exception. Businesses are incre...
1 day ago
How to build long-running MCP tools on Azure Functions
Learn how to build long-running MCP tools on Azure Functions using Durable Functions. This post explains why synchronous tool calls break down...
1 day ago
Assess Azure VM readiness with Azure Migrate
2 days ago