Merge branch 'master' into dd/fouad/llm-evals-investigate

Author: gsvigruha

hugo/config/_default/params.yaml

@@ -288,6 +288,7 @@ core_product:
 
 # Unsupported sites for each product
 unsupported_sites:
+  remediate_with_ai: [gov, gov2]
   cloudcraft_apm_overlay: [gov, gov2]
   code_locations: [gov, gov2]
   ownership_of_views: [gov, gov2]

hugo/content/en/containers/monitoring/kubernetes_explorer.md

@@ -80,6 +80,8 @@ For manual setup, see [Set up Kubernetes Explorer with a DaemonSet][1].
 
 You can populate the Kubernetes Explorer using a native OpenTelemetry pipeline instead of the Datadog Agent. This setup uses the [`k8sobjects`][1] receiver to collect Kubernetes resource data and forwards it through the [Datadog Exporter's][2] orchestrator explorer functionality.
 
+{{< site-region region="gov,gov2" >}}<div class="alert alert-warning">This feature is not available for {{< region-param key="dd_site_name" >}}.</div>{{< /site-region >}}
+
 #### Prerequisites
 
 - OpenTelemetry Collector Contrib [v0.154.0][3] or later.
@@ -304,6 +306,8 @@ The [`opentelemetry-kube-stack`][1] Helm chart installs the OpenTelemetry Operat
 - **`cluster`** (Deployment): Scrapes kube-state-metrics, watches Kubernetes objects, and enables `orchestrator_explorer` to populate Kubernetes Explorer.
 - **`daemon`** (DaemonSet): Collects host and kubelet metrics, and exposes an OTLP endpoint for application telemetry data.
 
+{{< site-region region="gov,gov2" >}}<div class="alert alert-warning">This feature is not available for {{< region-param key="dd_site_name" >}}.</div>{{< /site-region >}}
+
 #### Prerequisites
 
 - OpenTelemetry Kube Stack Helm chart [0.20.1][3] or later.

hugo/content/en/observability_pipelines/configuration/secrets_management.md

@@ -41,7 +41,7 @@ Datadog recommends using the [instance profile method][1] of retrieving secrets
 After you [install the Worker][1], configure the Worker's [bootstrap file][2] to resolve secrets using AWS Secrets Manager:
 
 ```yaml
-backend_type: aws.secrets
+backend_type: aws
 backend_config:
   aws_session:
     aws_region: <region_name>
@@ -58,7 +58,7 @@ Before you [install the Worker][1], add the bootstrap configuration to the [`dat
 bootstrap:
   config:
     secret:
-      backend_type: aws.secrets
+      backend_type: aws
       backend_config:
         aws_session:
           aws_region: <region_name>
@@ -147,7 +147,7 @@ To access your Key Vault, create a Managed Identity and assign it to your VM. Th
 After you [install the Worker][1], configure the Worker's [bootstrap file][2] to resolve secrets using Azure Key Vault:
 
 ```yaml
-backend_type: azure.keyvault
+backend_type: azure
 backend_config:
   keyvaulturl: <key_vault_url>
 ```
@@ -163,7 +163,7 @@ Before you [install the Worker][1], add the bootstrap configuration to the [`dat
 bootstrap:
   config:
     secret:
-      backend_type: azure.keyvault
+      backend_type: azure
       backend_config:
         keyvaulturl: <key_vault_url>
 ```