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
Replacing jackson-databind with azure-json and azure-xml
This blog post explains how azure-json and azure-xml replaced jackson-databind in the Azure SDK for Java. The post Replacing jackson-databind ...
8 hours ago
March Patches for Azure DevOps Server
Today we are releasing patches that impact our self-hosted product, Azure DevOps Server. We strongly encourage and recommend that all customer...
9 hours ago
Implementing Chat History for AI Applications Using Azure Cosmos DB Go SDK
This blog post covers how to build a chat history implementation using Azure Cosmos DB for NoSQL Go SDK and langchaingo. If you are new to the...
13 hours ago
Introducing Azure AI Foundry - Everything you need for AI development
Create agentic solutions quickly and efficiently with Azure AI Foundry. Choose the right models, ground your agents with knowledge, and seamle...
1 day ago
Azure Developer CLI (azd) – March 2025
This post announces the March release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) – March 2025 appeared first...
4 days ago