DevKyleS · pull · Sep 1, 2026 · Sep 1, 2026 · Sep 1, 2026 · Sep 1, 2026
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -9,11 +9,11 @@ hugo/config/                           @DataDog/corpweb
 hugo/package.json                      @DataDog/corpweb
 hugo/go.mod                            @DataDog/corpweb
 hugo/go.sum                            @DataDog/corpweb
-hugo/i18n/                             @DataDog/corpweb
 hugo/archetypes/                       @DataDog/corpweb
 
 # Websites Platform
-astro/                                                       @DataDog/WebOps-Platform   
+astro/                                                       @DataDog/WebOps-Platform
+shared/                                                      @DataDog/WebOps-Platform
 hugo/babel.config.js                                         @DataDog/WebOps-Platform
 hugo/data/reference/                                         @DataDog/WebOps-Platform
 datadog-ci.preview.json                                 @DataDog/WebOps-Platform

diff --git a/.github/workflows/gif_check.yml b/.github/workflows/gif_check.yml
@@ -21,7 +21,7 @@ jobs:
     - name: Checkout code
       uses: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955 # v4.3.0
       with:
-          fetch-depth: 0
+          fetch-depth: 1
           persist-credentials: false
 
     # Branch Name Validation to be run prior to workflow

diff --git a/hugo/config/_default/config.yaml b/hugo/config/_default/config.yaml
@@ -146,7 +146,7 @@ module:
       target: assets
     - source: assets
       target: assets
-    - source: i18n
+    - source: ../shared/i18n
       target: i18n
     - source: archetypes
       target: archetypes

diff --git a/hugo/config/_default/menus/main.en.yaml b/hugo/config/_default/menus/main.en.yaml
@@ -6504,51 +6504,56 @@ menu:
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_targeting_attributes
       weight: 305
+    - name: Evaluation Tester
+      url: feature_flags/concepts/evaluation_tester
+      parent: feature_flags_concepts
+      identifier: feature_flags_concepts_evaluation_tester
+      weight: 306
     - name: Scheduled Rollouts
       url: feature_flags/concepts/scheduled_rollouts
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_scheduled_rollouts
-      weight: 306
+      weight: 307
     - name: Saved Filters
       url: feature_flags/concepts/saved_filters
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_saved_filters
-      weight: 307
+      weight: 308
     - name: Traffic Splitting and Randomization
       url: feature_flags/concepts/traffic_splitting
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_traffic_splitting
-      weight: 308
+      weight: 309
     - name: Distribution Channels
       url: feature_flags/concepts/distribution_channels
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_distribution_channels
-      weight: 309
+      weight: 310
     - name: Configuration Sources
       url: feature_flags/concepts/configuration_sources
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_configuration_sources
-      weight: 310
+      weight: 311
     - name: Monthly Flag Configuration Requests
       url: feature_flags/concepts/monthly_flag_configuration_requests
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_mfcr
-      weight: 311
+      weight: 312
     - name: Flag History
       url: feature_flags/concepts/flag_history
       parent: feature_flags_concepts
       identifier: feature_flags_history
-      weight: 312
+      weight: 313
     - name: Feature Flag Graphs
       url: feature_flags/concepts/flag_graphs
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_flag_graphs
-      weight: 313
+      weight: 314
     - name: Stale Flags
       url: feature_flags/concepts/stale_flags
       parent: feature_flags_concepts
       identifier: feature_flags_concepts_stale_flags
-      weight: 314
+      weight: 315
     - name: Permissions and Access Control
       url: feature_flags/concepts/permissions
       parent: feature_flags_concepts

diff --git a/hugo/config/_default/menus/partners.en.yaml b/hugo/config/_default/menus/partners.en.yaml
@@ -37,5 +37,39 @@ menu:
       identifier: cloud-cost-management-aws
       parent: cloud-cost-management
       weight: 50
+    - name: Multi-Tenant Usage Metering and Billing
+      url: /partners/multi_tenant_billing/
+      identifier: multi-tenant-billing
+      weight: 4
+    - name: Onboarding a New Customer
+      url: /partners/multi_tenant_billing/customer-onboarding/
+      identifier: multi-tenant-billing-customer-onboarding
+      parent: multi-tenant-billing
+      weight: 10
+    - name: Trial Org Provisioning
+      url: /partners/multi_tenant_billing/trial-org-provisioning/
+      identifier: multi-tenant-billing-trial-org-provisioning
+      parent: multi-tenant-billing
+      weight: 20
+    - name: Cost and Usage Visibility
+      url: /partners/multi_tenant_billing/cost-and-usage-visibility/
+      identifier: multi-tenant-billing-cost-and-usage-visibility
+      parent: multi-tenant-billing
+      weight: 30
+    - name: Centralized Usage Metrics
+      url: /partners/multi_tenant_billing/centralized-usage-metrics/
+      identifier: multi-tenant-billing-centralized-usage-metrics
+      parent: multi-tenant-billing
+      weight: 40
+    - name: Customer Contracts
+      url: /partners/multi_tenant_billing/customer-contracts-management/
+      identifier: multi-tenant-billing-customer-contracts-management
+      parent: multi-tenant-billing
+      weight: 50
+    - name: Troubleshooting
+      url: /partners/multi_tenant_billing/troubleshooting/
+      identifier: multi-tenant-billing-troubleshooting
+      parent: multi-tenant-billing
+      weight: 70
 
 
diff --git a/hugo/content/en/account_management/billing/apm_tracing_profiler.md b/hugo/content/en/account_management/billing/apm_tracing_profiler.md
@@ -127,6 +127,29 @@ An AWS-Lambda based serverless application being invoked 10 million times in a m
 | Indexed Spans                  | 10 million | 150,000 Indexed Spans included with each 1 million Lambda invocations. $1.70 per million additional Indexed Spans | 8.5 * $1.70 | $14.45               |
 | Total                          |            |                                                                             | $50 + $14.45 | **$64.45 per month** |
 
+## APM Edge Devices
+
+APM Edge Devices is a billing option for monitoring Edge and IoT devices with APM, such as point-of-sale (POS) systems, medical devices, autonomous vehicles, and industrial systems. APM Edge Devices is the same APM product as standard APM billing, with a billing model designed for Edge and IoT device fleets. For pricing, contact [Sales][8] or your [Customer Success Manager][9].
+
+APM Edge Devices requires the standard Datadog Agent version 7.75.0 or later. The [Datadog IoT Agent][17] does not support APM.
+
+To identify a device as an APM Edge Device, configure the Datadog Agent to run in APM Edge mode with one of the following methods:
+
+- Set the `DD_APM_MODE` environment variable to `edge`:
+
+  ```shell
+  DD_APM_MODE=edge
+  ```
+
+- Add the following to the Agent's `datadog.yaml` configuration file:
+
+  ```yaml
+  apm_config:
+    mode: edge
+  ```
+
+**Note**: APM Edge Devices does not support OpenTelemetry. Contact [Sales][8] or your [Customer Success Manager][9] if your Edge or IoT devices require OpenTelemetry instrumentation.
+
 ## FAQ
 
 **1. What is classified as an APM host for billing?**
@@ -194,3 +217,4 @@ Yes. Let Datadog know if you are interested in buying Data Streams Monitoring wi
 [14]: /tracing/trace_pipeline/metrics
 [15]: /universal_service_monitoring/
 [16]: https://www.datadoghq.com/pricing/?product=serverless-monitoring&tab=aws-fargate#products
+[17]: /agent/iot/
diff --git a/hugo/content/en/account_management/billing/metric_name_pricing.md b/hugo/content/en/account_management/billing/metric_name_pricing.md
@@ -42,7 +42,7 @@ These SKUs are mutually incompatible with the Timeseries (cardinality) pricing S
 
 ## Pricing structure
 
-Both metric names and indexed datapoints are priced with marginal, volume-based discounting across 15 tiers. Higher-volume tiers have lower per-unit rates. As your usage increases, the portion that crosses into each higher tier is billed at that tier's rate. Previously billed usage is never repriced.
+Both metric names and indexed datapoints are priced with marginal, volume-based discounting across 5 tiers. Higher-volume tiers have lower per-unit rates. As your usage increases, the portion that crosses into each higher tier is billed at that tier's rate. Previously billed usage is never repriced.
 
 {{< img src="account_management/billing/metric_name_pricing/marginal-pricing-tiers.png" alt="Diagram illustrating how marginal pricing works, simplified to five volume tiers. Each tier has a per-unit rate, visualized as a bar height; higher-volume tiers (right side) have progressively shorter bars, indicating lower per-unit rates than lower-volume tiers (left side)." style="width:100%;" >}}
 
@@ -117,7 +117,7 @@ A Distribution metric that submits 100 datapoints with default aggregations is b
 
 You can commit to a usage volume independently for metric names and for datapoints. Each commitment is priced at the marginal pricing tier the committed volume falls into. The full committed volume is billed at that tier's rate, and marginal discounting does not apply within the committed range. Usage above the committed amount follows the standard marginal schedule, starting at the tier boundary immediately above the committed volume.
 
