Monitor Logic Apps workflow execution including run completions and failures, action execution counts, trigger firing rates, run and action latency, billable executions, and action-level success and failure breakdowns.
The collector uses Azure SDK clients for:
Authentication via Entra ID (service principal, managed identity, or default credentials)
Resource discovery via Azure Resource Graph queries
Metrics collection via Azure Monitor Metrics batch API, grouped by region and time grain
This collector is supported on all platforms.
This collector supports collecting metrics from multiple instances of this integration, including remote instances.
The monitoring principal needs read access to Azure Resource Graph and Azure Monitor metrics for target resources.
Default Behavior
Auto-Detection
When profiles includes auto (the default), the collector queries Azure Resource Graph
to discover which resource types exist in the subscription and enables matching built-in profiles automatically.
Limits
Azure Monitor metrics granularity is typically 1 minute.
The collector enforces a minimum collection interval of 60 seconds.
Performance Impact
The collector uses bounded request concurrency and batches resources and metrics to minimize API calls.
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
Setup
You can configure the azure_monitor collector in two ways:
Create a service principal or use a managed identity with the following permissions:
Monitoring Reader role on the target subscription or resource groups (for Azure Monitor metrics access)
Reader role for Azure Resource Graph queries (for resource discovery)
For service principal authentication:
# Create the service principalaz ad sp create-for-rbac --name "netdata-monitor" --role "Monitoring Reader"\
--scopes /subscriptions/<subscription-id>
# Note the appId (client_id), password (client_secret), and tenant
For managed identity (on Azure VMs, VMSS, or AKS):
# Assign Monitoring Reader role to the VM's managed identityaz role assignment create --assignee <managed-identity-principal-id> \
--role "Monitoring Reader" --scope /subscriptions/<subscription-id>
Configuration
Options
The following options can be defined globally: update_every, autodetection_retry.
User profile files with the same filename override stock profiles.
Group
Option
Description
Default
Required
Collection
update_every
Data collection interval (seconds). Must be at least 60.
60
no
autodetection_retry
Autodetection retry interval (seconds). Set 0 to disable.
0
no
Target
subscription_id
Azure subscription ID.
yes
cloud
Azure cloud environment: public, government, or china.
public
no
Collection
discovery_every
Resource discovery interval in seconds.
300
no
query_offset
Offset in seconds for metric query windows. Increase if metrics appear incomplete.
180
no
timeout
Timeout for Azure Resource Graph and Azure Monitor API requests, in seconds.
30
no
Limits
max_concurrency
Maximum concurrent batch queries to Azure Monitor.
4
no
max_batch_resources
Maximum resources per Azure Monitor batch request.
50
no
max_metrics_per_query
Maximum metrics per Azure Monitor batch request.
20
no
Profiles
profiles
Profile ids to enable. Use auto to discover resource types via Azure Resource Graph and enable matching profiles. Combine with explicit ids: [auto, custom_profile].
[auto]
no
Filters
resource_groups
Optional list of resource group names to restrict monitoring scope.
[]
no
Authentication
auth.mode
Authentication mode: service_principal, managed_identity, or default.
yes
auth.mode_service_principal.tenant_id
Entra ID tenant ID (required for service_principal mode).
no
auth.mode_service_principal.client_id
Entra ID application (client) ID (required for service_principal mode).
no
auth.mode_service_principal.client_secret
Entra ID client secret (required for service_principal mode).
no
auth.mode_managed_identity.client_id
Client ID for user-assigned managed identity. Leave empty for system-assigned.
no
Virtual Node
vnode
Associates this data collection job with a Virtual Node.
no
via UI
Configure the azure_monitor collector from the Netdata web interface:
Go to Nodes.
Select the node where you want the azure_monitor data-collection job to run and click the :gear: (Configure this node). That node will run the data collection.
The Collectors → Jobs view opens by default.
In the Search box, type azure_monitor (or scroll the list) to locate the azure_monitor collector.
Click the + next to the azure_monitor collector to add a new job.
Fill in the job fields, then click Test to verify the configuration and Submit to save.
Test runs the job with the provided settings and shows whether data can be collected.
If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
via File
The configuration file name for this integration is go.d/azure_monitor.conf.
The file format is YAML. Generally, the structure is:
Logic Apps prompt token overflow on ${label:resource_name}
Troubleshooting
Debug Mode
Important: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature.
To troubleshoot issues with the azure_monitor collector, run the go.d.plugin with the debug option enabled. The output
should give you clues as to why the collector isn’t working.
Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that’s not the case on
your system, open netdata.conf and look for the plugins setting under [directories].
cd /usr/libexec/netdata/plugins.d/
Switch to the netdata user.
sudo -u netdata -s
Run the go.d.plugin to debug the collector:
./go.d.plugin -d -m azure_monitor
To debug a specific job:
./go.d.plugin -d -m azure_monitor -j jobName
Getting Logs
If you’re encountering problems with the azure_monitor collector, follow these steps to retrieve logs and identify potential issues:
Run the command specific to your system (systemd, non-systemd, or Docker container).
Examine the output for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.
System with systemd
Use the following command to view logs generated since the last Netdata service restart:
journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep azure_monitor
System without systemd
Locate the collector log file, typically at /var/log/netdata/collector.log, and use grep to filter for collector’s name:
grep azure_monitor /var/log/netdata/collector.log
Note: This method shows logs from all restarts. Focus on the latest entries for troubleshooting current issues.
Docker Container
If your Netdata runs in a Docker container named “netdata” (replace if different), use this command:
docker logs netdata 2>&1 | grep azure_monitor
No metrics are collected
Verify the following:
The service principal or managed identity has Monitoring Reader role on the subscription or resource group.
The subscription_id in the configuration matches the subscription containing the target resources.
Target resources are running and producing metrics (check Azure Portal > Metrics for the resource).
Check the Netdata error log for authentication or API errors: grep azure_monitor /var/log/netdata/error.log.
Missing metrics for some resource types
Azure Monitor profiles are matched by resource type. If a resource type exists but no metrics appear:
Ensure profiles: [auto] (default) is set, or the specific profile id is listed.
Verify the resource type matches a built-in profile. Run ls /usr/lib/netdata/conf.d/go.d/azure_monitor.profiles/default/ to see available profiles.
Some metrics require the resource to be actively processing data (e.g., IoT Hub telemetry metrics only appear when devices send messages).
Metrics appear delayed
Azure Monitor metrics have a built-in reporting delay of 1-3 minutes. The collector uses a query_offset (default: 180 seconds) to account for this.
If metrics are missing or incomplete, try increasing query_offset to 240 or 300 seconds.
Some metrics with longer time grains (e.g., PT5M) may take up to 5 minutes to appear.
Authentication errors in sovereign clouds
For Azure Government or Azure China clouds, set the cloud parameter:
Azure Government: cloud: government
Azure China (21Vianet): cloud: china
Ensure the service principal is registered in the correct cloud tenant.
The observability platform companies need to succeed
