From 93d13c59d01047e1e28b5558baf56100aefcfa94 Mon Sep 17 00:00:00 2001 From: Fabian Reinartz Date: Sun, 23 Dec 2018 13:06:36 +0100 Subject: [PATCH] Sort Signed-off-by: Fabian Reinartz --- docs/configuration/configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuration/configuration.md b/docs/configuration/configuration.md index a0d069c3e..545fa8394 100644 --- a/docs/configuration/configuration.md +++ b/docs/configuration/configuration.md @@ -259,8 +259,6 @@ Azure SD configurations allow retrieving scrape targets from Azure VMs. The following meta labels are available on targets during relabeling: -* `__meta_azure_subscription_id`: the subscription ID -* `__meta_azure_tenant_id`: the tenant ID * `__meta_azure_machine_id`: the machine ID * `__meta_azure_machine_location`: the location the machine runs in * `__meta_azure_machine_name`: the machine name @@ -269,6 +267,8 @@ The following meta labels are available on targets during relabeling: * `__meta_azure_machine_resource_group`: the machine's resource group * `__meta_azure_machine_tag_`: each tag value of the machine * `__meta_azure_machine_scale_set`: the name of the scale set which the vm is part of (this value is only set if you are using a [scale set](https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/)) +* `__meta_azure_subscription_id`: the subscription ID +* `__meta_azure_tenant_id`: the tenant ID See below for the configuration options for Azure discovery: