Share via

Azure arc collecting logs only for 8 of my 31 machines

Todor Dimitrov 20 Reputation points
2025-06-27T06:29:37.3533333+00:00

Hello,

I have setup Azure arc to notify me when the space on any of the disks that are present on my servers reach 10% or less but i am only getting logs from a third of all the machines that i've configured an Azure Monitor agent on. In the heartbeat table i can see all of them but in the performance table i see logs that i haven't even set up performance counters for. Any help would be greatly appreciated.

Regards

Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rahul Jorrigala 3,745 Reputation points Microsoft External Staff Moderator
    2025-07-09T10:56:29.2833333+00:00

    Hello Todor,

    1. Verify Data Collection Rules (DCRs)

    Go to Azure Monitor > Data Collection Rules.

    Check:

    Are all target machines associated with the correct DCR?

    Is the DCR scoped to all expected machines?

    Are the performance counters for disk space correctly defined?

    You can use Azure CLI or PowerShell to list DCR associations:

    
az monitor data-collection rule association list --resource <Arc-enabled server resource ID>
    1. Check AMA Extension Status

    Even if Heartbeat is visible, AMA might not be fully functional.

    Run this on the Arc-enabled server:

    azcmagent show

    Look for:

    Connected: true

    Extensions: AzureMonitorWindowsAgent (or Linux equivalent)

    Status: Ready

    1. Validate Log Analytics Workspace Connections

    Ensure all machines are connected to the same workspace.

    Check if workspace ingestion is working:

    Go to Log Analytics > Tables > Perf.

    Run a query like:

    
Perf
| where ObjectName == "LogicalDisk"
| summarize count() by Computer

    
Perf
| where ObjectName == "Logical Disk"
| summarize count() by Computer
    1. Unexpected Performance Counters

    This can happen if:

    A default DCR is applied.

    Counters are inherited from another rule.

    You used a template that includes extra counters.

    az monitor data-collection rule show --name <DCR name> --resource-group <RG>

    Please let me know if you face any challenge here, I can help you to resolve this issue further

    If the comment was helpful, please click "Upvote"

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.