Ensure that the resource_id
for the Service Bus queue is correctly specified.
- The
resource_id
format for Service Bus queues is: - /subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.ServiceBus/namespaces/{namespace-name}/queues/{queue-name}
Check your configuration in azure.yml. You should have something like:
resource_groups:
- resource_group: "your-resource-group" resource_types:
- "Microsoft.ServiceBus/namespaces"
- name: "Messages"
- name: "ActiveMessages"
- name: "DeadletteredMessages"
- Make sure you have the correct permissions set up:
- The service principal needs "Monitoring Reader" role
- For Service Bus specifically, you might also need "Azure Service Bus Data Owner" or "Azure Service Bus Data Reader"
- Verify the metrics you're trying to collect are available through the Azure Monitor API. Common Service Bus metrics include:
- ActiveMessages
- DeadletteredMessages
- IncomingMessages
- OutgoingMessages
- ScheduledMessages
- Make sure you have the correct permissions set up:
- The service principal needs "Monitoring Reader" role
- For Service Bus specifically, you might also need "Azure Service Bus Data Owner" or "Azure Service Bus Data Reader"
- Verify the metrics you're trying to collect are available through the Azure Monitor API. Common Service Bus metrics include:
- ActiveMessages
- DeadletteredMessages
- IncomingMessages
- OutgoingMessages
- ScheduledMessages