Azure Monitor Status Archive articles

Azure Monitor Status Blog discontinuation notice

Azure-Monitor-Team — Thu, 04 Aug 2022 18:22:42 GMT

As part of our efforts to improve the Azure Monitor service experience and consolidate it with other Azure-wide services, from now on, we’ll post all Azure Monitor service updates in the Azure portal under Service Health instead of in this blog.

To get notifications on service issues, set up Service Health alerts in the Azure portal.

Name update for Agent and associated resources in Azure Monitor - Container Insights

iacairns — Thu, 27 Oct 2022 18:24:06 GMT

What is changing?

When customers enable Container Insights, Azure Monitor deploys a containerized collection agent. This agent is being renamed from OMSAgent to Azure Monitor Agent. There are no feature updates or functional changes to the agent in this release.

Why are the changes being made?

The current OMSAgent name is a legacy name from the OMS product and does not reflect the branding for Azure Monitor and Container Insights products. The Azure Monitor Agent is being standardized as the single collection agent for Azure Monitor. The name change brings the agent’s name in line with these updates.

When are the changes going live?

The changes will roll out region by region starting from early September. Exact dates and a version number of Container Insights image version with changes will be shared closer to the release date with an update to this blog post.
UPDATE: The changes were delayed and released on 26th October 2022 starting with the West Central US (WCUS) region. They should be all regions by the end of November.

Agent versions with the change

Linux: mcr.microsoft.com/azuremonitor/containerinsights/ciprod:ciprod10042022-3c05dd1b
Windows: mcr.microsoft.com/azuremonitor/containerinsights/ciprod:win-ciprod10042022-3c05dd1b

AKS customers will receive the changes as part of an AKS service update. Arc and Hybrid customers will have to update their extension and HELM chart versions manually. See detailed instructions below.

What are the exact changes?

The agent used by Container Insights has been renamed. So, customers will see a new pod name in their clusters. Alongside that, several other related resources have also been renamed. See the “List of renamed resources” and “List of renamed labels " tables below for complete details.

What is the impact? What do I need to do?

Log analytics queries

All log queries with string the omsagent in them will not work and results will only be returned for dates before the change. To mitigate, update the queries to have query clause to cover “omsagent” or “ama-logs” in existing queries. See examples below.

Original query

Updated query

KubePodInventory

| where Namespace == "kube-system"

| where Name contains "omsagent"

KubePodInventory

| where Namespace == "kube-system"

| where Name contains "omsagent" or Name contains “ama-logs”

Original query

Updated query

ContainerLog

| where Name contains "omsagent"

ContainerLog
| where Name contains "omsagent" or Name contains "ama-logs"

Alert Rules

Alert Rules with the string the omsagent will not work.

Query alerts with the string “omsagent”

Metric alerts which reference omsagent in a dimension

You can find alert rules using

Option 1 – In the Alerts section of Azure Monitor in the Azure portal

Option 2 - Programmatically using Azure Resource Graph queries

Go to the “Azure Resource Graph Explorer” in the portal and run the below query:

alertsmanagementresources

| where properties contains "omsagent"

The above steps should help you find the affected rules. To update the rules, simply edit them in the portal (as below).

User scripts

Any user scripts explicitly referencing the pod names will not work.

Resource name in all UIs

Customers will see the updated controller names in the Container Insights UI as well as the command line.

Screenshot 1 – Container Insights Portal UI

Screenshot 2 – Command Line

Screenshot 3 – Workbooks

Instructions for consuming the update

Instructions for AKS customers

No action needed from customers. Customers will receive this as part of an AKS service update.

Instructions for Arc K8s customers

Note: The extension version with the above changes is version 3.0.0

Get the Azure Log Analytics Workspace Resource Id which configured on the existing Azure Monitor for containers extension

az k8s-extension show --name azuremonitor-containers --cluster-name <cluster-name> --resource-group <resource-group> --cluster-type connectedClusters -n azuremonitor-containers

Delete the existing Azure Monitor for Containers extension either through Azure Portal or Azure CLI

Create Azure Monitor for containers extension either through Azure Portal or Azure CLI. Make sure to use the same Azure Log Analytics Workspace ResourceId which is obtained in Step #1, to ensure the data being ingested to the same Log analytics workspace as before

Instructions for Hybrid customers

Hybrid customers refers to customers running AKS Engine, Azure OpenShift, and other self-managed K8S distributions on Azure VMs.

