Set-AzureRmDiagnosticSetting in Module 5.1.0 does not work

[DirkBrinkmann]

Description

With 5.1.0 you introduced the new -Name parameter. Great! But unfortunately it does not work and the whole Cmdlet seems to be broken!

Script/Steps for Reproduction

If you specifiy the -name param or not, you will always get the error:

The diagnostic setting 'service' [or whatever name you entered]
doesn't exist., Code: ResourceNotFound, Status code:NotFound, Reason phrase: Not Found

Module Version

5.1.0

Environment Data

$PSVersionTable

Debug Output

<Set-AzureRmDiagnosticSetting : Exception type: ErrorResponseException, Message: The diagnostic setting 'service'
doesn't exist., Code: ResourceNotFound, Status code:NotFound, Reason phrase: Not Found
At line:1 char:1

• Set-AzureRmDiagnosticSetting -ResourceId $r.Id -WorkspaceId /subscrip ...

•   + CategoryInfo          : CloseError: (:) [Set-AzureRmDiagnosticSetting], PSInvalidOperationException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Insights.Diagnostics.SetAzureRmDiagnosticSettingCommand
  

[markcowl]

@DirkBrinkmann Can you include some additional information so we can diagnose this:

Run $DebugPreference="Continue" and then execute the cmdlet and include the debug output.

Run Resolve-AzureRmError after the failure.

[Orange-MM]

I am also confronted with the same problem with @DirkBrinkmann as well.
In my case, I'm trying to set up a new diagnostic log for Azure SQL Database as shown below.

Import-Module AzureRM
Get-Module AzureRM

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     6.6.0      AzureRM


Get-Module AzureRM.Insights

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     5.1.0      AzureRM.Insights                    {Add-AzureRmAutoscaleSetting, Add-AzureRmLogProfile, Add-A...

$sqlDbInfo = Get-AzureRmSqlDatabase `
    -DatabaseName "*****" `
    -ServerName "*****" `
    -ResourceGroupName "*****"

$storageInfo = Get-AzureRMStorageAccount `
    -ResourceGroupName "*****" `
    -Name "*****"

Set-AzureRmDiagnosticSetting `
    -ResourceId "$($sqlDbInfo.ResourceId)" `
    -StorageAccountId "$($storageInfo.Id)" `
    -Enabled $true `
    -RetentionEnabled $true `
    -RetentionInDays 3

警告: 11:17:28 - *** The namespace for all the model classes will change from Microsoft.Azure.Management.Monitor.Management.Models to Microsoft.Azure.Management.Monitor.Models in future releases.
警告: 11:17:28 - *** The namespace for output classes will be uniform for all classes in future releases to make it independent of modifications in the model classes.
警告: 11:17:28 - The arguments Categories and Timegrains now have aliases Category and Timegrain respectively. The plural names will be removed in future releases.
Set-AzureRmDiagnosticSetting : Exception type: ErrorResponseException, Message: The diagnostic setting 'service' doesn't exist., Code: ResourceNotFound, Status code:NotFound, Reason phrase: Not Found
発生場所 行:1 文字:1
+ Set-AzureRmDiagnosticSetting `
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Set-AzureRmDiagnosticSetting]、PSInvalidOperationException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Insights.Diagnostics.SetAzureRmDiagnosticSettingCommand

According to the advice from @markcowl, I will post the debug output.

Message        : Exception type: ErrorResponseException, Message: The diagnostic setting 'service' doesn't exist., Code: ResourceNotFound, Status code:NotFound, Reason phrase: Not Found
StackTrace     :    場所 Microsoft.Azure.Commands.Insights.MonitorCmdletBase.ExecuteCmdlet()
                    場所 Microsoft.WindowsAzure.Commands.Utilities.Common.AzurePSCmdlet.ProcessRecord()
Exception      : System.Management.Automation.PSInvalidOperationException
InvocationInfo : {Set-AzureRmDiagnosticSetting}
Line           : Set-AzureRmDiagnosticSetting `

Position       : 発生場所 行:1 文字:1
                 + Set-AzureRmDiagnosticSetting `
                 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 10

Message        : Operation returned an invalid status code 'NotFound'
StackTrace     :    場所 Microsoft.Azure.Management.Monitor.DiagnosticSettingsOperations.<GetWithHttpMessagesAsync>d__5.MoveNext()
                 --- 直前に例外がスローされた場所からのスタック トレースの終わり ---
                    場所 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                    場所 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
                    場所 Microsoft.Azure.Management.Monitor.DiagnosticSettingsOperationsExtensions.<GetAsync>d__1.MoveNext()
Exception      : Microsoft.Azure.Management.Monitor.Models.ErrorResponseException
InvocationInfo : {Set-AzureRmDiagnosticSetting}
Line           : Set-AzureRmDiagnosticSetting `

Position       : 発生場所 行:1 文字:1
                 + Set-AzureRmDiagnosticSetting `
                 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 10

[DirkBrinkmann]

@markcowl: Are you fine with @Orange-MM Output?

[vinaydam]

We are also facing the same issue. @markcowl Could you please provide an update on this issue?

[amoghnatu]

@markcowl We're also seeing the below exception when passing PT1M as Timegrain.

Set-AzureRmDiagnosticSetting : Metric timegrain 'PT1M' is not available
At D:\Set-AzureRmDiagnosticSetting.ps1:64 char:19
 ... agnostics = Set-AzureRmDiagnosticSetting -ResourceId $ResourceId -Ena ...
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     CategoryInfo          : CloseError: (:) [Set-AzureRmDiagnosticSetting], ArgumentException
     FullyQualifiedErrorId : Microsoft.Azure.Commands.Insights.Diagnostics.SetAzureRmDiagnosticSettingCommand

[seanke]

Also having this issue.

[Orange-MM]

@markcowl:
It is additional information.

• This problem occurred when "Set-AzureRmDiagnosticSetting" was executed with the diagnostic setting turned off.
• This problem didn't occur if you executed the "Set-AzureRmDiagnosticSetting" after setting the diagnostic setting to name = "service" from Azure portal and turning it on first.