-For example, if you commit to 15,000 metric names that fall within Tier 6, all 15,000 are billed at the Tier 6 rate. If your actual usage reaches 75,000 metric names, the additional 60,000 follow the marginal schedule from Tier 6 through Tier 8.
+For example, if you commit to 15,000 metric names that fall within Tier 3, all 15,000 are billed at the Tier 3 rate. If your actual usage reaches 150,000 metric names, the additional 135,000 follow the marginal schedule from Tier 3 through Tier 4.
 
 ## Usage Attribution
 

diff --git a/hugo/content/en/agent/fleet_automation/fleet_view.md b/hugo/content/en/agent/fleet_automation/fleet_view.md
@@ -122,10 +122,28 @@ Most Kubernetes view features are available without version requirements. Specif
 | View `DatadogAgent` configuration | Datadog Operator v1.24 or later |
 | View Helm Chart values | Datadog Helm Chart v3.157.0 or later |
 | Edit configuration | [Remote Configuration][6] enabled and Datadog Operator v1.27 or later |
+| Edit configuration without setting a cluster name | Datadog Operator v1.30.0 or later |
 | View integrations on a Cluster Agent | Agent v7.72.0 or later |
 | View integration status on a Cluster Agent | Agent v7.79.0 or later |
 
-To edit configuration from Fleet View, also set the following flags in your [Operator configuration][7]: `remoteConfigEnabled`, `remoteUpdatesEnabled`, and `createControllerRevisions`. Editing Helm Chart values from Fleet View is not supported.
+To edit configuration from Fleet View, set the following flags in your [Operator configuration][7]: `remoteConfigEnabled`, `remoteUpdatesEnabled`, and `createControllerRevisions`. Editing also requires a Datadog API key and application key to be configured. Editing Helm Chart values from Fleet View is not supported.
+
+On Datadog Operator versions earlier than v1.30.0, you must also set a cluster name (`clusterName`), otherwise the {{< ui >}}Edit{{< /ui >}} button remains disabled. As of Datadog Operator v1.30.0, a cluster name is optional.
+
+If you install the Datadog Operator with its Helm chart, you can enable the required flags together using the `previewFleetRollouts` value:
+
+{{< code-block lang="shell" >}}
+helm repo add datadog https://helm.datadoghq.com
+helm repo update
+
+helm upgrade --install datadog-operator datadog/datadog-operator \
+  --set previewFleetRollouts=true \
+  --set apiKeyExistingSecret=datadog-secret \
+  --set appKeyExistingSecret=datadog-secret \
+  --devel
+{{< /code-block >}}
+
+Replace `datadog-secret` with the name of the Kubernetes Secret that holds your Datadog API and application keys. The `--devel` flag installs the latest development release of the chart.
 
 ### View Kubernetes clusters
 

diff --git a/hugo/content/en/data_observability/_index.md b/hugo/content/en/data_observability/_index.md
@@ -8,6 +8,9 @@ further_reading:
  - link: "https://www.datadoghq.com/blog/datadog-google-cloud-ai-stack/"
    tag: "Blog"
    text: "Evaluate, optimize, and secure your Google Cloud AI stack with Datadog"
+ - link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
+   tag: "Blog"
+   text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"
 ---
 
 ## Overview

diff --git a/hugo/content/en/data_security/guide/tls_ciphers_deprecation.md b/hugo/content/en/data_security/guide/tls_ciphers_deprecation.md
@@ -20,7 +20,7 @@ To test your client's cipher suite compatibility, connect to [tls-config-test.da
 
 {{< site-region region="us,eu,us3,us5,ap1,ap2,uk1" >}}
 
-Effective September 1, 2026, Datadog will accept only the following cipher suites:
+As of September 1, 2026, Datadog accepts only the following cipher suites:
 
 | Code         | IANA Name                                         |
 |--------------|---------------------------------------------------|
@@ -59,7 +59,7 @@ Datadog has disabled support for the following cipher suites, which are consider
 
 ### Effective September 1, 2026
 
-Beginning **September 1, 2026**, Datadog will disable support for the following cipher suites:
+As of **September 1, 2026**, Datadog does not support the following cipher suites:
 
 | Code         | IANA Name                                  | OpenSSL Name             |
 |--------------|--------------------------------------------|--------------------------|

diff --git a/hugo/content/en/data_streams/_index.md b/hugo/content/en/data_streams/_index.md
@@ -14,6 +14,9 @@ further_reading:
     - link: '/internal_developer_portal/catalog/'
       tag: 'Documentation'
       text: 'Catalog'
+    - link: "https://learn.datadoghq.com/courses/monitor-a-kafka-pipeline-with-dsm"
+      tag: "Learning Center"
+      text: "Monitor a Kafka Pipeline with Data Streams Monitoring"
     - link: 'https://www.datadoghq.com/blog/data-streams-monitoring/'
       tag: 'Blog'
       text: 'Track and improve the performance of streaming data pipelines with Datadog Data Streams Monitoring'
@@ -29,9 +32,9 @@ further_reading:
     - link: "https://www.datadoghq.com/blog/data-observability/"
       tag: "Blog"
       text: "Ensure trust across the entire data life cycle with Datadog Data Observability"
-    - link: "https://learn.datadoghq.com/courses/monitor-a-kafka-pipeline-with-dsm"
-      tag: "Learning Center"
-      text: "Monitor a Kafka Pipeline with Data Streams Monitoring"
+    - link: "https://www.datadoghq.com/blog/data-pipeline-monitoring/"
+      tag: "Blog"
+      text: "Data pipeline monitoring 101: Tracking health and performance across the data stack"
 cascade:
     algolia:
         rank: 70

diff --git a/hugo/content/en/database_monitoring/_index.md b/hugo/content/en/database_monitoring/_index.md
@@ -8,12 +8,12 @@ further_reading:
 - link: "/database_monitoring/troubleshooting/"
   tag: "Documentation"
   text: "Troubleshooting"
-- link: "https://dtdg.co/fe"
-  tag: "Foundation Enablement"
-  text: "Join an interactive session to level up your Database Monitoring"
 - link: "https://learn.datadoghq.com/courses/database-monitoring"
   tag: "Learning Center"
   text: "Monitoring a Postgres Database with Datadog DBM"
+- link: "https://dtdg.co/fe"
+  tag: "Foundation Enablement"
+  text: "Join an interactive session to level up your Database Monitoring"
 - link: "https://www.datadoghq.com/blog/map-postgresql-explain-plan-nodes-to-sql-with-datadog/"
   tag: "Blog"
   text: "Diagnose slow PostgreSQL queries faster with explain plan correlation"

diff --git a/hugo/content/en/experiments/concepts/cumulative_impact.md b/hugo/content/en/experiments/concepts/cumulative_impact.md
@@ -15,6 +15,9 @@ further_reading:
 - link: "/experiments/statistics/analysis_methods"
   tag: "Documentation"
   text: "Analysis Methods"
+- link: "https://www.datadoghq.com/blog/two-ways-to-measure-cumulative-impact/"
+  tag: "Blog"
+  text: "Two ways to measure the cumulative impact of experiments"
 ---
 
 ## Overview

diff --git a/hugo/content/en/experiments/statistics/analysis_methods.md b/hugo/content/en/experiments/statistics/analysis_methods.md
@@ -20,6 +20,9 @@ further_reading:
 - link: "/experiments/statistics/multiple_testing_correction"
   tag: "Documentation"
   text: "Multiple Testing Correction"
+- link: "https://www.datadoghq.com/blog/two-ways-to-measure-cumulative-impact/"
+  tag: "Blog"
+  text: "Two ways to measure the cumulative impact of experiments"
 ---
 
 ## Overview

diff --git a/hugo/content/en/feature_flags/concepts/_index.md b/hugo/content/en/feature_flags/concepts/_index.md
@@ -11,6 +11,7 @@ Learn how Datadog Feature Flags work and how to configure flags, environments, t
     {{< nextlink href="/feature_flags/concepts/evaluation_context" >}}Evaluation Context{{< /nextlink >}}
     {{< nextlink href="/feature_flags/concepts/targeting_rules" >}}Targeting Rules and Filters{{< /nextlink >}}
     {{< nextlink href="/feature_flags/concepts/targeting_attributes" >}}Targeting Attributes{{< /nextlink >}}
+    {{< nextlink href="/feature_flags/concepts/evaluation_tester" >}}Evaluation Tester{{< /nextlink >}}
     {{< nextlink href="/feature_flags/concepts/scheduled_rollouts" >}}Scheduled Rollouts{{< /nextlink >}}
     {{< nextlink href="/feature_flags/concepts/saved_filters" >}}Saved Filters{{< /nextlink >}}
     {{< nextlink href="/feature_flags/concepts/traffic_splitting" >}}Traffic Splitting and Randomization{{< /nextlink >}}