Share via

AMA creating group in Linux VM

Abrar Adil S 421 Reputation points
2025-12-12T07:41:39.5766667+00:00

why is this behavior for newly enrolled devices the group is been created irrespective of the whether we onboard a machine to a DCR or azure monitor workspace the group azuremetricsext is been created, but we don't see that group on older machines, for older devices which are onboarded the group is not created.

There is no documentation for this kind of groups been created, requesting you to please help me why the group been created for new devices enrolled to DCR/Monitor but not for old devices where the device is already part of it.

User's image

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Shraddha Pandey 540 Reputation points Microsoft External Staff Moderator
    2025-12-12T07:45:36.9733333+00:00

    Hey Abrar,

    it looks like you’re facing an interesting issue with the Azure Monitor Agent (AMA) and how it handles newly enrolled devices versus older ones in terms of the group azuremetricsext. Here's what I can help you with:

    Understanding the Issue:

    When new devices are onboarded to a Data Collection Rule (DCR) or an Azure Monitor workspace, a group named azuremetricsext is being created. However, this does not seem to happen for older devices that have already been onboarded.

    Possible Explanation:

    The difference in behavior you’re observing could be due to the following reasons:

    1. Version Differences: Newer VMs or devices might be using an updated version of the Azure Monitor Agent which includes features or behavior that were not part of the agent deployed to your older devices.
    2. Data Collection Rules (DCR): The configuration of the DCRs for your old and new devices may differ. Ensure that the new devices are linked to a properly configured DCR that specifies the creation of such groups.
    3. Deployment Settings: It's worth checking how the old devices were set up compared to new ones. Any changes in deployment methodology might explain the discrepancy.

    Suggested Steps:

    1. Compare Configurations: Check the DCRs and configuration settings for both your old and new devices. Look specifically at how the data is being collected and if any group creation rules differ.
    2. Documentation Search: Since you mentioned a lack of documentation, consider raising this as an official support request with Azure Support. They might provide insights that are not readily available in public documentation.
    3. Look for Agent Updates: Ensure that the Azure Monitor Agent is up to date on your older devices. Sometimes, behavior can change with updates that incorporate new functionalities.

    Follow-Up Questions:

    To better assist you, could you clarify the following?

    1. What specific versions of the Azure Monitor Agent are running on the new vs old devices?
    2. Can you confirm if the DCR settings applied to both new and old devices are identical?
    3. Have there been any recent changes in your Azure environment that might have coincided with the new behavior of group creation?

    If you gather this information, it might help pinpoint the specific cause of the behavior you're observing. Hope this helps!

    0 comments

Your answer

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