Note: The Helm chart version with the above changes is version 3.0.0

Get the Azure Log Analytics workspace which is being used for the Azure Monitor for containers HELM chart. You can obtain through

helm get values <azure-monitor-for-containers-release-name> -A

Delete the Azure Monitor for containers HELM chart - https://docs.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-optout-hybrid#how-to-stop-monitoring-using-helm

Install the HELM chart as per the Instructions - https://docs.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-hybrid-setup#install-the-helm-chart . Make sure to same Azure Log Analytics Workspace to ensure the data being ingested to the same Log Analytics workspace as before.

List of renamed resources

Note: The xxxx below is a placeholder for random hash values appended to the resource name. In practice, a name like “ama-logs-xxxxx” will appear as “ama-logs-cfkst” or similar.

Resource Type	Old name	New name
Configmap	configmap/omsagent-rs-config	configmap/ama-logs-rs-config
Pod	pod/omsagent-xxxxx	pod/ama-logs-xxxxx
Pod	pod/omsagent-rs-xxxxxxxxxx- xxxxx	pod/ama-logs-rs- xxxxxxxxxx-xxxxx
Pod	pod/omsagent-win-xxxxx	pod/ama-logs-windows- xxxxx
Secret	secret/omsagent-secret	secret/ama-logs-secret
Secret	secret/omsagent-token-xxxxx	secret/ama-logs-token-xxxxx
ServiceAccount	serviceaccount/omsagent	serviceaccount/ama-logs
ControllerRevision	controllerrevision.apps/omsagent-xxxxxxxxxx	controllerrevision.apps/ama-logs-xxxxxxxxxx
ControllerRevision	controllerrevision.apps/omsagent-win-xxxxxxxxxx	controllerrevision.apps/ama-logs-windows-xxxxxxxxxx
Daemonset	daemonset.apps/omsagent	daemonset.apps/ama-logs
Daemonset	daemonset.apps/omsagent-win	daemonset.apps/ama-logs-windows
Deployment	deployment.apps/omsagent-rs	deployment.apps/ama-logs-rs
Replicaset	replicaset.apps/omsagent-rs-xxxxxxxxxx	replicaset.apps/ama-logs-rs-xxxxxxxxxx

List of renamed labels

component=oms-agent	component=ama-logs-agent
component=oms-agent-win	component=ama-logs-agent-windows

Experiencing Data Latency for Azure Log Analytics - 07/15 - Resolved

Azure-Monitor-Team — Fri, 15 Jul 2022 09:28:38 GMT

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.

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

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-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.

Work Around: None
Next Update: Before 07/15 06:30 UTC

-Rahul

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.

Work Around: None
Next Update: Before 07/15 04:30 UTC

-Rahul

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.

Work Around: None
Next Update: Before 07/15 02:00 UTC

-Rahul

Experiencing Data Access Issue in Azure portal for Log Analytics - 07/13 - Resolved

Azure-Monitor-Team — Wed, 13 Jul 2022 13:36:00 GMT

Final Update: Wednesday, 13 July 2022 13:00 UTC

We've confirmed that all systems are back to normal with no customer impact as of 7/13, 12:30 UTC. Our logs show the incident started on 7/13, 11:05 UTC and that during the 1 hour 25 minutes that it took to resolve the issue, some of customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in Australia Southeast region.

Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
Incident Timeline: 1 Hours & 25 minutes - 7/13, 11:05 UTC through 7/13, 12:30 UTC

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Ashok

Initial Update: Wednesday, 13 July 2022 12:07 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may experience data access issue and delayed or missed alerts in Australia South East.

Work Around: None
Next Update: Before 07/13 14:30 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Ashok

Experiencing Data Access Issue in Azure portal for Log Analytics - 07/13 - Resolved

Azure-Monitor-Team — Wed, 13 Jul 2022 09:29:33 GMT

Final Update: Wednesday, 13 July 2022 07:07 UTC

We've confirmed that all systems are back to normal with no customer impact as of 7/13, 05:20 UTC. Our logs show the incident started on 7/13, 04:40 UTC and that during the 40 minutes that it took to resolve the issue some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in North Central US region.

Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
Incident Timeline: 40 minutes - 7/13, 04:40 UTC through 7/13, 05:20 UTC

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Ashok

Initial Update: Wednesday, 13 July 2022 05:29 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts.

