I've installed Linux Diagnostic Extension 3.0 following steps described here: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/diagnostic-extension

I see [Guest] metrics appearing in the list of metrics, but no [Guest] metrics values are being posted.

Am I missing something? What could be causing a problem?


1 Answer 1


It seems a known issue. If you check extension log, you will see error like below:

enter image description here

The root reason is that Azure Cli 2.0 could not generate sas token contain table.

Please refer to this issue on Github.

A solution to solve this:

You could use Azure Power Shell to generate sas token.

$resourceGroup = "shuicli"
$storageAccountName = "shuiclidiag630"
$storageAccount = Get-AzureRmStorageAccount -ResourceGroupName $resourceGroup -Name $storageAccountName 
$ctx = $storageAccount.Context
$accountSAS = New-AzureStorageAccountSASToken -Service Blob,File,Table,Queue -ResourceType Service,Container,Object -Permission "racwdlup" -Context $ctx

Then replace my_diagnostic_storage_account_sastoken= to sastoken.

I test in my lab, it works for me.

enter image description here

  • The command az storage account generate-sas --account-name $my_diagnostic_storage_account --expiry 9999-12-31T23:59Z --permissions wlacu --resource-types co --services bt -o tsv generate like ss=b&sp=wlacu&sv=2017-04-17&sig=uc93nbzWheETbFAti2rScRKBXzGSfjALpKU4SQUrgUU%3D&srt=co&se=9999-12-31T23%3A59Z ss=b does not contain t table, so, this sas does not have permission to create tables in storage account. Jan 30, 2018 at 7:31
  • I see this issue on github. The issue will resolve in the future version. Jan 30, 2018 at 8:01
  • Thanks for your response! I'm ready to retest. To clarify: the fix was put in azure-storage-python. Is it part of Azure CLI? Should I update Axure CLI before I retest? Feb 2, 2018 at 17:55
  • No, azure-storage-python this python sdk. I test in latest Azure CLI, it does not work for me. I suggest you could use Power Shell to get sas. Feb 5, 2018 at 1:07
  • 1
    Expiration issue was solved since your previous comment. Now I'm using an expiry date far in the future: $resourceGroup = "xxx" $storageAccountName = "xxx" Login-AzureRmAccount $storageAccount = Get-AzureRmStorageAccount -ResourceGroupName $resourceGroup -Name $storageAccountName $ctx = $storageAccount.Context $expiration = [System.DateTime]::Now.AddYears(100) $accountSAS = New-AzureStorageAccountSASToken -Service Blob,File,Table,Queue -ResourceType Service,Container,Object -Permission "racwdlup" -ExpiryTime $expiration -Context $ctx echo "Generated SAS token=$accountSAS" Feb 12, 2018 at 15:56

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .