Adding Azure SQL server metric alert via Bicep fails with "Couldn't find a metric named deadlock."

Based off of what I could see in the AMBA GitHub samples for deadlock, dtu_used and others, they are using are supported metrics for the metricName. If you are using the same bicep file as this then it should work for you. It's hard to tell without seeing your code, but maybe you are having some permission issues. You could look at running the API through Postman and see what result you get.

Some references to look at

• Supported metrics with Azure Monitor
• Metric API

Hi @ lmp

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Hi @ lmp

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thanks for your quick responses!

I'm not 100% sure what I'm supposed to check for using the API, but calling it with

https://management.azure.com/subscriptions/$subscriptionId/resourceGroups/$rgName/providers/Microsoft.Insights/metrics?api-version=2023-10-01&metricnamespace=Microsoft.Sql%2Fservers%2Fdatabases

gets me only this, no other elements in the response object

id                 : subscriptions/$subscriptionId/resourcegroups/$rgName/providers/Microsoft.Insights/metrics/cpu_percent
type               : Microsoft.Insights/metrics
name               : @{value=cpu_percent; localizedValue=CPU percentage}
displayDescription : CPU percentage
unit               : Percent
timeseries         : {}
errorCode          : Success

If I then also add two metric_names, dtu_used and dtu_limit like this

https://management.azure.com/subscriptions/$subscriptionId/resourceGroups/$rgName/providers/Microsoft.Insights/metrics?api-version=2023-10-01&metricnamespace=Microsoft.Sql%2Fservers%2Fdatabases&metricnames=dtu_used%2Cdtu_limit

I get this

id                 : subscriptions/$subscriptionId/resourcegroups/$rgName/providers/Microsoft.Insights/metrics/dtu_used
type               : Microsoft.Insights/metrics
name               : @{value=dtu_used; localizedValue=DTU used}
displayDescription : DTU used. Applies to DTU-based databases.
unit               : Count
timeseries         : {}
errorCode          : Success
id                 : subscriptions/$subscriptionId/resourcegroups/$rgName/providers/Microsoft.Insights/metrics/dtu_limit
type               : Microsoft.Insights/metrics
name               : @{value=dtu_limit; localizedValue=DTU Limit}
displayDescription : DTU Limit. Applies to DTU-based databases.
unit               : Count
timeseries         : {}
errorCode          : Success

Out of the metrics alerts I've tried to create, only dtu_used has been successfully deployed using Bicep.

I've also tried to add dtu_limit, connections_failed and deadlock but all of these result in the error described in my first post.

It seems these metrics should exist since I can easily create metrics alerts for them using Azure portal, it's just the Bicep code that's failing.

The Bicep code I'm using for dtu_limit

resource metricAlert 'Microsoft.Insights/metricAlerts@2018-03-01' = {
  name: alertName
  location: 'global'
  tags: tags
  properties: {
    actions: [
      {
        actionGroupId: actionGroup.id
      }
    ]
    description: alertDescription
    scopes: [targetResourceId]
    severity: alertSeverity
    enabled: isEnabled
    evaluationFrequency: evaluationFrequency
    windowSize: windowSize
    criteria: {
      'odata.type': 'Microsoft.Azure.Monitor.MultipleResourceMultipleMetricCriteria'
      allOf: [
        {
          name: '1st criterion'
          metricName: 'dtu_limit'
          operator: operator
          threshold: threshold
          timeAggregation: timeAggregation
          criterionType: 'StaticThresholdCriterion'
        }
      ]
    }
  }
}

The Bicep code I'm using for dtu_used

resource metricAlert 'Microsoft.Insights/metricAlerts@2018-03-01' = {
  name: alertName
  location: 'global' 
  tags: tags
  properties: {
        actions: [
      {
        actionGroupId: actionGroup.id
        }
      
    ]
    description: alertDescription
    scopes: [targetResourceId]
    severity: alertSeverity
    enabled: isEnabled
    evaluationFrequency: evaluationFrequency
    windowSize: windowSize
    criteria: {
      'odata.type': 'Microsoft.Azure.Monitor.MultipleResourceMultipleMetricCriteria'
      allOf: [
        {
          name: '1st criterion'
          metricName: 'dtu_used'
          operator: operator
          threshold: threshold
          timeAggregation: timeAggregation
          criterionType: 'StaticThresholdCriterion'
        }
      ]
    }
  }
}

Hi @ lmp

Is your Issue resolved?