Work Around: None
Next Update: Before 07/13 07:30 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol

Experiencing Data Access Issue in Azure portal for Log Analytics - 07/13 - Resolved

Azure-Monitor-Team — Wed, 13 Jul 2022 09:28:33 GMT

Final Update: Wednesday, 13 July 2022 04:14 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/13 02:35 UTC. Our logs show the incident started on 07/13 01:30 UTC and that during the 1 hours & 5 minutes that it took to resolve the issue some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in North Central US region.

Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
Incident Timeline: 1 hour 5 minutes - 7/13, 01:30 UTC through 7/13, 02:35 UTC

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Samuel Durodolu

Experincing intermittent data latency and incorrect alert activation

Azure-Monitor-Team — Sat, 09 Jul 2022 20:31:52 GMT

Final Update: Saturday, 09 July 2022 15:55 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09 July 2022, 15:55 UTC. Our logs show the incident started on 09 July 2022, 15:55 UTC and that during incident, we identified some customers using Log Analytics in Central US may be experiencing intermittent data latency and incorrect alert activation when ingesting telemetry in their Log Analytics Workspace.

Root Cause: We determined that some unhealth services caused the issue and have immediately started working on them to fix the issue.

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Samuel Durodolu

Experiencing Data Latency in Azure Portal for Many Data Types - 07/09 - Resolved

Azure-Monitor-Team — Sat, 09 Jul 2022 09:46:18 GMT

Final Update: Saturday, 09 July 2022 09:45 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/09, 08:50 UTC. Our logs show the incident started on 07/09, 08:15 UTC and that during the 35 minutes that it took to resolve the issue. Some of the customer using Azure monitor for Metric APIs or alerts who may have experienced data latencies when attempting to query for metrics for Microsoft.Web also might have experienced false or delayed alerts.

Root Cause: The failure was due to dependent backend service which Azure Monitor relies upon became unhealthy.
Incident Timeline: 35 minutes - 07/08, 08:15 UTC through 07/09, 08:50 UTC

We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Sai Kumar

Experiencing latency issue in Azure Portal for Many Data Types - 07/09 - Resolved

Azure-Monitor-Team — Sat, 09 Jul 2022 01:49:29 GMT

Final Update: Saturday, 09 July 2022 01:41 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09 July 2022, 01:13 UTC. Our logs show the incident started on 09 July 2022, 00:15 UTC and that during the 1 hour that it took to resolve the issue of customers experienced unavailability of metrics and some alerts were not fired as expected.

Root Cause: We determined that a dependent backend service which Azure Monitor relies upon became unhealthy.

Incident Timeline: 1 Hour - 09 July 2022, 00:15 UTC through 09 July 2022, 01:13 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Faraz Khan

Experiencing Data Access issue in Azure Portal for Many Data Types - 07/08 - Resolved

Azure-Monitor-Team — Sat, 09 Jul 2022 00:38:13 GMT

Final Update: Saturday, 09 July 2022 00:35 UTC

We have confirmed all services are back to normal, our logs show that the incident occurred between 18:45 UTC and 22:40 UTC on 8 July 2022. In the three hours that it took to resolve the issue, some of the customers using Azure Monitor who may have experienced issues in East US 2 and West Europe region.

Root Cause: The Issue was due to high ingestion from Alerts and metrics services.

Incident Timeline: Between 18:45 UTC and 22:40 UTC on 8 July 2022,

We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Samuel Durodolu

We are aware of issues within Alerts and Metrics Services and are actively investigating. Some of the customers in East US 2 and West Europe geographical region may experience Issues with the services.

Work Around: On-going

Next Update: Before 07/08 12:39 UTC

We are working hard to resolve this issue and apologize for any inconvenience.

Experiencing Data Latency issue in Azure Portal for Many Data Types - 07/07 - Investigating

Azure-Monitor-Team — Fri, 08 Jul 2022 01:49:41 GMT

Update: Thursday, 07 July 2022 19:32 UTC

We've confirmed that all systems are back to normal with no customer impact as of 17:00 UTC on 07 Jul 2022. Our logs show the incident started on 12:00 UTC on 06 Jul 2022. you were identified as a customer using Application Insights in West Central US who may have experienced ingestion latency and delayed alerts.

