Linux VM memory metrics missing from azure.vm.linux.guestmetrics namespace

Question

Linux VM memory metrics missing from azure.vm.linux.guestmetrics namespace

Appmanager Zohocorp 61

We are monitoring Azure Linux Virtual Machines using Azure Monitor Agent (AMA) deployed with a Data Collection Rule (DCR) configured specifically for Linux.

In the DCR deployment, memory metrics are available and selected, and the DCR has been deployed successfully.

User's image

After deployment, in Azure VM > Extensions + applications, the AzureMonitorLinuxAgent shows the status Provisioning succeeded.

User's image Next, in Azure VM > Monitor > Metrics, the namespace azure.vm.linux.guestmetrics is listed which contains other metrics, but the expected memory metrics selected in the DCR are not listed under that namespace.

User's image

What we have verified

The Data Collection Rule was created specifically for Linux.
Memory-related counters are selected in DCR deployment.
AMA status on the VM is Provisioning succeeded.
The namespace azure.vm.linux.guestmetrics is listed in Azure Monitor.
The selected memory metrics are not appearing under that namespace

Please let us know why the memory metrics selected in the DCR deployment are not listed in Azure Monitor Metrics.

Thanks.

Himanshu Shekhar 6,790 Reputation points Microsoft External Staff Moderator

2026-06-23T07:19:00.78+00:00
Hey! Based on what you’re seeing, the key point is: guest OS memory metrics (like those coming from Linux DCR performance counters) don’t always show up in the Metrics blade immediately under the exact namespace you expect. Guest metrics are collected by the in-VM monitoring pipeline (AMA/DCR), but visibility in Azure Monitor Metrics Explorer depends on the collection path and the portal being able to query/return those metric definitions and data.

Here are the most common reasons (and what to try) when azure.vm.linux.guestmetrics exists but the selected memory metrics aren’t listed.

Guest OS metrics visibility requires the correct guest-metrics pipeline

Per the troubleshooting guidance, Guest OS metrics are not collected automatically and must be collected by Azure Monitor Agent (AMA) using the required configuration (DCR / diagnostics-style collection path). If the agent/DCR is not actually emitting into the metrics store the portal reads, you’ll see the namespace but not the metric list/data.

You already confirmed:

AMA extension shows “Provisioning succeeded”

DCR is Linux-specific

Memory counters are selected

So the remaining checks are usually around the portal’s ability to read the metric definitions and the metric-emission actually succeeding end-to-end.

Check portal “Metrics Explorer” configuration: namespace vs metric picker mismatch

In Metrics Explorer, you should ensure you’re selecting:

the correct resource scope (the VM)

the correct Metric Namespace (docs mention azure.vm.linux.guest / azure.vm.windows.guest, while your screenshot shows azure.vm.linux.guestmetrics)

The documentation notes that if guest namespaces/metrics aren’t visible, it indicates a configuration/collection issue. It also calls out verifying namespace + metric presence in Monitor > Metrics.

What to try

In Monitor > Metrics, open the metric picker and explicitly set the namespace to the Linux guest namespace that shows in your portal and then look for the memory counters (example memory metric names referenced in guidance include counters like Memory(*)\Available MBytes and related memory counters).

Try switching to a broader time range (e.g., last 30 days) and refresh.

Storage/account access or diagnostics-path issues (most relevant for “Guest (classic)” metrics)

Two of the provided articles explain that, historically/for the classic guest metrics path:

Guest OS metrics may be stored in a storage account configured via diagnostics settings

If that storage account is protected by a firewall, the Azure portal can’t access the data/definitions, and you’ll see missing/limited results.

Even though you’re using AMA + DCR, this still comes up as a “portal can’t access the data source” failure mode for guest metrics visibility.

What to try

Confirm the underlying destination/collection path that feeds the Metrics UI is not blocked from Azure portal access (firewall restrictions on the associated storage are explicitly called out as a common cause).

