From 61fe8a16e7fe6377f80914e37673f04ae505b044 Mon Sep 17 00:00:00 2001 From: Ilia Kurenkov Date: Fri, 19 May 2023 08:50:00 +0200 Subject: [PATCH] fix validation --- rabbitmq/assets/configuration/spec.yaml | 4 +++- rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/rabbitmq/assets/configuration/spec.yaml b/rabbitmq/assets/configuration/spec.yaml index 8d7590509be2ba..4ca44594deab4c 100644 --- a/rabbitmq/assets/configuration/spec.yaml +++ b/rabbitmq/assets/configuration/spec.yaml @@ -53,7 +53,9 @@ files: You can also provide a query exactly as if you were making an HTTP request to this endpoint. For example, `detailed?family=queue_consumer_count`. - You can specify both this and the aggregated endpoint. If you specify both endpoints, metrics from the unaggregated endpoint are prioritized over metrics from the aggregated endpoint in case of name clashes. + You can specify both this and the aggregated endpoint. + If you specify both endpoints, metrics from the unaggregated endpoint are prioritized + over metrics from the aggregated endpoint in case of name clashes. value: type: string example: "detailed" diff --git a/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example b/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example index 1dab4d8f3cc2ee..cfd7a5e7aa21b8 100644 --- a/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example +++ b/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example @@ -80,7 +80,9 @@ instances: ## You can also provide a query exactly as if you were making an HTTP request ## to this endpoint. For example, `detailed?family=queue_consumer_count`. ## - ## You can specify both this and the aggregated endpoint. If you specify both endpoints, metrics from the unaggregated endpoint are prioritized over metrics from the aggregated endpoint in case of name clashes. + ## You can specify both this and the aggregated endpoint. + ## If you specify both endpoints, metrics from the unaggregated endpoint are prioritized + ## over metrics from the aggregated endpoint in case of name clashes. # # unaggregated_endpoint: detailed