Root Cause: The failure was due to the dependent backend service unhealthy.
Incident Timeline: 06 Jul 2022 12:00 UTC through 07 Jul 2022 17:00 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Faraz Khan

Experiencing Alerting failure for Metric Alerts - 07/07 - Resolved

Azure-Monitor-Team — Thu, 07 Jul 2022 07:21:04 GMT

Final Update: Thursday, 07 July 2022 07:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 7/7, 06:05 UTC. Our logs show the incident started on 7/7, 05:20 UTC and that during the 45 minutes that it took to resolve the issue. Some of the customers may have experienced issues with Azure monitor metrics and alerts.

Root Cause: The failure was due to the dependent backend service unhealthy.
Incident Timeline: 45 minutes - 7/7, 05:20 UTC through 7/7, 06:05 UTC

We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Surya

Experiencing Data Latency issue in Azure Portal for Many Data Types - 07/07 - Resolved

Azure-Monitor-Team — Thu, 07 Jul 2022 05:18:04 GMT

Final Update: Thursday, 07 July 2022 05:03 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/07, 03:00 UTC. Our logs show the incident started on 07/07, 00:00 UTC and that during the 3 hours that it took to resolve the issue some of the customers ingesting telemetry in China East 2 geographical region may have experienced intermittent data latency, data gaps and incorrect alert activation.

Root Cause: The failure was due to a backend dependent service becoming unhealthy.
Incident Timeline: 3 Hours - 07/07, 00:00 UTC through 07/07, 03:00 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Sai Kumar

Initial Update: Thursday, 07 July 2022 04:34 UTC

We are aware of issues within Application Insights and are actively investigating. Some of the customers ingesting telemetry in China East 2 geographical region may experience intermittent data latency, data gaps and incorrect alert activation.

Work Around: None
Next Update: Before 07/07 08:00 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Sai Kumar

Experiencing Alerting failure for Log Search Alerts - 07/06 - Resolved

Azure-Monitor-Team — Wed, 06 Jul 2022 13:19:16 GMT

Final Update: Wednesday, 06 July 2022 12:54 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/06, 11:25 UTC. Our logs show the incident started on 07/06, 05:45 UTC and that during the 5 hours & 40 minutes that it took to resolve the issue, some of the customers using Azure Monitor who may have experienced issues with missed alerts or missed alerts notifications in Korea Central region.

Root Cause: The failure was due to a backend dependency service becoming unhealthy.
Incident Timeline: 5 Hours & 40 minutes - 07/06, 05:45 UTC through 07/06, 11:25 UTC

We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Sai Kumar

Initial Update: Wednesday, 06 July 2022 10:25 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customer using Azure Monitor who may experience issues with missed alerts or missed alerts notifications.

Work Around: NA
Next Update: Before 07/06 14:30 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Sai Kumar

Experiencing Data Access issue in Azure Portal for Many Data Types - 06/30 - Resolved

Azure-Monitor-Team — Thu, 30 Jun 2022 21:49:23 GMT

Final Update: Thursday, 30 June 2022 21:44 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/30, 20:40 UTC. Our logs show that the incident started on 06/30, 10:30 UTC and that during the 10 hours and 10 minutes that it took to resolve the issue some of the customers experienced intermittent data latency, missed or delayed log search alerts and incorrect alert activation.

Root Cause: The failure was due to a backend dependency.
Incident Timeline: 10 Hours & 10 minutes - 06/30, 10:30 UTC through 06/30, 20:40 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Saika

Update: Thursday, 30 June 2022 19:57 UTC

The backend dependency is in the process of applying Hotfix. Some customers using Application Insights components in West US2 region continue to experience intermittent data latency, missed or delayed log search alerts and incorrect alert activation.

Work Around: None
Next Update: Before 06/30 23:00 UTC

-Saika

Update: Thursday, 30 June 2022 17:09 UTC

Root cause has been isolated to a backend dependency. Some customers using Application Insights components in West US2 region continue to experience intermittent data latency, missed or delayed log search alerts and incorrect alert activation.

Work Around: None
Next Update: Before 06/30 20:30 UTC

-Saika

Initial Update: Thursday, 30 June 2022 14:14 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers using Application Insights components in West US2 may experience intermittent data latency, missed or delayed log search alerts and incorrect alert activation.

Work Around: None
Next Update: Before 06/30 17:30 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol

Experiencing Data Access Issue in Azure portal for Log Analytics - 06/30 - Resolved

