From a926b12686a9cd7740b6047bf9064fb974d8a46b Mon Sep 17 00:00:00 2001 From: natemollica-dev Date: Fri, 16 Feb 2024 15:38:10 -0800 Subject: [PATCH] Revide working for OpenMetrics metrics mapping --- website/content/docs/k8s/connect/observability/datadog.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/k8s/connect/observability/datadog.mdx b/website/content/docs/k8s/connect/observability/datadog.mdx index d2ff21d2fb..5f11bf387f 100644 --- a/website/content/docs/k8s/connect/observability/datadog.mdx +++ b/website/content/docs/k8s/connect/observability/datadog.mdx @@ -399,7 +399,7 @@ This method of integration is useful for cases where Prometheus enabled scrapes By default, all metrics pulled using this method will scrape Consul metrics using the `/v1/agent/metrics?format=prometheus` API query, and are considered to be **_custom metrics_**. -Use of this method will map to Datadog as described in [Mapping Prometheus Metrics to Datadog Metrics](https://docs.datadoghq.com/integrations/guide/prometheus-metrics/?tab=latestversion) and is summarized in the table below. +Use of this method maps to Datadog as described in [Mapping Prometheus Metrics to Datadog Metrics](https://docs.datadoghq.com/integrations/guide/prometheus-metrics/?tab=latestversion). The following table summarizing how these metrics map to each other. | OpenMetrics metric type | Datadog metric type | |:------------------------|:-----------------------------------|