All the Azure Monitor metrics that needs to be scraped are consolidated in one YAML file. This configuration defines the Azure metadata and all the metrics.

General Declaration

Azure

Metric Defaults

Metrics

Every metric that is being declared needs to define the following fields:

Additionally, the following fields are optional:

Example

Here is an example of how you can scrape two Azure Service Bus queues in different resource groups, one in the promitor resource group and one on the promitor-dev resource group:

azureMetadata:
  tenantId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  subscriptionId: yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
  resourceGroupName: promitor
metricDefaults:
  aggregation:
    interval: 00:05:00
  scraping:
    # Every minute
    schedule: "0 * * ? * *"
metrics:
  - name: demo_queue_size
    description: "Amount of active messages of the 'myqueue' queue"
    resourceType: ServiceBusQueue
    namespace: promitor-messaging
    queueName: orders
    scraping:
      # Every 2 minutes
      schedule: "0 */2 * ? * *"
    azureMetricConfiguration:
      metricName: ActiveMessages
      aggregation:
        type: Total
        interval: 00:15:00
  - name: demo_queue_dev_size
    description: "Amount of active messages of the 'myqueue-dev' queue"
    resourceType: ServiceBusQueue
    namespace: promitor-messaging-dev
    queueName: orders
    resourceGroupName: promitor-dev
    azureMetricConfiguration:
      metricName: ActiveMessages
      aggregation:
        type: Total
        interval: 00:15:00

Supported Azure Services

Generic Azure Resource allows you to scrape every Azure service supported by Azure Monitor.

We also provide a simplified way to scrape the following Azure resources:

Want to help out? Create an issue and contribute a new scraper.

← back