Azure-Monitor-Team — Thu, 30 Jun 2022 15:30:36 GMT

Final Update: Thursday, 30 June 2022 15:23 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/30, 12:20 UTC. Our logs show the incident started on 06/30, 11:25 UTC and that during the 55 minutes that it took to resolve the issue some of the customers using Log analytics and Azure Sentinel in East US region may have experienced data access issue and delayed or missed alerts.

Root Cause: The failure was due to one of the backend dependent service becoming unhealthy.
Incident Timeline: 55 minutes - 06/30, 11:25 UTC through 06/30, 12:20 UTC

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Soumyajeet

Initial Update: Thursday, 30 June 2022 12:58 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in East US region.

Next Update: Before 06/30 16:00 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Soumyajeet

Experiencing Alerting Failure issue in Azure Portal for Many Data Types - 06/28 - Resolved

Azure-Monitor-Team — Tue, 28 Jun 2022 14:30:06 GMT

Final Update: Tuesday, 28 June 2022 14:18 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/28, 12:53 UTC. Our logs show the incident started on 06/27, 15:43 UTC and that during the 21 hours and 10 minutes that it took to resolve the some of the customers using the IT Service Management (ITSM) connector with Azure Monitor in West Europe may have experienced errors or failure notifications. New alerts may not export to ServiceNow and connections to ServiceNow may fail after creation.

Root Cause: The failure was due to a backend dependency service becoming unhealthy.
Incident Timeline: 21 Hours & 10 minutes - 06/27, 15:43 UTC through 06/28, 12:53 UTC

We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Soumyajeet

Experiencing Data Latency issue in Application Insights - US-WEST-2- 06/28 - Investigating

Azure-Monitor-Team — Tue, 28 Jun 2022 03:58:50 GMT

Final Update: Tuesday, 28 June 2022 03:53 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/28, 03:33 UTC. Our logs show the incident started on 06/27, 21:20 UTC and during the 6 hours and 13 minutes that it took to resolve the issue. Some customers using Application Insights components in West US2 who may have experienced intermittent data latency and incorrect alert activation.

Root Cause: We determined that some instances of a backend service Application Insights relies on became unhealthy. This resulted in the latency and missed alerts customers may have experienced.
Mitigation: We restarted the backend services to a healthy state that mitigating the issue.
Incident Timeline: 6 Hours & 13 minutes - 06/27, 21:20 UTC through 06/28, 03:33 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Vignesh

Initial Update: Tuesday, 28 June 2022 03:01 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Data Latency.

Work Around: None
Impact start time: 6/27/2022 21:30 UTC
Next Update: Before 06/28 04:30 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-muhkhan

Experiencing Data Access Issue in Azure Log Analytics - 06/27 - Resolved

Azure-Monitor-Team — Mon, 27 Jun 2022 22:26:19 GMT

Final Update: Monday, 27 June 2022 22:17 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/27, 21:40 UTC. Our logs show the incident started on 06/27 17:55 UTC and that during the 3 hours & 45 minutes that it took to resolve the issue some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts.

Root Cause: The failure was due to degraded downstream dependency.
Impacted Region: UsGovVirginia
Incident Timeline: 3 Hours & 45 minutes - 06/27 17:55 UTC through 06/27, 21:40 UTC

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vignesh

Update: Monday, 27 June 2022 20:49 UTC

We continue to investigate issues within Log Analytics & Azure Sentinel. Root cause is not fully understood at this time. Some customers continue to experience data access issues and delayed or missed alerts. Initial findings indicate that the problem began at 06/27 17:55 UTC. We currently have no estimate for resolution.

Work Around: None
Next Update: Before 06/27 22:00 UTC

-Vignesh

Experiencing Data Access Issue in Azure portal for Log Analytics - 06/27 - Resolved

Azure-Monitor-Team — Mon, 27 Jun 2022 12:21:51 GMT

Final Update: Monday, 27 June 2022 12:14 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/27, 10:06 UTC. Our logs show the incident started on 06/27, 09:48 UTC and that during the 18 minutes that it took to resolve the issue some of the customers in Central US region may have experienced issues accessing their data as well as missed or delayed alerts.

Root Cause: The failure was due to backend dependency service becoming unhealthy.
Incident Timeline: 18 minutes - 06/27, 09:48 UTC through 06/27, 10:06 UTC

We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Soumyajeet