From 24e6da2461c41b9b3893bcd08cbec6970ae4041e Mon Sep 17 00:00:00 2001 From: Brett Blue Date: Tue, 18 Aug 2026 17:02:29 -0600 Subject: [PATCH] Set the Datadog site in the Kubernetes Metrics setup secret The reference Collector configurations read the Datadog site from a dd-site secret key that falls back to datadoghq.com, but the setup step created the secret with only an API key. Customers on other sites had no instruction to set it. --- .../opentelemetry/integrations/kubernetes_metrics.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/hugo/content/en/opentelemetry/integrations/kubernetes_metrics.md b/hugo/content/en/opentelemetry/integrations/kubernetes_metrics.md index 7178c609a4b..9a14cf79e43 100644 --- a/hugo/content/en/opentelemetry/integrations/kubernetes_metrics.md +++ b/hugo/content/en/opentelemetry/integrations/kubernetes_metrics.md @@ -48,13 +48,16 @@ helm repo update helm install kube-state-metrics prometheus-community/kube-state-metrics ``` -#### 2. Create a Datadog API key secret +#### 2. Create a Datadog configuration secret -Create a Kubernetes secret to store your Datadog API key: +Create a Kubernetes secret to store your Datadog API key and [site][12]. Replace `` with your Datadog site, such as `datadoghq.com` or `datadoghq.eu`: ```sh export DD_API_KEY="" -kubectl create secret generic datadog-secret --from-literal api-key=$DD_API_KEY +export DD_SITE="" +kubectl create secret generic datadog-secret \ + --from-literal api-key="$DD_API_KEY" \ + --from-literal dd-site="$DD_SITE" ``` #### 3. Install the OpenTelemetry Collectors @@ -180,3 +183,4 @@ The [count connector][11] generates object-count metrics by counting the number [9]: https://github.com/open-telemetry/opentelemetry-helm-charts/tree/opentelemetry-collector-0.156.2/charts/opentelemetry-collector [10]: /containers/monitoring/kubernetes_explorer/ [11]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/countconnector +[12]: /getting_started/site/