describes how azure diagnostics can be enabled on a Virtual Machine Scale Set. The first part covers the steps to enable this for a VMSS running Windows VMs. The steps to enable these for a VMSS running Linux VMs to follow soon.
These steps can be performed on an existing Virtual Machine Scale Set running Windows VMs. In the example here, a VMSS with the following properties pre-exist in Azure before enabling the Diagnostics extension.
VMSS Name - palvmss
VMSS Resource Group Name: palvmssrg
- Azure CLI on the local Computer. Details on this here
The CLI Command to enable the extension is documented here
A Storage Account with the name palvmssstr is created in Azure
The Storage Account name needs to be entered in this Json Document. Save this file to the Working folder on your Computer (PublicSettings.json).
{
"WadCfg": {
"DiagnosticMonitorConfiguration": {
"overallQuotaInMB": 10000,
"DiagnosticInfrastructureLogs": {
"scheduledTransferLogLevelFilter": "Verbose"
},
"PerformanceCounters": {
"scheduledTransferPeriod": "PT1M",
"sinks": "AzureMonitorSink",
"PerformanceCounterConfiguration": [
{
"counterSpecifier": "\\Processor(_Total)\\% Processor Time",
"sampleRate": "PT1M",
"unit": "percent"
},
{
"counterSpecifier":"\\Memory\\Available Bytes",
"sampleRate":"PT15S",
"unit": "Bytes"
}
]
},
"WindowsEventLog": {
"scheduledTransferPeriod": "PT1M",
"DataSource": [
{
"name": "Application!*[System[(Level=1 or Level=2 or Level=3)]]"
},
{
"name": "System!*[System[(Level=1 or Level=2 or Level=3)]]"
},
{
"name": "Security!*[System[(band(Keywords,4503599627370496))]]"
}
]
},
"Logs": {
"scheduledTransferPeriod": "PT1M",
"scheduledTransferLogLevelFilter": "Verbose"
}
},
"SinksConfig": {
"Sink": [
{
"name": "AzureMonitorSink",
"AzureMonitor":
{
}
}]
}
},
"StorageAccount": "palvmssstr",
"StorageType": "TableAndBlob"
}
Add other Performance counters and metrics to the configuration above, as necessary. Shown in this example are just a few of them. More details on these here. The PublicConfig.xml file in this repo has other Performance counters that can be used.
This configuration contains the keys to access the Storage Account. Generate a SAS Key for the Storage Account, from the Azure portal. The '?' preceding the SAS key has to be removed before use. Save this Json document to the working folder on the local Computer(PrivateSettings.json)
{
"storageAccountName": "palvmssstr",
"storageAccountKey": "<Access Key to the Storage Account>",
"storageAccountEndPoint": "https://core.windows.net",
"storageAccountSasToken": "sv=2018-03-28&ss=bfqt&srt=sco&sp=rwdlacup&se=2019-06-29T13:57:55Z&st=2018-12-15T05:57:55Z&spr=https&sig=<generate a SAS Key from the Storage Account>"
}
az vmss diagnostics set --resource-group palvmssrg --settings PublicSettings.json --vmss-name palvmss --no-auto-upgrade --protected-settings PrivateSettings.json
This step takes a couple of minutes to complete After this runs successfully, verify that the diagnostics data is generated, by navigating to the Storage Account, and viewing the Storage Tables - see figure below
Use the Azure Storage Emulator to connect to the Storage Table and view the Diagnostics data generated by the extension.
Enabling the diagnostics extension can also be performed using PowerShell. The command to do that is documented here
$VMSSName = '<vmss name>'
$publicConfigPath = '.\<working folder>\PublicSettings.json'
$privateConfigPath = '.\<working folder>\PrivateSettings.json'
$extName = 'IaaS.Diagnostics'
$typeVersion = 1.5
$ResourceGroupName = '<vmss resource groupname>'
#Login-AzureRmAccount
$VMSS = Get-AzureRmVmss -ResourceGroupName $ResourceGroupName -VMScaleSetName $VMSSName
$returnval = Add-AzureRmVmssDiagnosticsExtension -VirtualMachineScaleSet $VMSS -SettingFilePath $publicConfigPath -ProtectedSettingFilePath $privateConfigPath -Name $extName -TypeHandlerVersion $typeVersion -AutoUpgradeMinorVersion $True -Force
$returnval.ProvisioningState
The ARM Template VMSS-DiagnosticsNew-ARM.json shared in this Repo provisions a new VM Scale Set Resource and enables the Diagnostics extension on it during creation. (Use any of the options - PowerShell, CLI or Template Deployment from the Azure Portal to deploy this Template)
For the scenario when a VMSS already exists and when using an ARM Template to update it to enable the Diagnostics extension, does not seem to work yet.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent