VM diagnostics

[prafulbusa]

By following the article below, i am trying to enable the diagnostics settings using Azure CLI instead of manually for my Azure VM. however the script runs fine but it is not enabling the diagnostics setting and also no error message. please help me out with the solution. https://docs.microsoft.com/en-us/cli/azure/vm/diagnostics?view=azure-cli-latest&viewFallbackFrom=azure-cli-latest.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior.

Expected behavior
A clear and concise description of what you expected to happen.

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)

Additional context
Add any other context about the problem here.

[adewaleo]

Hello Praful Busa (@prafulbusa), what does the cli return when you run the command and what did you expect. As much information as possible / reasonable would be helpful. Thanks!

[prafulbusa]

Unable to set guest-level monitoring disagnostic from azure cli.
Cx is automating the creation of VMs using azure cli and one of the things that he was trying to do is set the diagnostics as shown below. When he look at the result from the Azure portal, it shows the diagnostic being set but the the save button is enabled meaning the diagnostic setting has not been saved and has to be done manually. I am not clear as to why this is occurring and what should be done to not end up in such a state.

[adewaleo]

Praful Busa (@prafulbusa) as we have discussed:

• The fact that the save button is not greyed out and is clickable does not mean the diagnostics extension has not been set. If you create a linux vm and check the diagnostics tab on portal or run az vm show before running az vm diagnostics set, you will see that there is a difference before and after. Even if you click the save button, it can be clicked again after the same extension settings have been applied.
• A user can verify that diagnostics have been properly set by looking at the storage account specified in their settings. They should see that diagnostics data is being set to it.
• I will update the documentation example for az vm diagnostics set. Some shell variables were not properly referenced.
• UPDATED: You can use az vm diagnostics set or az vm extensions set to set diagnostics for a windows vm in the same way. az diagnostics set can be thought of as a wrapper around az vm extension set. Simply supply the correct settings and protected settings. You can run az vm diagnostics get-default-config --is-windows-os to get the default config info for a windows vm. This article has more information about setting diagnostics on a windows vm.

[tjprescott]

This syntax {foo} was not used to imply it was a shell variable. It is the standard placeholder syntax we use in examples. However, since the entire example presents itself as a script, it would make sense to use bash variable syntax.

[jagan-at-vi]

I have the same issue - az cli setting of diagnostics does not work for windows unless the save is performed in the portal for that vm's diagnostic setting. (BTW, not an issue with Linux VMs.).

my_vm_resource_id=$(az vm show -g $my_resource_group -n $my_win_vm --query "id" -o tsv)
protected_settings="{'storageAccountName': '${my_diagnostic_storage_account}',
'storageAccountSasToken': '${storage_sastoken}'}"

default_config=$(az vm diagnostics get-default-config --is-windows-os
| sed "s#DIAGNOSTIC_STORAGE_ACCOUNT#$my_diagnostic_storage_account#g"
| sed "s#VM_OR_VMSS_RESOURCE_ID#$my_vm_resource_id#g")

storage_sastoken=$(az storage account generate-sas
--account-name $my_diagnostic_storage_account --expiry 2037-12-31T23:59:00Z
--permissions wlacu --resource-types co --services bt -o tsv)

az vm extension set --publisher Microsoft.Azure.Diagnostics
--name IaaSDiagnostics
--protected-settings "${protected_settings}"
--settings "${default_config}"
--version "1.5"
--resource-group $my_resource_group --vm-name $my_win_vm

[jagan-at-vi]

Outputs using
az vm show -n gr-sim-win -g gr-rg-westcentralus --query "resources[]"

[adewaleo]

jagan-at-vi, I will look into this. You can remove / update the txt files. They have your subscriptions ids in them.

Travis Prescott (@tjprescott), ah I see, this is good to know. I wasn't aware of this format

[adewaleo]

jagan-at-vi, I could reproduce this issue with windows VMs. I, too, couldn't set the extension. Even after fixing / altering the default config settings. It seems, this might be a service side issue.

I reached out to the extension's documentation authors for help.