[pull] master from DataDog:master

hugo/.gitignore

@@ -181,6 +181,8 @@ content/en/containers/datadog_operator/secret_management.md
 content/en/containers/guide/v2alpha1_migration.md
 content/en/containers/datadog_operator/kubectl_plugin.md
 content/en/containers/datadog_operator/migration.md
+content/en/containers/datadog_operator/datadog_agent_profiles.md
+content/en/containers/datadog_operator/providers.md
 
 # serverless
 content/en/serverless/libraries_integrations/plugin.md
@@ -311,7 +313,7 @@ assets/jsconfig.json
 local/bin/py/build/*
 # Unignore the configurations folder, so we can apply exceptions to it
 !local/bin/py/build/configurations/
-# Ignore everything inside the configurations folder, 
+# Ignore everything inside the configurations folder,
 # except for the files we add explicit exceptions for
 local/bin/py/build/configurations/*
 !local/bin/py/build/configurations/pull_config_preview.yaml
@@ -349,4 +351,4 @@ playwright-report/
 
 # AI
 .superpowers/
-data/site_region_usage.json
+data/site_region_usage.json

hugo/assets/scripts/components/conversational-search/suggested-questions.js

@@ -18,7 +18,7 @@ const SUGGESTED_QUESTIONS = [
     'How do I set up Real User Monitoring (RUM) for a web application?',
     'How do I monitor AWS Lambda functions with Datadog?',
     'How do I enable Continuous Profiler for a Java service?',
-    'How do I trace LLM application calls with Datadog LLM Observability?',
+    'How do I trace LLM application calls with Datadog Agent Observability?',
     'How do I create a Service Level Objective (SLO) in Datadog?',
     'How do I send OpenTelemetry traces to Datadog?',
     'How do I track AWS cloud costs in Datadog?'

hugo/config/_default/menus/api.en.yaml

@@ -11913,6 +11913,75 @@ menu:
           - SearchIssues
         unstable: []
         order: 1
+    - name: Execution Policy
+      url: /api/latest/execution-policy/
+      identifier: execution-policy
+      generated: true
+    - name: Update an execution policy
+      url: /api/latest/execution-policy/update-an-execution-policy/
+      identifier: execution-policy-update-an-execution-policy
+      parent: execution-policy
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - UpdateExecutionPolicy
+        unstable:
+          - v2
+        order: 12
+    - name: Get an execution policy
+      url: /api/latest/execution-policy/get-an-execution-policy/
+      identifier: execution-policy-get-an-execution-policy
+      parent: execution-policy
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - GetExecutionPolicy
+        unstable:
+          - v2
+        order: 11
+    - name: Delete an execution policy
+      url: /api/latest/execution-policy/delete-an-execution-policy/
+      identifier: execution-policy-delete-an-execution-policy
+      parent: execution-policy
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - DeleteExecutionPolicy
+        unstable:
+          - v2
+        order: 13
+    - name: Create an execution policy
+      url: /api/latest/execution-policy/create-an-execution-policy/
+      identifier: execution-policy-create-an-execution-policy
+      parent: execution-policy
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - CreateExecutionPolicy
+        unstable:
+          - v2
+        order: 10
+    - name: List execution policies
+      url: /api/latest/execution-policy/list-execution-policies/
+      identifier: execution-policy-list-execution-policies
+      parent: execution-policy
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - ListExecutionPolicies
+        unstable:
+          - v2
+        order: 9
     - name: Fastly Integration
       url: /api/latest/fastly-integration/
       identifier: fastly-integration

hugo/config/_default/menus/main.en.yaml

@@ -3307,7 +3307,7 @@ menu:
       parent: containers
       identifier: containers_autoscaling
       weight: 2
-    - name: Cluster 
+    - name: Cluster
       url: containers/autoscaling/cluster
       parent: containers_autoscaling
       identifier: containers_autoscaling_cluster
@@ -3512,41 +3512,51 @@ menu:
       identifier: containers_datadog_operator_configuration
       parent: containers_datadog_operator
       weight: 803
+    - name: Datadog Agent Profiles
+      url: containers/datadog_operator/datadog_agent_profiles
+      identifier: containers_datadog_operator_agent_profiles
+      parent: containers_datadog_operator
+      weight: 804
+    - name: Providers
+      url: containers/datadog_operator/providers
+      identifier: containers_datadog_operator_providers
+      parent: containers_datadog_operator
+      weight: 805
     - name: Custom Checks
       url: containers/datadog_operator/custom_check
       identifier: containers_datadog_operator_customchecks
       parent: containers_datadog_operator
-      weight: 804
+      weight: 806
     - name: Data Collected
       url: containers/datadog_operator/data_collected
       identifier: containers_datadog_operator_datacollected
       parent: containers_datadog_operator
-      weight: 805
+      weight: 807
     - name: Secret Management
       url: containers/datadog_operator/secret_management
       identifier: containers_datadog_operator_secretmanagement
       parent: containers_datadog_operator
-      weight: 806
+      weight: 808
     - name: DatadogDashboard CRD
       url: containers/datadog_operator/crd_dashboard
       identifier: containers_datadog_operator_crd_dashboard
       parent: containers_datadog_operator
-      weight: 807
+      weight: 809
     - name: DatadogGenericResource CRD
       url: containers/datadog_operator/crd_ddgr
       identifier: containers_datadog_operator_crd_ddgr
       parent: containers_datadog_operator
-      weight: 808
+      weight: 810
     - name: DatadogMonitor CRD
       url: containers/datadog_operator/crd_monitor
       identifier: containers_datadog_operator_crd_monitor
       parent: containers_datadog_operator
-      weight: 809
+      weight: 811
     - name: DatadogSLO CRD
       url: containers/datadog_operator/crd_slo
       identifier: containers_datadog_operator_crd_slo
       parent: containers_datadog_operator
-      weight: 810
+      weight: 812
     - name: Troubleshooting
       url: containers/troubleshooting/
       parent: containers
@@ -6463,56 +6473,66 @@ menu:
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_variants
       weight: 302
+    - name: Evaluation Context
+      url: feature_flags/concepts/evaluation_context
+      parent: feature_flags_concepts
+      identifier: feature_flags_concepts_evaluation_context
+      weight: 303
     - name: Targeting Rules and Filters
       url: feature_flags/concepts/targeting_rules
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_targeting_rules
-      weight: 303
+      weight: 304
     - name: Targeting Attributes
       url: feature_flags/concepts/targeting_attributes
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_targeting_attributes
-      weight: 304
+      weight: 305
     - name: Scheduled Rollouts
       url: feature_flags/concepts/scheduled_rollouts
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_scheduled_rollouts
-      weight: 305
+      weight: 306
     - name: Saved Filters
       url: feature_flags/concepts/saved_filters
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_saved_filters
-      weight: 306
+      weight: 307
     - name: Traffic Splitting and Randomization
       url: feature_flags/concepts/traffic_splitting
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_traffic_splitting
-      weight: 307
+      weight: 308
     - name: Distribution Channels
       url: feature_flags/concepts/distribution_channels
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_distribution_channels
-      weight: 308
+      weight: 309
     - name: Configuration Sources
       url: feature_flags/concepts/configuration_sources
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_configuration_sources
-      weight: 309
+      weight: 310
+    - name: Monthly Flag Configuration Requests
+      url: feature_flags/concepts/monthly_flag_configuration_requests
+      parent: feature_flags_concepts
+      identifier: feature_flags_concepts_mfcr
+      weight: 311
     - name: Flag History
       url: feature_flags/concepts/flag_history
       parent: feature_flags_concepts
       identifier: feature_flags_history
-      weight: 310
+      weight: 312
     - name: Feature Flag Graphs
       url: feature_flags/concepts/flag_graphs
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_flag_graphs
-      weight: 311
+      weight: 313
     - name: Stale Flags
       url: feature_flags/concepts/stale_flags
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_stale_flags
-      weight: 312
+      weight: 314
     - name: Permissions and Access Control
       url: feature_flags/concepts/permissions
       parent: feature_flags_concepts
@@ -7296,16 +7316,21 @@ menu:
       parent: observability_pipelines_packs
       identifier: observability_pipelines_packs_zscaler_zia_web_logs
       weight: 525
+    - name: Replay
+      url: observability_pipelines/replay/
+      parent: observability_pipelines
+      identifier: observability_pipelines_replay
+      weight: 6
     - name: Search Syntax
       url: observability_pipelines/search_syntax/logs/
       parent: observability_pipelines
       identifier: observability_pipelines_logs_search_syntax
-      weight: 6
+      weight: 7
     - name: Scaling and Performance
       url: observability_pipelines/scaling_and_performance/
       parent: observability_pipelines
       identifier: observability_pipelines_scaling_and_performance
-      weight: 7
+      weight: 8
     - name: Buffering and Backpressure
       url: observability_pipelines/scaling_and_performance/buffering_and_backpressure/
       parent: observability_pipelines_scaling_and_performance
@@ -7320,7 +7345,7 @@ menu:
       url: observability_pipelines/monitoring_and_troubleshooting/
       parent: observability_pipelines
       identifier: observability_pipelines_monitoring_and_troubleshooting
-      weight: 8
+      weight: 9
     - name: Worker CLI Commands
       url: observability_pipelines/monitoring_and_troubleshooting/worker_cli_commands/
       parent: observability_pipelines_monitoring_and_troubleshooting
@@ -7345,7 +7370,7 @@ menu:
       url: observability_pipelines/guide/
       parent: observability_pipelines
       identifier: observability_pipelines_guide
-      weight: 9
+      weight: 10
     - name: Upgrade Worker Guide
       url: observability_pipelines/guide/upgrade_worker/
       parent: observability_pipelines_guide
@@ -10709,6 +10734,12 @@ menu:
       url: account_management/workload_identity_federation/
       parent: account_management
       weight: 18
+    - name: Disaster Recovery
+      url: disaster_recovery/
+      pre: disaster-recovery-wui
+      identifier: disaster_recovery
+      parent: administration_heading
+      weight: 15000
     - name: Data Security
       url: data_security/
       pre: security-lock

hugo/content/en/account_management/billing/metric_name_pricing.md

@@ -13,6 +13,9 @@ further_reading:
 - link: "/metrics/guide/custom_metrics_governance/"
   tag: "Guide"
   text: "Best practices for custom metrics governance"
+- link: "https://www.datadoghq.com/blog/infinite-cardinality-metrics/"
+  tag: "Blog"
+  text: "Infinite Cardinality Metrics: Custom metrics built for modern systems"
 algolia:
   tags: ['custom metrics billing', 'metric name pricing']
 ---

hugo/content/en/account_management/personal-access-tokens.md

@@ -3,6 +3,10 @@ title: Personal Access Tokens
 description: "Create and manage short-lived, scoped Personal Access Tokens to authenticate Datadog API calls without pairing API and application keys."
 aliases:
     - /account_management/faq/personal-access-tokens/
+further_reading:
+- link: "https://www.datadoghq.com/blog/datadog-api-authentication/"
+  tag: "Blog"
+  text: "Modernize Datadog API authentication with scoped credentials"
 ---
 
 ## Overview
@@ -167,3 +171,7 @@ PATs follow an eventual consistency model. After creation or revocation, changes
 [5]: https://app.datadoghq.com/audit-trail
 [6]: /api/latest/key-management/
 [7]: /account_management/service-access-tokens/
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}

hugo/content/en/account_management/service-access-tokens.md

@@ -11,6 +11,9 @@ further_reading:
     - link: "/account_management/workload_identity_federation/"
       tag: "Documentation"
       text: "Workload Identity Federation"
+    - link: "https://www.datadoghq.com/blog/datadog-api-authentication/"
+      tag: "Blog"
+      text: "Modernize Datadog API authentication with scoped credentials"
 ---
 
 ## Overview

hugo/content/en/account_management/teams/github.md

@@ -52,7 +52,7 @@ Ensure your Datadog organization is [connected][3] to a GitHub organization. You
 
 After an admin enables team provisioning from GitHub, a notification appears on the Team detail page. The notification asks users {{< ui >}}Log in to GitHub{{< /ui >}} to connect their accounts from Datadog to GitHub through OAuth.
 
-{{< img src="account_management/teams/github/connect-to-github.png" alt="'Not Connected to GitHub' box with button to 'Log in to GitHub'" style="width:60%;">}}
+{{< img src="account_management/teams/github/connect-to-github-v2.png" alt="'Not Connected to GitHub' box with button to 'Log in to GitHub'" style="width:60%;">}}
 
 Each user must manually link their GitHub account to Datadog to establish the connection between Datadog and GitHub. This behavior is required by GitHub's OAuth and user privacy policies.
 

hugo/content/en/actions/workflows/test_and_debug.md

@@ -55,11 +55,25 @@ Clicking on a failed step gives you the inputs, outputs, and execution context f
 The initial run history for a workflow provides a panel with the list of previous workflow executions and whether each execution succeeded or failed. Failures include a link to the failed workflow step. Click on a workflow execution in the list to inspect it. You can return to the initial execution history at any time by clicking anywhere on the workflow canvas.
 
 
+## Fix a failed step with AI
+
+In {{< ui >}}Run History{{< /ui >}}, select a failed step and open its {{< ui >}}Outputs{{< /ui >}} tab. Next to the error message, click {{< ui >}}Fix with AI{{< /ui >}} to get help resolving the failure.
+
+{{< img src="actions/workflows/test_and_debug/fix-with-ai.png" alt="Bits Chat diagnosing and proposing a fix for a failed workflow step." >}}
+
+The assistant opens in [Bits Chat][7], diagnoses the failure using the step's inputs, outputs, execution context, and error message, and can search external documentation for errors returned by third-party APIs. It explains the issue and proposes a fix, then asks you to confirm before applying any change. After you confirm, the assistant updates the step's configuration and reruns validation.
+
+Fixes with AI apply to problems in the workflow's configuration, such as incorrect inputs or an outdated action setup. For failures caused by external factors, such as invalid credentials, rate limits, or an outage in a connected service, the assistant explains the root cause and suggests next steps, such as checking your credentials or contacting the owner of the connected service.
+
+If the failed step triggers another workflow, Bits Chat can trace the failure into the triggered workflow to diagnose and propose a fix there as well.
+
+
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
 <br>Do you have questions or feedback? Join the **#workflows** channel on the [Datadog Community Slack][10].
 
 [6]: /actions/workflows/expressions/
+[7]: /bits_ai/bits_chat/
 [10]: https://chat.datadoghq.com/

hugo/content/en/agent/configuration/fips-compliance.md

@@ -13,6 +13,9 @@ further_reading:
 - link: "https://www.datadoghq.com/blog/datadog-fips-enabled-agent/"
   tag: "Blog"
   text: "Monitor highly regulated workloads with Datadog's FIPS-enabled Agent"
+- link: "https://www.datadoghq.com/blog/engineering-the-datadog-agent-for-fedramp-high/"
+  tag: "Blog"
+  text: "Engineering the Datadog Agent for FedRAMP High® Certification"
 algolia:
   rank: 80
   tags: ["fips", "fips proxy", "compliance", "fedramp", "govcloud", "fips agent"]