Upgrade to the new monitoring experience - no data

Question

Upgrade to the new monitoring experience - no data

MarcVanderhaegen 256

Hello,

We have set up the 'new monitoring experience' for two arc enabled servers but even 16 hours later there is no data ingested.
The setup is pretty straightforward, you click 'Configure', in the Capabilities, the 'Preview OpenTelemetry metrics' check box is checked and you select the Azure Monitor Workspace (I created a new one when setting up the first machine), you click 'Review + enable' and it is done.

For each machine I got a message 'Onboarding has completed. Data may take a few minutes to start flowing while configuration syncs.' .
So far so good.
But, 16 hours later, there is still no data in the workspace.
I don't know if this could be the problem but when I check the DCRs, I see that a DCR is created for each machine and the platform type of the DCR is set to 'Linux' ! (my test servers are Windows machines)
I can't find any way to change that setting.

If I try to create a new DCR, I can't find the Microsoft-OtelPerfMetrics in the Data source list.

Any ideas if the cause of having no data can be related to the wrong type for the DCRs and how I can correct that ?

Thanks for your help

Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-23T07:56:54.9566667+00:00
Hello MarcVanderhaegen,

You're having trouble with the new monitoring experience on your Arc-enabled servers, not ingesting data even after a significant wait time.

It seems like you've done the initial setup correctly by enabling the "Preview OpenTelemetry metrics" and linking it to a newly created Azure Monitor Workspace. The completion message is a good sign that the onboarding process was initiated successfully.

As you mentioned, the Data Collection Rules (DCRs) are set to 'Linux' while your servers are Windows, it is a factor that could be affecting data collection. DCR should match the operating system of the virtual machines they're monitoring.

The absence of "Microsoft-OtelPerfMetrics" when creating a new DCR could indicate that the necessary monitoring components for OpenTelemetry metrics are not correctly configured or available for Windows, which might be linked to the DCR type issue.

Here are the steps you can try to resolve your issue:

Check DCR Configuration: You can follow the below document to edit DCR: Create data collection rules (DCRs) in Azure Monitor - Azure Monitor | Microsoft Learn

If you are unable to edit or perform modification, the simplest path to correcting the issue is to delete the faulty configuration and create new ones ensuring the correct operating system type is selected.

Remove DCR Association (DCRA):

Go to your Azure Arc-enabled server resource in the Azure portal.

Navigate to Settings > Extensions + applications.

Locate the AzureMonitorWindowsAgent extension.

There should be a link or section to view Data Collection Rules. Disassociate or remove the link to the incorrect Linux DCR.

To delete the Incorrect DCRs:

Go to Azure Monitor > Data Collection Rules

Identify and delete the DCRs with platform type 'Linux' that are assigned to Windows servers

Create New DCRs for Windows: Use Azure CLI or ARM templates to create a DCR with platform type set to Windows

Reassign the New DCRs

Assign the new Windows-based DCRs to your Arc-enabled servers

Confirm that the Azure Monitor Agent (AMA) is installed and running

Verify Agent Installation: Ensure that the Azure Monitor Agent (AMA) is properly installed on your Windows machines, as the monitoring capabilities you're looking for depend on it.

Install and Manage the Azure Monitor Agent - Azure Monitor | Microsoft Learn

Azure Monitor Agent Overview - Azure Monitor | Microsoft Learn

Review Logs: Access Log Analytics and run specific queries to see if any log entries are being recorded at all: Perf | where ObjectName == "Processor" and Computer == "<your_server_name>" | take 10

Update DCR and Check Metrics: Make sure all updates are applied, including any necessary agent updates or Azure Monitor updates. After making these changes, wait to see if data starts showing up after few minutes.

The reason you cannot find Microsoft-OtelPerfMetrics in the standard DCR creation wizard is that these OpenTelemetry metrics are considered custom metrics and are not exposed in the simple wizard UI. You would need to create a DCR with Platform Type: Windows and ensure the data source section (dataSources) includes the correct stream for the metrics extension, targeting the Azure Monitor Metrics destination.

You can follow the below reference: Migrate to VM Insights OpenTelemetry - Azure Monitor | Microsoft Learn

Migrate to VM Insights OpenTelemetry - Azure Monitor | Microsoft Learn

If you still encounter issues, could you please help us on these below questions:

Have you installed and configured the Azure Monitor Agent on the Windows machines?

Are there any error messages or warnings in the Azure portal related to the monitoring setup?

Have you checked the Log Analytics workspace to see if any data is being recorded from the servers?

I hope this helps you resolve the issue effectively!
Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-24T06:57:29.6466667+00:00
Hello MarcVanderhaegen, thank for the update, based on screenshot, it seems that the DCR is using Microsoft-OTelPerfMetrics as a data source, but the telemetry still isn’t flowing. Also, if a Data Collection Rule (DCR) only includes the Microsoft-OTelPerfMetrics stream, it will collect OpenTelemetry metrics but stop collecting standard logs like performance data and event logs. This can break the usual insights you get in Log Analytics.

Ensures all required streams and destinations are included.

Include both metrics and logs in the DCR, your streamDeclarations should include both Microsoft-OTelPerfMetrics that is Azure Monitor Metrics and Perf, InsightsMetrics, and WindowsEventLogs that is Log Analytics

You can follow the below reference:Migrate to VM insights OpenTelemetry - Azure Monitor | Microsoft Learn
Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-28T09:27:51.13+00:00

Hello MarcVanderhaegen, kindly let us know if the provided information that helps you, If you need any further assistance, please feel free to reach out. Thanks,
MarcVanderhaegen 256 Reputation points

2025-10-28T09:33:48.8733333+00:00

Hello, sorry but there is no change to the situation. It is not working at all for us. As soon as the DCR is created through an arm template and configure on a Windows type, it is not working and breaks the ingestion through Log Analytics. And when the DCR is created through the portal during the onboarding, the type is set on Linux and it is not working.

2 answers

Your answer

Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-24T06:57:29.6466667+00:00

Hello MarcVanderhaegen, thank for the update, based on screenshot, it seems that the DCR is using Microsoft-OTelPerfMetrics as a data source, but the telemetry still isn’t flowing. Also, if a Data Collection Rule (DCR) only includes the Microsoft-OTelPerfMetrics stream, it will collect OpenTelemetry metrics but stop collecting standard logs like performance data and event logs. This can break the usual insights you get in Log Analytics.

Ensures all required streams and destinations are included.

Include both metrics and logs in the DCR, your streamDeclarations should include both Microsoft-OTelPerfMetrics that is Azure Monitor Metrics and Perf, InsightsMetrics, and WindowsEventLogs that is Log Analytics

You can follow the below reference:Migrate to VM insights OpenTelemetry - Azure Monitor | Microsoft Learn
Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-28T09:27:51.13+00:00

Hello MarcVanderhaegen, kindly let us know if the provided information that helps you, If you need any further assistance, please feel free to reach out. Thanks,
MarcVanderhaegen 256 Reputation points

2025-10-28T09:33:48.8733333+00:00

Hello, sorry but there is no change to the situation. It is not working at all for us. As soon as the DCR is created through an arm template and configure on a Windows type, it is not working and breaks the ingestion through Log Analytics. And when the DCR is created through the portal during the onboarding, the type is set on Linux and it is not working.

Answer 1

Hello @Bharath Y P

I have tried to create a DCR through an ARM template but it doesn't seem to work.

User's image

Yes, now, it says Windows, but the data sources are not displaying correct values and if I open the DCR it says that the data source is Microsoft-OTelPerfMetrics :
User's image

I applied this DCR to a machine and waited .

Unfortunately, still nothing for the Metrics based visualization, it says 'no events'.

Applying this DCR also 'killed' the insights through log analytics :
User's image

And the message to onboard the machine to the new monitoring experience is back.

So the DCR created, even if the validation was ok, is not good.

To restore the working of log based visualization I had to delete the manually created DCR.

To answer your question :

the Azure Monitor Windows Agent is installed on our machines
there is no error message, the onboarding is always 'successful'
in the log analytics wokspace, data are still ingested but in the azure monitor workspace, no data are ingested (that may be normal because of the linux type DCRs)

Answer 2

Hello @Bharath Y P

I completely understand that seeing only Microsoft-OTelPerfMetrics would tell that no metrics ingestion would be done through Log Analytics but when you configure the new monitoring experience, you clearly configure that the system you continue the ingestion into the Log Analytics workspace :
User's image

But also, the servers are still in the resources list from the DCR that configures the ingestion into Log Analytics so it should never stop sending data there.
At the moment, it is still not working because the DCR created for each machine is still for Linux and not Windows :
User's image

Marc

Share via

Upgrade to the new monitoring experience - no data

2 answers

Your answer