Provide documentation on metric labelling

docs/configuration/v1.x/metrics/service-bus-queue.md

@@ -10,12 +10,10 @@ The following fields need to be provided:
 - `namespace` - The name of the Service Bus namespace
 - `queueName` - The name of the queue
 
-Supported metrics:
-- `IncomingMessages`
-- `IncomingRequests`
-- `ActiveMessages`
-- `Messages`
-- `Size`
+All supported metrics are documented in the official [Azure Monitor documentation](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/metrics-supported#microsoftservicebusnamespaces).
+
+The following scraper-specific metric label(s) will be added:
+- `entity_name` - Name of the queue
 
 Example:
 ```yaml

docs/configuration/v1.x/metrics/storage-queue.md

@@ -17,6 +17,9 @@ Supported metrics:
 - `TimeSpentInQueue` - Time in seconds that the oldest message has been waiting in the queue to be processed.
 - `MessageCount`
 
+The following scraper-specific metric label(s) will be added:
+- `queue_name` - Name of the queue
+
 Example:
 ```yaml
 name: demo_queue_size

docs/configuration/v1.x/runtime.md

@@ -42,7 +42,7 @@ server:
   httpPort: 80 # Optional. Default: 80
 ```
 
-# Scraping
+# Scraping Prometheus
 Promitor automatically scrapes Azure Monitor and makes the information available based on the metrics configuration.
 
 The behavior of this can be configured to fit your needs:

docs/index.md

@@ -44,6 +44,7 @@ And there is more on the way - Check our [backlog](https://github.com/tomkerkhov
 - **Metrics**
     - [General Declaration](configuration/v0.x/metrics)
     - [Supported Providers](configuration/v0.x/metrics#supported-azure-services)
+    - [What labels do we provide?](metrics/labels)
 - **Configuration**
     - [Runtime](configuration/v0.x/#runtime)
     - [Scraping](configuration/v0.x/#scraping)

docs/metrics/labels.md

@@ -0,0 +1,35 @@
+---
+layout: default
+title: Metric Labels
+---
+
+Here is an overview of how we label metrics.
+
+There are a couple of scenarios where labels are being added:
+- Built-in labels
+- Scaler-specific labels
+- Bring-your-own labels
+
+In case of duplicate label names the above priority will be used.
+
+# Built-in labels
+Every metric that is being reported in the scraping endpoint comes with the following built-in labels:
+- `resource_uri` - Full resource URI of the instance. *(ie `subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.ServiceBus/namespaces/promitor`)*
+- `subscription_id` - Id of the subscription.
+- `resource_group` - Name of the resource group.
+- `instance_name` - Name of the instance, if applicable.
+
+# Scaler-specific labels
+Every scraper can provide additional labels to provide more information.
+
+Currently we support this for:
+- Azure Service Bus
+- Azure Storage Queue
+
+For more information, we recommend reading the [scraper-specific documentation](./../configuration/v1.x/metrics/#supported-azure-services).
+
+# Custom Labels
+
+As of v1.0, you can define your own labels by configuring them for a specific metric.
+
+For more information, see ["Metrics"](./../configuration/v1.x/metrics/#metrics).