Send Guest OS metrics to the Azure Monitor metric store classic Cloud Services
We recommend that you use the Azure Az PowerShell module to interact with Azure. See Install Azure PowerShell to get started. To learn how to migrate to the Az PowerShell module, see Migrate Azure PowerShell from AzureRM to Az.
With the Azure Monitor Diagnostics extension, you can collect metrics and logs from the guest operating system (Guest OS) running as part of a virtual machine, cloud service, or Service Fabric cluster. The extension can send telemetry to many different locations.
This article describes the process for sending Guest OS performance metrics for Azure classic Cloud Services to the Azure Monitor metric store. Starting with Diagnostics version 1.11, you can write metrics directly to the Azure Monitor metrics store, where standard platform metrics are already collected.
Storing them in this location allows you to access the same actions that you can for platform metrics. Actions include near-real time alerting, charting, routing, access from a REST API, and more. In the past, the Diagnostics extension wrote to Azure Storage, but not to the Azure Monitor data store.
The process that's outlined in this article works only for performance counters in Azure Cloud Services. It doesn't work for other custom metrics.
You must be a service administrator or co-administrator on your Azure subscription.
Your subscription must be registered with Microsoft.Insights.
Your Cloud Service must be in a region that supports custom metrics.
Provision a cloud service and storage account
Create and deploy a classic cloud service. A sample classic Cloud Services application and deployment can be found at Get started with Azure Cloud Services and ASP.NET.
You can use an existing storage account or deploy a new storage account. It's best if the storage account is in the same region as the classic cloud service that you created. In the Azure portal, go to the Storage accounts resource pane, and then select Keys. Take note of the storage account name and the storage account key. You'll need this information in later steps.
Create a service principal
Create a service principal in your Microsoft Entra tenant by using the instructions at Use portal to create a Microsoft Entra application and service principal that can access resources. Note the following while you're going through this process:
- You can put in any URL for the sign-in URL.
- Create new client secret for this app.
- Save the key and the client ID for use in later steps.
Give the app created in the previous step Monitoring Metrics Publisher permissions to the resource you want to emit metrics against. If you plan to use the app to emit custom metrics against many resources, you can grant these permissions at the resource group or subscription level.
The Diagnostics extension uses the service principal to authenticate against Azure Monitor and emit metrics for your cloud service.
Author Diagnostics extension configuration
Prepare your Diagnostics extension configuration file. This file dictates which logs and performance counters the Diagnostics extension should collect for your cloud service. Following is a sample Diagnostics configuration file:
<?xml version="1.0" encoding="utf-8"?> <DiagnosticsConfiguration xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration"> <PublicConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration"> <WadCfg> <DiagnosticMonitorConfiguration overallQuotaInMB="4096"> <DiagnosticInfrastructureLogs scheduledTransferLogLevelFilter="Error" /> <Directories scheduledTransferPeriod="PT1M"> <IISLogs containerName="wad-iis-logfiles" /> <FailedRequestLogs containerName="wad-failedrequestlogs" /> </Directories> <PerformanceCounters scheduledTransferPeriod="PT1M"> <PerformanceCounterConfiguration counterSpecifier="\Processor(_Total)\% Processor Time" sampleRate="PT15S" /> <PerformanceCounterConfiguration counterSpecifier="\Memory\Available MBytes" sampleRate="PT15S" /> <PerformanceCounterConfiguration counterSpecifier="\Memory\Committed Bytes" sampleRate="PT15S" /> <PerformanceCounterConfiguration counterSpecifier="\Memory\Page Faults/sec" sampleRate="PT15S" /> </PerformanceCounters> <WindowsEventLog scheduledTransferPeriod="PT1M"> <DataSource name="Application!*[System[(Level=1 or Level=2 or Level=3)]]" /> <DataSource name="Windows Azure!*[System[(Level=1 or Level=2 or Level=3 or Level=4)]]" /> </WindowsEventLog> <CrashDumps> <CrashDumpConfiguration processName="WaIISHost.exe" /> <CrashDumpConfiguration processName="WaWorkerHost.exe" /> <CrashDumpConfiguration processName="w3wp.exe" /> </CrashDumps> <Logs scheduledTransferPeriod="PT1M" scheduledTransferLogLevelFilter="Error" /> </DiagnosticMonitorConfiguration> <SinksConfig> </SinksConfig> </WadCfg> <StorageAccount /> </PublicConfig> <PrivateConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration"> <StorageAccount name="" endpoint="" /> </PrivateConfig> <IsEnabled>true</IsEnabled> </DiagnosticsConfiguration>
In the "SinksConfig" section of your diagnostics file, define a new Azure Monitor sink:
<SinksConfig> <Sink name="AzMonSink"> <AzureMonitor> <ResourceId>-Provide ClassicCloudService’s Resource ID-</ResourceId> <Region>-Azure Region your Cloud Service is deployed in-</Region> </AzureMonitor> </Sink> </SinksConfig>
In the section of your configuration file where you list the performance counters to collect, add the Azure Monitor sink. This entry ensures that all the performance counters that you specified are routed to Azure Monitor as metrics. You can add or remove performance counters according to your needs.
<PerformanceCounters scheduledTransferPeriod="PT1M" sinks="AzMonSink"> <PerformanceCounterConfiguration counterSpecifier="\Processor(_Total)\% Processor Time" sampleRate="PT15S" /> ... </PerformanceCounters>
Finally, in the private configuration, add an Azure Monitor Account section. Enter the service principal client ID and secret that you created earlier.
<PrivateConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration"> <StorageAccount name="" endpoint="" /> <AzureMonitorAccount> <ServicePrincipalMeta> <PrincipalId>clientId from step 3</PrincipalId> <Secret>client secret from step 3</Secret> </ServicePrincipalMeta> </AzureMonitorAccount> </PrivateConfig>
Save this diagnostics file locally.
Deploy the Diagnostics extension to your cloud service
Launch PowerShell and log in to Azure.
Use the following commands to store the details of the storage account that you created earlier.
$storage_account = <name of your storage account from step 3> $storage_keys = <storage account key from step 3>
Similarly, set the diagnostics file path to a variable by using the following command:
$diagconfig = “<path of the Diagnostics configuration file with the Azure Monitor sink configured>”
Deploy the Diagnostics extension to your cloud service with the diagnostics file with the Azure Monitor sink configured using the following command:
Set-AzureServiceDiagnosticsExtension -ServiceName <classicCloudServiceName> -StorageAccountName $storage_account -StorageAccountKey $storage_keys -DiagnosticsConfigurationPath $diagconfig
It's still mandatory to provide a storage account as part of the installation of the Diagnostics extension. Any logs or performance counters that are specified in the diagnostics config file are written to the specified storage account.
Plot metrics in the Azure portal
Go to the Azure portal.
On the left menu, select Monitor.
On the Monitor pane, select the Metrics Preview tab.
In the resources drop-down menu, select your classic cloud service.
In the namespaces drop-down menu, select azure.vm.windows.guest.
In the metrics drop-down menu, select Memory\Committed Bytes in Use.
You use the dimension filtering and splitting capabilities to view the total memory that's used by a specific role or role instance.
- Learn more about custom metrics.