From 8eefe163ac8b7ceb602442b22ec92139bee1eb35 Mon Sep 17 00:00:00 2001 From: Sarah Date: Tue, 17 May 2022 14:44:24 -0400 Subject: [PATCH 1/3] update extra_metrics docs --- .../configuration/instances/openmetrics.yaml | 16 ++++++++-------- .../openmetrics/data/conf.yaml.example | 8 ++++---- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml b/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml index c3dfdab3c6bb9..e225e4036d312 100644 --- a/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml +++ b/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml @@ -28,14 +28,14 @@ 1. If the item is a string, then it represents the exposed metric name, and the sent metric name will be identical. For example: - metrics: + extra_metrics: - - 2. If the item is a mapping, then the keys represent the exposed metric names. a. If a value is a string, then it represents the sent metric name. For example: - metrics: + extra_metrics: - : - : b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -43,7 +43,7 @@ the metric should be handled, overriding any type information the endpoint may provide. For example: - metrics: + extra_metrics: - : name: type: @@ -61,7 +61,7 @@ Regular expressions may be used to match the exposed metric names, for example: - metrics: + extra_metrics: - ^network_(ingress|egress)_.+ - .+: type: gauge @@ -90,14 +90,14 @@ 1. If the item is a string, then it represents the exposed metric name, and the sent metric name will be identical. For example: - metrics: + extra_metrics: - - 2. If the item is a mapping, then the keys represent the exposed metric names. a. If a value is a string, then it represents the sent metric name. For example: - metrics: + extra_metrics: - : - : b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -105,7 +105,7 @@ the metric should be handled, overriding any type information the endpoint may provide. For example: - metrics: + extra_metrics: - : name: type: @@ -123,7 +123,7 @@ Regular expressions may be used to match the exposed metric names, for example: - metrics: + extra_metrics: - ^network_(ingress|egress)_.+ - .+: type: gauge diff --git a/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example b/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example index ad451b09f2cfe..4684099b96924 100644 --- a/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example +++ b/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example @@ -69,14 +69,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -84,7 +84,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -102,7 +102,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge From 6f8103ec5a3358f8c03535a2b042720b3f14b232 Mon Sep 17 00:00:00 2001 From: Sarah Date: Tue, 17 May 2022 14:45:28 -0400 Subject: [PATCH 2/3] Only do for extra metrics --- .../templates/configuration/instances/openmetrics.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml b/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml index e225e4036d312..0cc2a71656295 100644 --- a/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml +++ b/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/openmetrics.yaml @@ -28,14 +28,14 @@ 1. If the item is a string, then it represents the exposed metric name, and the sent metric name will be identical. For example: - extra_metrics: + metrics: - - 2. If the item is a mapping, then the keys represent the exposed metric names. a. If a value is a string, then it represents the sent metric name. For example: - extra_metrics: + metrics: - : - : b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -43,7 +43,7 @@ the metric should be handled, overriding any type information the endpoint may provide. For example: - extra_metrics: + metrics: - : name: type: @@ -61,7 +61,7 @@ Regular expressions may be used to match the exposed metric names, for example: - extra_metrics: + metrics: - ^network_(ingress|egress)_.+ - .+: type: gauge From c16c7b9146f1825146cc71b199f1f1b70e6d2516 Mon Sep 17 00:00:00 2001 From: Sarah Date: Tue, 17 May 2022 14:56:27 -0400 Subject: [PATCH 3/3] Sync config --- .../aerospike/data/conf.yaml.example | 8 ++++---- .../amazon_msk/data/conf.yaml.example | 8 ++++---- .../arangodb/data/conf.yaml.example | 8 ++++---- .../avi_vantage/data/conf.yaml.example | 8 ++++---- .../datadog_checks/calico/data/conf.yaml.example | 8 ++++---- .../datadog_checks/cilium/data/conf.yaml.example | 8 ++++---- .../cockroachdb/data/conf.yaml.example | 8 ++++---- .../coredns/data/conf.yaml.example | 8 ++++---- .../datadog_checks/envoy/data/conf.yaml.example | 8 ++++---- .../haproxy/data/conf.yaml.example | 8 ++++---- .../datadog_checks/istio/data/conf.yaml.example | 8 ++++---- kong/datadog_checks/kong/data/conf.yaml.example | 8 ++++---- .../linkerd/data/conf.yaml.example | 8 ++++---- .../openmetrics/data/conf.yaml.example | 16 ++++++++-------- .../datadog_checks/pulsar/data/conf.yaml.example | 8 ++++---- .../datadog_checks/vault/data/conf.yaml.example | 8 ++++---- 16 files changed, 68 insertions(+), 68 deletions(-) diff --git a/aerospike/datadog_checks/aerospike/data/conf.yaml.example b/aerospike/datadog_checks/aerospike/data/conf.yaml.example index c49ed03764d55..192d9a1e782c3 100644 --- a/aerospike/datadog_checks/aerospike/data/conf.yaml.example +++ b/aerospike/datadog_checks/aerospike/data/conf.yaml.example @@ -64,14 +64,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -79,7 +79,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -97,7 +97,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example b/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example index 42ecea65a34e4..d0805896bee70 100644 --- a/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example +++ b/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example @@ -115,14 +115,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -130,7 +130,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -148,7 +148,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/arangodb/datadog_checks/arangodb/data/conf.yaml.example b/arangodb/datadog_checks/arangodb/data/conf.yaml.example index f6f0912912461..7a42d72362644 100644 --- a/arangodb/datadog_checks/arangodb/data/conf.yaml.example +++ b/arangodb/datadog_checks/arangodb/data/conf.yaml.example @@ -64,14 +64,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -79,7 +79,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -97,7 +97,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example b/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example index 51f4c9e8b2b53..8761e30ac2301 100644 --- a/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example +++ b/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example @@ -75,14 +75,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -90,7 +90,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -108,7 +108,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/calico/datadog_checks/calico/data/conf.yaml.example b/calico/datadog_checks/calico/data/conf.yaml.example index 667f6e368d0a5..e50ac75b57f86 100644 --- a/calico/datadog_checks/calico/data/conf.yaml.example +++ b/calico/datadog_checks/calico/data/conf.yaml.example @@ -64,14 +64,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -79,7 +79,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -97,7 +97,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/cilium/datadog_checks/cilium/data/conf.yaml.example b/cilium/datadog_checks/cilium/data/conf.yaml.example index 42ad45ed5bb80..e4223c45229b1 100644 --- a/cilium/datadog_checks/cilium/data/conf.yaml.example +++ b/cilium/datadog_checks/cilium/data/conf.yaml.example @@ -80,14 +80,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -95,7 +95,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -113,7 +113,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example b/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example index 616449e78598b..a2f5aac04597b 100644 --- a/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example +++ b/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example @@ -65,14 +65,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -80,7 +80,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -98,7 +98,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/coredns/datadog_checks/coredns/data/conf.yaml.example b/coredns/datadog_checks/coredns/data/conf.yaml.example index f29547efd233e..ab03f3e763174 100644 --- a/coredns/datadog_checks/coredns/data/conf.yaml.example +++ b/coredns/datadog_checks/coredns/data/conf.yaml.example @@ -87,14 +87,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -102,7 +102,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -120,7 +120,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/envoy/datadog_checks/envoy/data/conf.yaml.example b/envoy/datadog_checks/envoy/data/conf.yaml.example index 8813ffb963faf..389ac849d7012 100644 --- a/envoy/datadog_checks/envoy/data/conf.yaml.example +++ b/envoy/datadog_checks/envoy/data/conf.yaml.example @@ -76,14 +76,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -91,7 +91,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -109,7 +109,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/haproxy/datadog_checks/haproxy/data/conf.yaml.example b/haproxy/datadog_checks/haproxy/data/conf.yaml.example index d8b0001a67316..8a67a1b18732d 100644 --- a/haproxy/datadog_checks/haproxy/data/conf.yaml.example +++ b/haproxy/datadog_checks/haproxy/data/conf.yaml.example @@ -76,14 +76,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -91,7 +91,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -109,7 +109,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/istio/datadog_checks/istio/data/conf.yaml.example b/istio/datadog_checks/istio/data/conf.yaml.example index e646a0afea9f9..8c4a4ce14af04 100644 --- a/istio/datadog_checks/istio/data/conf.yaml.example +++ b/istio/datadog_checks/istio/data/conf.yaml.example @@ -82,14 +82,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -97,7 +97,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -115,7 +115,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/kong/datadog_checks/kong/data/conf.yaml.example b/kong/datadog_checks/kong/data/conf.yaml.example index 83298ede0158e..16110ed67d3d7 100644 --- a/kong/datadog_checks/kong/data/conf.yaml.example +++ b/kong/datadog_checks/kong/data/conf.yaml.example @@ -74,14 +74,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -89,7 +89,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -107,7 +107,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/linkerd/datadog_checks/linkerd/data/conf.yaml.example b/linkerd/datadog_checks/linkerd/data/conf.yaml.example index 5f6019530fe66..563d96e08c698 100644 --- a/linkerd/datadog_checks/linkerd/data/conf.yaml.example +++ b/linkerd/datadog_checks/linkerd/data/conf.yaml.example @@ -65,14 +65,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -80,7 +80,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -98,7 +98,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example b/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example index 4684099b96924..a5431df41ef89 100644 --- a/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example +++ b/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example @@ -69,14 +69,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## extra_metrics: + ## metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## extra_metrics: + ## metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -84,7 +84,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## extra_metrics: + ## metrics: ## - : ## name: ## type: @@ -102,7 +102,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## extra_metrics: + ## metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge @@ -117,14 +117,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -132,7 +132,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -150,7 +150,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/pulsar/datadog_checks/pulsar/data/conf.yaml.example b/pulsar/datadog_checks/pulsar/data/conf.yaml.example index 723ec7c40929b..0c764f60c61b5 100644 --- a/pulsar/datadog_checks/pulsar/data/conf.yaml.example +++ b/pulsar/datadog_checks/pulsar/data/conf.yaml.example @@ -64,14 +64,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -79,7 +79,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -97,7 +97,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge diff --git a/vault/datadog_checks/vault/data/conf.yaml.example b/vault/datadog_checks/vault/data/conf.yaml.example index 90b09c5bb12af..1e214f29c9ded 100644 --- a/vault/datadog_checks/vault/data/conf.yaml.example +++ b/vault/datadog_checks/vault/data/conf.yaml.example @@ -97,14 +97,14 @@ instances: ## 1. If the item is a string, then it represents the exposed metric name, and ## the sent metric name will be identical. For example: ## - ## metrics: + ## extra_metrics: ## - ## - ## 2. If the item is a mapping, then the keys represent the exposed metric names. ## ## a. If a value is a string, then it represents the sent metric name. For example: ## - ## metrics: + ## extra_metrics: ## - : ## - : ## b. If a value is a mapping, then it must have a `name` and/or `type` key. @@ -112,7 +112,7 @@ instances: ## the metric should be handled, overriding any type information the endpoint ## may provide. For example: ## - ## metrics: + ## extra_metrics: ## - : ## name: ## type: @@ -130,7 +130,7 @@ instances: ## ## Regular expressions may be used to match the exposed metric names, for example: ## - ## metrics: + ## extra_metrics: ## - ^network_(ingress|egress)_.+ ## - .+: ## type: gauge