From b855990c7c0bd5cda3a9b429a67b283287be832e Mon Sep 17 00:00:00 2001 From: Koichi Shimada Date: Sat, 15 Aug 2026 18:33:50 +0900 Subject: [PATCH] Fix the annotation key names listed in the AD Annotations v1 tab The AD Annotations v1 tab named `ad.datadoghq.com/.checks` as the check configuration key. That is the v2 key: the sentence was duplicated from the v2 tab, where it is correct. The YAML example in the same tab already used the three v1 keys, so the tab contradicted itself. --- hugo/content/en/getting_started/containers/autodiscovery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo/content/en/getting_started/containers/autodiscovery.md b/hugo/content/en/getting_started/containers/autodiscovery.md index 2d1d084d4bc..fd0a7f14050 100644 --- a/hugo/content/en/getting_started/containers/autodiscovery.md +++ b/hugo/content/en/getting_started/containers/autodiscovery.md @@ -103,7 +103,7 @@ annotations: In the example above, the `tags.datadoghq.com` labels set the `env`, `service`, and even `version` as tags for all logs and metrics emitted for the pod's `redis` container. These standard labels are part of [Unified Service Tagging][1]. As a best practice, Datadog recommends using unified service tagging when configuring tags and environment variables. -The check configuration annotation key follows the format `ad.datadoghq.com/.checks`. +The check configuration annotation keys follow the format `ad.datadoghq.com/.check_names`, `ad.datadoghq.com/.init_configs`, and `ad.datadoghq.com/.instances`. `check_names` includes the names of the check to run, and `init_configs` contains some configuration parameters, such as minimum collection interval. Each item in `instances` represents the configuration to run for one instance of a check. **Note**: In this example, `%%host%%` is a template variable that is dynamically populated with your container's IP.