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
BYOM: Using Azure AI Foundry models in Copilot Studio
Copilot Studio gives you a fast, secure way to build conversational agents and deploy them into the Microsoft 365 environment without writing ...
2 days ago
Building a Modern Python API with Azure Cosmos DB: A 5-Part Video Series
I’m excited to share our new video series where I walk through building a production-ready inventory management API using Python, FastAP...
3 days ago
Azure Developer CLI (azd) – June 2025
This post announces the June release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) – June 2025 appeared first o...
4 days ago
Restricting PAT Creation in Azure DevOps Is Now in Preview
As organizations continue to strengthen their security posture, restricting usage of personal access tokens (PATs) has become a critical area ...
4 days ago
Building Copilot Studio agents with Azure AI Search and Mapped Citations
Integration with custom systems and enterprise use cases often requires more than the out-of-the-box Copilot Studio knowledge sources. Azure A...
5 days ago