Failed to create monitor diagnostic setting with StorageWrite

[neil-yechenwei]

Seems it failed to create monitor diagnostic setting with StorageWrite using azure go sdk client and throw below error message.
According by the doc, I assume it has been supported by azure portal. So I assume it should also be supported by rest api, right?

Error message:

Error: Error creating Monitor Diagnostics Setting "storageodgxstor-logs" for Resource "/subscriptions/xx-xx-xx-xx/resourceGroups/storage-odgx/providers/Microsoft.Storage/storageAccounts/storageodgxstor": insights.DiagnosticSettingsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Category 'StorageWrite' is not supported."

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

[blueww]

This looks like a DiagnosticSetting API issue instead of storage API issue.
Add "DiagnosticSetting" tag.

[jrauschenbusch]

any progress here?

[jmkimball55]

any progress here?

J Kimball - Integration Platforms and Engineering

[ishepherd]

Error: Error creating Monitor Diagnostics Setting "storageodgxstor-logs" for Resource "/subscriptions/xx-xx-xx-xx/resourceGroups/storage-odgx/providers/Microsoft.Storage/storageAccounts/storageodgxstor": <...snip...> Category 'StorageWrite' is not supported."

Possibly you tried to target the diagnostic setting at the storage account? Microsoft.Storage/storageAccounts resource

Blob diagnostic settings are actually targeted to the Microsoft.Storage/storageAccounts/blobServices resource.

This comment helped me: hashicorp/terraform-provider-azurerm#8275 (comment)

[andaryjo]

What worked for me is using .../storageAccounts/<account>/blobServices/default as resource ID.

[MarcoCavalazzi]

Hi guys, to complement @andaryjo's comment, this configuration is working for me:

# Diagnostic settings for the metrics of the storage account.
resource "azurerm_monitor_diagnostic_setting" "storageaccount_diagnostic" {
  name                       = "${var.environment}-${var.storage_account.name}-diagnostic"
  target_resource_id         = azurerm_storage_account.storageaccount.id
  log_analytics_workspace_id = var.loganalytics_workspace_id
  
  # All metrics
  metric {
    category = "Capacity"
    enabled  = true
  }
  metric {
    category = "Transaction"
    enabled  = true
  }
}
# Diagnostic settings (metrics and logs) for the storage account's blob containers. It's configured once to cover all blobs.
resource "azurerm_monitor_diagnostic_setting" "storageaccount_diagnostic_blobs" {
  name                       = "${var.environment}-${var.storage_account.name}-diagnostic-blobs"
  target_resource_id         = "${azurerm_storage_account.storageaccount.id}/blobServices/default/"
  log_analytics_workspace_id = var.loganalytics_workspace_id

  enabled_log {
    category_group = "allLogs"
  }
  
  # All metrics
  metric {
    category = "Capacity"
    enabled  = true
  }
  metric {
    category = "Transaction"
    enabled  = true
  }
}

I did the same for the tables and queues, using an additional resource and changing the target_resource_id reference to:

• "${azurerm_storage_account.storageaccount[0].id}/tableServices/default/"
• "${azurerm_storage_account.storageaccount[0].id}/queueServices/default/"

Naturally the variables will need to be updated to reflect your environment.