Azure Monitors – Status-Based Data Collection

Overview

If the resource is in any other state, the monitor will be marked as DOWN, and data collection will be skipped. This article explains the default states for each monitor type and how to customize the states so that data collection continues for additional states.

Default Behavior

How to Enable Data Collection for Additional States

1. Global Config Key Format: The key follows the pattern: am.<monitortype_in_lowercase>.up.status.list

Note: The monitor type portion of the key must always be in lowercase. Refer to the Applicable Monitor Types table below for the exact key for each monitor.

Step 1 — Identify the Monitor Type and Key

Identify the Azure monitor type for which you want to customize the states for data collection. Then look up the corresponding Global Config key from the table below.

Example: For Azure Data Factory, the key is am.azuredatafactory.up.status.list

Step 2 — Check if the Key Already Exists

Run the following query to check whether the key already exists in the Global Config table:

SELECT * FROM GlobalConfig WHERE key = 'am.azuredatafactory.up.status.list';

Step 3a — If Key Does NOT Exist: Insert a New Entry

If the SELECT query returns no results, insert the key with the desired comma-separated states:

INSERT INTO GlobalConfig (key, value) VALUES ('am.azuredatafactory.up.status.list', 'Succeeded,Updating');

Step 3b — If Key Already Exists: Update the Existing Entry

If the SELECT query returns a result, update the existing entry with the desired comma-separated states:

UPDATE GlobalConfig SET value = 'Succeeded,Updating' WHERE key = 'am.azuredatafactory.up.status.list';

Step 4 — Restart the Build

After updating the Global Config table, restart the Applications Manager build for the changes to take effect.

Important: Always include Succeeded in the value along with any additional states you want to allow. If you set the value to only the new state (e.g., Updating), data collection will not run when the resource returns to Succeeded state.

Example Scenario

Problem: An Azure Data Factory resource is in Updating state. The monitor shows the error:

"Unable to perform data collection as the AzureDataFactory Provisioning State is in Updating state."

Solution: Allow data collection for both Succeeded and Updating states:

1. Check if the key exists:
   

SELECT * FROM GlobalConfig WHERE key = 'am.azuredatafactory.up.status.list';
2. If the key does not exist, insert it:
   

INSERT INTO GlobalConfig (key, value) VALUES ('am.azuredatafactory.up.status.list', 'Succeeded,Updating');
3. If the key already exists, update it:
   

UPDATE GlobalConfig SET value = 'Succeeded,Updating' WHERE key = 'am.azuredatafactory.up.status.list';
4. Restart the Applications Manager build. The monitor will now collect data in both Succeeded and Updating states.

To Revert to Default Behavior

UPDATE GlobalConfig SET value = 'Succeeded' WHERE key = 'am.azuredatafactory.up.status.list';

DELETE FROM GlobalConfig WHERE key = 'am.azuredatafactory.up.status.list';

Note: If the key is removed, the default state defined for that monitor type will be automatically used.

Default States and Global Config Keys per Monitor Type

Note: Data collection for Azure Storage Account, Azure Premium Storage Account, and Azure DNS Zone monitors is not based on resource state. These monitors always collect data regardless of the resource's state, and no Global Config key is applicable for them.

Monitors with a Single State Key

The following monitors use one Global Config key to control allowed states:

