Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix extra metrics description example #12043

Merged
merged 3 commits into from
May 18, 2022
Merged

Fix extra metrics description example #12043

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8eefe16
update extra_metrics docs
sarah-witt May 17, 2022
6f8103e
Only do for extra metrics
sarah-witt May 17, 2022
c16c7b9
Sync config
sarah-witt May 17, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Sync config
  • Loading branch information
@sarah-witt
sarah-witt committed May 17, 2022
commit c16c7b9146f1825146cc71b199f1f1b70e6d2516
8 changes: 4 additions & 4 deletions aerospike/datadog_checks/aerospike/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,22 +64,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,22 +115,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions arangodb/datadog_checks/arangodb/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,22 +64,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,22 +75,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions calico/datadog_checks/calico/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,22 +64,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions cilium/datadog_checks/cilium/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,22 +80,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,22 +65,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions coredns/datadog_checks/coredns/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,22 +87,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions envoy/datadog_checks/envoy/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,22 +76,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions haproxy/datadog_checks/haproxy/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,22 +76,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
8 changes: 4 additions & 4 deletions istio/datadog_checks/istio/data/conf.yaml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,22 +82,22 @@ 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:
## - <METRIC_1>
## - <METRIC_2>
## 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:
## - <EXPOSED_METRIC_1>: <SENT_METRIC_1>
## - <EXPOSED_METRIC_2>: <SENT_METRIC_2>
## b. If a value is a mapping, then it must have a `name` and/or `type` key.
## The `name` represents the sent metric name, and the `type` represents how
## the metric should be handled, overriding any type information the endpoint
## may provide. For example:
##
## metrics:
## extra_metrics:
## - <EXPOSED_METRIC_1>:
## name: <SENT_METRIC_1>
## type: <METRIC_TYPE_1>
Expand All @@ -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
Expand Down
Loading