DCR counters may be selected, but the metric names don’t match what the portal expects

There are cases where the counter names configured in the DCR don’t map cleanly to what shows up in Metric Explorer until the emission pipeline is correct. One of the provided internal references specifically discusses mapping Linux performance counter names to the metric names shown in the portal.

What to try

Confirm the exact performance counter names you selected (examples from the Linux memory counters list in the provided reference include Memory(*)\Available MBytes, Memory(*)\% Available Memory, Memory(*)\% Used Memory, etc.).

After updating a DCR, restart AMA / let data emission settle, then refresh Metrics Explorer.

(There’s a relevant example in the provided results where Linux guest metrics became visible after updating the DCR with correct memory counters and then restarting the AMA agent.)

References

Resolve issues viewing Memory (or other Guest OS) metrics in Azure Monitor: https://learn.microsoft.com/azure/azure-monitor/metrics/metrics-troubleshoot#resolve-issues-viewing-memory-or-other-guest-os-metrics-in-azure-monitor

“I can’t pick Guest OS namespace and metrics” (guest vs host metrics visibility; diagnostics/portal access): https://supportabilityhub.microsoft.com/solutions/apollosolutions/f00779a9-2e7e-941c-4bf6-7b8aec670cc1/39f32606-6cda-44e5-8dc7-c1cd1634a703

“My chart with Guest OS metric is blank” (common causes incl. diagnostics extension / provider / storage firewall / time range): https://supportabilityhub.microsoft.com/solutions/apollosolutions/f00779a9-2e7e-941c-4bf6-7b8aec670cc1/f915aa88-f4e0-48be-8eac-f0addcea43f5

Differences between Guest and Host metrics (setup + guest requires AMA/DCR): https://supportabilityhub.microsoft.com/solutions/apollosolutions/f00779a9-2e7e-941c-4bf6-7b8aec670cc1/034ab5df-c364-47f1-af7b-0fc941c1030f

AMA Linux: HT: How to match Linux metric names to counter names in DCR perf data stream: https://supportability.visualstudio.com/AzureMonitor/_wiki/wikis/AzureMonitor.wiki/1553058/Monitor%20Agents/Agents/Azure%20Monitor%20Agent%20(AMA)%20for%20Linux/How-To/AMA%20Linux:%20HT:%20How%20to%20match%20Linux%20metric%20names%20to%20counter%20names%20in%20the%20DCR%20Perf%20data%20stream

OpenTelemetry Guest OS Metrics reference (preview) / Linux performance counters list: https://learn.microsoft.com/azure/azure-monitor/vm/metrics-guest-reference?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#performance-counters
Himanshu Shekhar 6,790 Reputation points Microsoft External Staff Moderator

2026-06-25T05:31:36.7466667+00:00

Just checking if provided response was helpful! please let me know if you have any queries.
Appmanager Zohocorp 61 Reputation points

2026-06-29T07:10:34.61+00:00
@Himanshu Shekhar ,

Thank you for the guidance. To clarify the current status:

✅ DCR is configured with Azure Monitor Metrics as the destination

✅ Namespace azure.vm.linux.guestmetrics is visible in Metrics Explorer

✅ Other metrics (CPU, Disk, Network) selected in the DCR are listed under the namespace

❌ Only Memory metrics (% Used Memory, Available MBytes, Used Memory MBytes) are not listed in Metrics Explorer

This confirms the DCR configuration and AMA are working correctly for other metrics. The issue appears to be specific to Memory counters not being routed to the Azure Monitor Metrics on Linux, even though the same DCR destination is used for all other metrics.

Is this a known platform limitation for Linux memory counters in azure.vm.linux.guestmetrics?

Thanks

1 answer

Your answer

Himanshu Shekhar 6,790 Reputation points Microsoft External Staff Moderator

2026-06-25T05:31:36.7466667+00:00

Just checking if provided response was helpful! please let me know if you have any queries.
Appmanager Zohocorp 61 Reputation points

2026-06-29T07:10:34.61+00:00

@Himanshu Shekhar ,

Thank you for the guidance. To clarify the current status:

✅ DCR is configured with Azure Monitor Metrics as the destination

✅ Namespace azure.vm.linux.guestmetrics is visible in Metrics Explorer

✅ Other metrics (CPU, Disk, Network) selected in the DCR are listed under the namespace

❌ Only Memory metrics (% Used Memory, Available MBytes, Used Memory MBytes) are not listed in Metrics Explorer

This confirms the DCR configuration and AMA are working correctly for other metrics. The issue appears to be specific to Memory counters not being routed to the Azure Monitor Metrics on Linux, even though the same DCR destination is used for all other metrics.

Is this a known platform limitation for Linux memory counters in azure.vm.linux.guestmetrics?

Thanks

Answer 1

Hello Appmanager Zohocorp,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are seeing Linux VM memory metrics missing from the azure.vm.linux.guestmetrics namespace even though the Azure Monitor Agent is installed and the Linux DCR has memory counters selected.

The issue is not confirmed by the AMA extension status alone.“Provisioning succeeded” only confirms that the Azure Monitor Linux Agent extension was installed; it does not confirm that the DCR was applied, that memory counters were collected, or that they were routed to Azure Monitor Metrics. - https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-troubleshoot-linux-vm

You will need to confirm that the Linux memory performance counters are being sent to Azure Monitor Metrics, not only to Log Analytics. Performance counters sent to Log Analytics appear in the Perf table, while counters sent to Azure Monitor Metrics are the ones available in Metrics Explorer under azure.vm.linux.guestmetrics. - https://learn.microsoft.com/en-us/azure/azure-monitor/vm/data-collection-performance

To resolve this, validate that the DCR association, confirm the AMA service is running, check whether memory counters are arriving in the Perf table, and ensure the DCR performance counter data source has Azure Monitor Metrics as a destination. Guest OS memory metrics are not standard VM host metrics; they must be collected through an agent and routed correctly.

Use the below Microsoft resources for more reading and implementation steps:

I hope this is helpful. Please close the thread by upvoting and accepting the answer if it resolves the issue.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Appmanager Zohocorp 61 Reputation points

2026-07-03T07:24:30.7+00:00

@Sina Salam

Thank you for the guidance. To clarify the current status:

✅ DCR is configured with Azure Monitor Metrics as the destination

✅ Namespace azure.vm.linux.guestmetrics is visible in Metrics Explorer

✅ Other metrics (CPU, Disk, Network) selected in the DCR are listed under the namespace

❌ Only Memory metrics (% Used Memory, Available MBytes, Used Memory MBytes) are not listed in Metrics Explorer

This confirms the DCR configuration and AMA are working correctly for other metrics. The issue appears to be specific to Memory counters not being routed to the Azure Monitor Metrics on Linux, even though the same DCR destination is used for all other metrics.

Is this a known platform limitation for Linux memory counters in azure.vm.linux.guestmetrics?

Thanks
Sina Salam 30,566 Reputation points Volunteer Moderator

2026-07-03T14:37:01.4066667+00:00

Hi @Appmanager Zohocorp

Thank you for your feedback.

Since you've proven that the DCR and Azure Monitor Metrics destination are working for other Linux guest counters.

What you can do is to:

Check whether the memory counters exist in azure.vm.linux.guestmetrics metric definitions.

If they exist, query them directly and treat the portal as the issue.

If they do not exist, recreate/update the DCR with Linux-only memory counter paths and Azure Monitor Metrics destination.

If they still do not appear while CPU/disk/network metrics continue to work, collect evidence from CLI, DCR JSON, and Perf table, then raise a Microsoft support case via PCS: Priority Customer Support - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/priority-community-support as a Linux AMA memory-counter-to-Azure-Monitor-Metrics ingestion/definition issue.

Cheers.

Good Success.