Monitor Type	Global Config Key	State Checked	Default State
Azure App Plan	am.azureappplan.up.status.list	Provisioning State	Succeeded
Azure App Service	am.azureappservice.up.status.list	Web App State	Running
Azure Application Gateway	am.azureapplicationgateway.up.status.list	Provisioning State	Succeeded
Azure Backup Vault	am.azurebackupvault.up.status.list	Provisioning State	Succeeded
Azure Bastion	am.azurebastion.up.status.list	Provisioning State	Succeeded
Azure Connection	am.azureconnection.up.status.list	Provisioning State	Succeeded
Azure Container App	am.azurecontainerapp.up.status.list	Provisioning State	Succeeded
Azure Container Instance	am.azurecontainerinstance.up.status.list	Provisioning State	Succeeded
Azure Container Registry	am.azurecontainerregistry.up.status.list	Provisioning State	Succeeded
Azure Cosmos DB	am.azurecosmosdb.up.status.list	Provisioning State	Succeeded
Azure Data Factory	am.azuredatafactory.up.status.list	Provisioning State	Succeeded
Azure DNS Zone	am.azurednszone.up.status.list	Provisioning State	Succeeded
Azure Event Hub Cluster	am.azureeventhubcluster.up.status.list	Provisioning State	Succeeded
Azure Event Hub Namespace	am.azureeventhubnamespace.up.status.list	Provisioning State	Succeeded
Azure Express Route Circuit	am.azureexpressroutecircuit.up.status.list	Circuit Provisioning State	Enabled
Azure Firewall	am.azurefirewall.up.status.list	Provisioning State	Succeeded
Azure Front Door and CDN Profile	am.azurefrontdoorandcdnprofile.up.status.list	Provisioning State	Succeeded
Azure Front Door Classic	am.azurefrontdoorclassic.up.status.list	Provisioning State	Succeeded
Azure Functions	am.azurefunctions.up.status.list	Function App State	Running
Azure Key Vault Managed HSM	am.azurekeyvaultmanagedhsm.up.status.list	Provisioning State	Succeeded
Azure Key Vaults	am.azurekeyvaults.up.status.list	Provisioning State	Succeeded
Azure Load Balancer	am.azureloadbalancer.up.status.list	Provisioning State	Succeeded
Azure Logic App Consumption	am.azurelogicappconsumption.up.status.list	Provisioning State	Succeeded
Azure Logic App Standard	am.azurelogicappstandard.up.status.list	Provisioning State	Succeeded
Azure MariaDB Server	am.azuremariadbserver.up.status.list	State	Ready
Azure MySQL Server	am.azuremysqlserver.up.status.list	State	Ready,Starting,Updating
Azure Network Interface	am.azurenetworkinterface.up.status.list	Provisioning State	Succeeded
Azure Network Watcher Connection	am.azurenetworkwatcherconnection.up.status.list	Provisioning State	Succeeded
Azure PostgreSQL Server	am.azurepostgresqlserver.up.status.list	State	Ready
Azure PostgreSQL Server Single	am.azurepostgresqlserversingle.up.status.list	State	Ready
Azure Private DNS Zone	am.azureprivatednszone.up.status.list	Provisioning State	Succeeded
Azure Private Endpoint	am.azureprivateendpoint.up.status.list	Provisioning State	Succeeded
Azure Private Link Service	am.azureprivatelinkservice.up.status.list	Provisioning State	Succeeded
Azure Public IP Address	am.azurepublicipaddress.up.status.list	Provisioning State	Succeeded
Azure Recovery Service Vault	am.azurerecoveryservicevault.up.status.list	Provisioning State	Succeeded
Azure Redis Cache	am.azurerediscache.up.status.list	Provisioning State	Succeeded
Azure Redis Cache Enterprise	am.azurerediscacheenterprise.up.status.list	Resource State	Running
Azure Relay	am.azurerelay.up.status.list	Provisioning State	Succeeded
Azure Service Bus	am.azurearmservicebus.up.status.list	Namespace Status	Active
Azure SQL Database	am.azuresqldatabase.up.status.list	Database Status	Online
Azure SQL Elastic Pool	am.azuresqlelasticpool.up.status.list	State	Ready
Azure Storage Sync Service	am.azurestoragesyncservice.up.status.list	Provisioning State	Succeeded
Azure Synapse Analytics	am.azuresynapseanalytics.up.status.list	Provisioning State	Succeeded
Azure Traffic Manager Profile	am.azuretrafficmanagerprofile.up.status.list	Profile Status	Enabled
Azure Virtual Machine	am.azurevirtualmachine.up.status.list	Power State	PowerState/running
Azure Virtual Network	am.azurevirtualnetwork.up.status.list	Provisioning State	Succeeded
Azure VM Scale Sets	am.azurevmscalesets.up.status.list	Provisioning State	Succeeded
Azure VNet Gateway	am.azurevnetgateway.up.status.list	Provisioning State	Succeeded

Monitors with Two State Keys

The following monitors check two independent states. Data collection proceeds only when both states match their respective values. Each state has its own Global Config key:

Azure Kubernetes Service

Global Config Key	State Checked	Default State
am.azurekubernetesservice.up.cluster.status.list	Cluster Status	Running
am.azurekubernetesservice.up.provisioning.status.list	Provisioning State	Succeeded

Azure SQL Managed Instance

Global Config Key	State Checked	Default State
am.azuresqlmanagedinstance.up.instance.status.list	Instance State	Ready
am.azuresqlmanagedinstance.up.provisioning.status.list	Provisioning State	Succeeded