From 90009b2f700ad15bd42bd0a05e914cf806277ddb Mon Sep 17 00:00:00 2001 From: Minyi Zhu Date: Wed, 9 Apr 2025 16:12:33 -0400 Subject: [PATCH 1/3] add check_tag_cardinality --- content/en/getting_started/integrations/_index.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/content/en/getting_started/integrations/_index.md b/content/en/getting_started/integrations/_index.md index fa6952282f4..e081a54801e 100644 --- a/content/en/getting_started/integrations/_index.md +++ b/content/en/getting_started/integrations/_index.md @@ -100,12 +100,22 @@ For example, setting `service` in your config file is the recommended [Agent set To better unify your environment, it is also recommended to configure the `env` tag in the Agent. To learn more, see [Unified Service Tagging][27]. +#### Per-check tag configuration +You can customize tag behavior for individual checks, overriding the global Agent-level settings: + +1. Disable Autodiscovery Tags By default, the metrics reported by integrations include tags autodiscovered from the environment. For example, the metrics reported by a Redis check that runs inside a container include tags that refer to the container, such as `image_name`. You can turn this behavior off by setting the `ignore_autodiscovery_tags` parameter to `true`: +2. Set Tag Cardinality Per Integration Check +You can define the level of tag cardinality (low, orchestrator, or high) on a per-check basis using the `check_tag_cardinality` parameter. This overrides the global tag_cardinality setting defined in the Agent configuration. + ```yaml init_config: - +# Ignores tags coming from autodiscovery ignore_autodiscovery_tags: true +# Override global tag cardinality setting +check_tag_cardinality: low + # Rest of the config here ``` From 1a4fc98a8830bd7f2c3e8a8a0893aac756d12533 Mon Sep 17 00:00:00 2001 From: domalessi <111786334+domalessi@users.noreply.github.com> Date: Fri, 18 Apr 2025 11:57:09 -0400 Subject: [PATCH 2/3] Update content/en/getting_started/integrations/_index.md --- content/en/getting_started/integrations/_index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/getting_started/integrations/_index.md b/content/en/getting_started/integrations/_index.md index e081a54801e..5ef53b3c65e 100644 --- a/content/en/getting_started/integrations/_index.md +++ b/content/en/getting_started/integrations/_index.md @@ -103,10 +103,10 @@ To better unify your environment, it is also recommended to configure the `env` #### Per-check tag configuration You can customize tag behavior for individual checks, overriding the global Agent-level settings: -1. Disable Autodiscovery Tags -By default, the metrics reported by integrations include tags autodiscovered from the environment. For example, the metrics reported by a Redis check that runs inside a container include tags that refer to the container, such as `image_name`. You can turn this behavior off by setting the `ignore_autodiscovery_tags` parameter to `true`: -2. Set Tag Cardinality Per Integration Check -You can define the level of tag cardinality (low, orchestrator, or high) on a per-check basis using the `check_tag_cardinality` parameter. This overrides the global tag_cardinality setting defined in the Agent configuration. +1. **Disable autodiscovery tags** + By default, the metrics reported by integrations include tags autodiscovered from the environment. For example, the metrics reported by a Redis check that runs inside a container include tags that refer to the container, such as `image_name`. You can turn this behavior off by setting the `ignore_autodiscovery_tags` parameter to `true`. +2. **Set tag cardinality per integration check** + You can define the level of tag cardinality (low, orchestrator, or high) on a per-check basis using the `check_tag_cardinality` parameter. This overrides the `global tag_cardinality` setting defined in the Agent configuration. ```yaml init_config: From 48032de649d774c864706e99218678dd22f3add2 Mon Sep 17 00:00:00 2001 From: Dominique Alessi Date: Fri, 18 Apr 2025 12:10:35 -0400 Subject: [PATCH 3/3] formatting tweaks --- content/en/getting_started/integrations/_index.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/content/en/getting_started/integrations/_index.md b/content/en/getting_started/integrations/_index.md index 5ef53b3c65e..e2c3819436d 100644 --- a/content/en/getting_started/integrations/_index.md +++ b/content/en/getting_started/integrations/_index.md @@ -103,10 +103,13 @@ To better unify your environment, it is also recommended to configure the `env` #### Per-check tag configuration You can customize tag behavior for individual checks, overriding the global Agent-level settings: -1. **Disable autodiscovery tags** - By default, the metrics reported by integrations include tags autodiscovered from the environment. For example, the metrics reported by a Redis check that runs inside a container include tags that refer to the container, such as `image_name`. You can turn this behavior off by setting the `ignore_autodiscovery_tags` parameter to `true`. -2. **Set tag cardinality per integration check** - You can define the level of tag cardinality (low, orchestrator, or high) on a per-check basis using the `check_tag_cardinality` parameter. This overrides the `global tag_cardinality` setting defined in the Agent configuration. +1. **Disable Autodiscovery tags** + + By default, the metrics reported by integrations include tags automatically detected from the environment. For example, the metrics reported by a Redis check that runs inside a container include tags associated with the container, such as `image_name`. You can turn this behavior off by setting the `ignore_autodiscovery_tags` parameter to `true`. + +1. **Set tag cardinality per integration check** + + You can define the level of tag cardinality (low, orchestrator, or high) on a per-check basis using the `check_tag_cardinality` parameter. This overrides the global tag cardinality setting defined in the Agent configuration. ```yaml init_config: