Merge branch 'master' into mtullalizardi-patch-1

Author: mtullalizardi

content/en/agent/faq/_index.md

@@ -27,6 +27,6 @@ aliases:
     {{< nextlink href="agent/faq/docker-hub" >}}Docker Hub{{< /nextlink >}}
     {{< nextlink href="agent/faq/proxy_example_haproxy" >}}Send traffix to Datadog using HAProxy{{< /nextlink >}}
     {{< nextlink href="agent/faq/proxy_example_nginx" >}}Send traffix to Datadog using NGINX{{< /nextlink >}}
-    {{< nextlink href="agent/faq/fips_proxy" >}}Agent FIPS proxy (deprecated){{< /nextlink >}}
+    {{< nextlink href="agent/faq/fips_proxy" >}}Agent FIPS proxy{{< /nextlink >}}
 
 {{< /whatsnext >}}

content/en/cloud_cost_management/tag_pipelines.md

@@ -22,13 +22,15 @@ Tag pipelines are applied to Cloud Cost metrics from all providers. Tag pipeline
 
 ## Create a ruleset
 
+To create a ruleset, navigate to [**Cloud Cost > Settings > Tag Pipelines**][1].
+
 <div class="alert alert-warning"> You can create up to 100 rules. API-based Reference Tables are not supported. </div>
 
 Before creating individual rules, create a ruleset (a folder for your rules) by clicking **+ New Ruleset**.
 
 Within each ruleset, click **+ Add New Rule** and select a rule type: **Add tag**, **Alias tag keys**, or **Map multiple tags**. These rules execute in a sequential, deterministic order from top to bottom.
 
-{{< img src="cloud_cost/tags_order.png" alt="A list of tag rules on the Tag Pipelines page displaying various categories such as team, account, service, department, business unit, and more" style="width:80%;" >}}
+{{< img src="cloud_cost/pipelines-create-ruleset.png" alt="A list of tag rules on the Tag Pipelines page displaying various categories such as team, account, service, department, business unit, and more" style="width:60%;" >}}
 
 You can organize rules and rulesets to ensure the order of execution matches your business logic.
 
@@ -38,32 +40,40 @@ Add a new tag (key + value) based on the presence of existing tags on your Cloud
 
 For example, you can create a rule to tag all resources with their business unit based on the services those resources are a part of.
 
-{{< img src="cloud_cost/tags_addnew.png" alt="Add new business unit tag to resources with service:processing, service:creditcard, or service:payment-notification." style="width:60%;" >}}
+{{< img src="cloud_cost/pipelines-add-tag.png" alt="Add new business unit tag to resources with service:process-agent or service:process-billing." style="width:60%;" >}}
+
+Under the **Additional options** section, you have the following options:
 
-To ensure the rule only applies if the `business_unit` tag doesn't already exist, click the toggle in the **Additional options** section.
+- **Only apply if tag `{tag}` doesn't exist** - Ensures the rule only applies if the specified tag (`business-unit` in the example above) doesn't already exist.
+- **Apply case-insensitive matching to resource tags** - Enables tags defined in the `To resources with tag(s)` field and tags from the cost data to be case insensitive. For example, if resource tags from the UI is: `foo:bar` and the tag from the cost data is `Foo:bar`, then the two can be matched.
 
 ### Alias tag keys
 
 Map existing tag values to a more standardized tag.
 
 For example, if your organization wants to use the standard `application` tag key, but several teams have a variation of that tag (like `app`, `webapp`, or `apps`), you can alias `apps` to `application`. Each alias tag rule allows you to alias a maximum of 25 tag keys to a new tag.
 
-{{< img src="cloud_cost/tags_alias.png" alt="Add application tag to resources with app, webapp, or apps tag." style="width:60%;" >}}
+{{< img src="cloud_cost/pipelines-alias-tag.png" alt="Add application tag to resources with app, webapp, or apps tag." style="width:60%;" >}}
 
 Add the application tag to resources with `app`, `webapp`, or `apps` tags. The rule stops executing for each resource after a first match is found. For example, if a resource already has a `app` tag, then the rule no longer attempts to identify a `webapp` or `apps` tag.
 
 To ensure the rule only applies if the `application` tag doesn't already exist, click the toggle in the **Additional options** section.
 
 ### Map multiple tags
 
-Use [Reference Tables][2] to add multiple tags to cost data without creating multiple rules. This will map the values from your Reference Table's primary key column to values from cost tags. If found, the pipelines adds the selected Reference Table columns as tags to cost data.
+Use [Reference Tables][2] to add multiple tags to cost data without creating multiple rules. This maps the values from your Reference Table's primary key column to values from cost tags. If found, the pipelines adds the selected Reference Table columns as tags to cost data.
 
 For example, if you want to add information about which VPs, organizations, and business_units different AWS and Azure accounts fall under, you can create a table and map the tags.
 
-{{< img src="cloud_cost/tags_mapmultiple.png" alt="Add account metadata like vp, organization, and businessunit using reference tables for tag pipelines" style="width:60%;" >}}
+{{< img src="cloud_cost/pipelines-map-multiple-tags.png" alt="Add account metadata like customer_name using reference tables for tag pipelines" style="width:60%;" >}}
 
 Similar to [Alias tag keys](#alias-tag-keys), the rule stops executing for each resource after a first match is found. For example, if an `aws_member_account_id` is found, then the rule no longer attempts to find a `subscriptionid`.
 
+Under the **Additional options** section, you have the following options:
+
+- **Only apply if columns don't exist** - Ensures the defined columns are only added if they do not already exist with the associated tags from the cost data.
+- **Apply case-insensitive matching for primary key values** - Enables case-insensitive matching between the primary key value from the reference table and the value of the tag in the cost data where the tag key matches the primary key. For example, if the primary key value pair from UI is: foo:Bar and the tag from the cost data is foo:bar, then the two can be matched.
+
 ## Reserved tags
 
 Certain tags such as `env` and `host` are [reserved tags][4], and are part of [Unified Service Tagging][3]. The `host` tag cannot be added in Tag Pipelines.

content/en/dora_metrics/_index.md

@@ -29,7 +29,6 @@ further_reading:
 <div class="alert alert-warning">DORA Metrics is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
-<div class="alert alert-warning">DORA Metrics is in Preview.</div>
 
 ## Overview
 
@@ -38,7 +37,7 @@ DevOps Research and Assessment (DORA) metrics are [four key metrics][1] that ind
 Deployment frequency
 : How often an organization successfully releases to production.
 
-Lead time for changes
+Change lead time
 : The amount of time it takes a commit to get into production.
 
 Change failure rate

content/en/dora_metrics/data_collected/_index.md

@@ -19,7 +19,6 @@ further_reading:
 <div class="alert alert-warning">DORA Metrics is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
-<div class="alert alert-warning">DORA Metrics is in Preview.</div>
 
 ## Overview
 

content/en/dora_metrics/setup/_index.md

@@ -12,7 +12,6 @@ further_reading:
 <div class="alert alert-warning">DORA Metrics is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
-<div class="alert alert-warning">DORA Metrics is in Preview.</div>
 
 ## Overview
 

content/en/dora_metrics/setup/deployments.md

@@ -26,7 +26,6 @@ further_reading:
 <div class="alert alert-warning">DORA Metrics is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
-<div class="alert alert-warning">DORA Metrics is in Preview.</div>
 
 ## Overview
 

content/en/dora_metrics/setup/failures.md

@@ -30,11 +30,10 @@ further_reading:
 <div class="alert alert-warning">DORA Metrics is not available in the selected site ({{< region-param key="dd_site_name" >}}) at this time.</div>
 {{< /site-region >}}
 
-<div class="alert alert-warning">DORA Metrics is in Preview.</div>
 
 ## Overview
 
-Failed deployment events, currently interpreted through failure events, are used to compute [change failure rate](#calculating-change-failure-rate) and [time to restore](#calculating-time-to-restore). 
+Failure events are used to compute [change failure rate](#calculating-change-failure-rate) and [time to restore](#calculating-time-to-restore). 
 
 ## Selecting and configuring a failure data source
 

content/en/integrations/guide/source-code-integration.md

@@ -225,9 +225,7 @@ If you are using a host, you have two options: using Microsoft SourceLink or con
   The Node.js client library version 3.21.0 or later is required.
   </br>
   </br>
-  Displaying code links and snippets for TypeScript applications requires your Node application to be run with: 
-  </br>
-  <a href="https://nodejs.org/dist/v12.22.12/docs/api/cli.html#cli_enable_source_maps"><code>--enable-source-maps</code></a>.
+  For transpiled Node.js applications (for example, TypeScript), make sure to generate and publish source maps with the deployed application, and to run Node.js with the <a href="https://nodejs.org/docs/latest/api/cli.html#--enable-source-maps"><code>--enable-source-maps</code></a> flag. Otherwise, code links and snippets will not work.
 </div>
 
 #### Containers

content/en/logs/explorer/search.md

@@ -19,9 +19,9 @@ further_reading:
 
 The [Logs Explorer][5] lets you search and view individual logs as a list. However, the most valuable insights often come from aggregating logs at scale. Using the search feature, you can filter logs and visualize them as timeseries charts, top lists, tree maps, pie charts, or tables to better understand trends, patterns, and outliers across your log data.
 
-## Natural language query
+## Natural language queries
 
-<div class="alert alert-info">Natural language queries for Logs is in Preview. To access this feature, request through <a href="https://www.datadoghq.com/product-preview/natural-language-queries-for-logs/">this form</a>.</div>
+<div class="alert alert-info"><strong>Built with Llama</strong>, Natural Language Queries (NLQ) for Logs is in Preview. To access this feature, request through <a href="https://www.datadoghq.com/product-preview/natural-language-queries-for-logs/">this form</a>.</div>
 
 Use Natural Language Queries (NLQ) to describe what you're looking for in plain English. Datadog automatically translates your request into a structured log query, making it easier to explore logs without needing to write complex syntax. To access this feature, click **Ask** in the search field.
 

content/en/logs/workspaces/_index.md

@@ -7,10 +7,6 @@ further_reading:
   text: "Take enhanced control of your log data with Datadog Log Workspaces"
 ---
 
-{{< callout url="https://www.datadoghq.com/private-beta/log-workspaces/" header="Access the Preview!" >}}
-  Log Workspaces is in Preview.
-{{< /callout >}}
-
 ## Overview
 During an incident investigation, you might need to run complex queries, such as combining attributes from multiple log sources or transforming log data, to analyze your logs. Use Log Workspaces to run queries to:
 

content/en/monitors/guide/alert_aggregation.md

@@ -76,7 +76,7 @@ If you are managing your monitors with the API, use the variable `notify_by` to
 
 | Type of Alert     | Configuration Example                  |
 |-------------------|----------------------------------------|
-| Simple Alert      | `"notify_by": [*]`                     |
+| Simple Alert      | `"notify_by": ["*"]`                     |
 | Multi Alert       | `"notify_by": [<group>]`, for example, `"notify_by": ["topic"]` |
 
 For more information, see the [API documentation][4].
@@ -88,4 +88,4 @@ For more information, see the [API documentation][4].
 [1]: /monitors/configuration/?tab=thresholdalert#simple-alert
 [2]: /monitors/notify/variables/?tab=is_alert#triggered-variables
 [3]: /monitors/configuration/?tab=thresholdalert#multi-alert
-[4]: /api/latest/monitors/#create-a-monitor
+[4]: /api/latest/monitors/#create-a-monitor

content/en/network_monitoring/cloud_network_monitoring/setup.md

@@ -90,7 +90,7 @@ Cloud Network Monitoring supports use of the following provisioning systems:
 
 ## Setup
 
-Given this tool's focus and strength is in analyzing traffic _between_ network endpoints and mapping network dependencies, it is recommended to install it on a meaningful subset of your infrastructure and a **_minimum of 2 hosts_** to maximize value.
+Cloud Network Monitoring is designed to analyze traffic _between_ network endpoints and map network dependencies. Datadog recommends installing CNM on a meaningful subset of your infrastructure and a **_minimum of 2 hosts_** to maximize value.
 
 {{< tabs >}}
 {{% tab "Agent (Linux)" %}}
@@ -395,11 +395,10 @@ If you already have the [Agent running with a manifest][4]:
 [5]: https://github.com/DataDog/helm-charts/blob/main/charts/datadog/values.yaml#L1519-L1523
 {{% /tab %}}
 {{% tab "Operator" %}}
-<div class="alert alert-warning">The Datadog Operator is Generally Available with the `1.0.0` version, and it reconciles the version `v2alpha1` of the DatadogAgent Custom Resource. </div>
 
-[The Datadog Operator][1] is a way to deploy the Datadog Agent on Kubernetes and OpenShift. It reports deployment status, health, and errors in its Custom Resource status, and it limits the risk of misconfiguration thanks to higher-level configuration options.
+[The Datadog Operator][1] simplifies deploying the Datadog Agent on Kubernetes and OpenShift. It provides deployment status, health, and error reporting through its Custom Resource status, while reducing the risk of misconfiguration with higher-level configuration options.
 
-To enable Cloud Network Monitoring in Operator, use the following configuration:
+To enable Cloud Network Monitoring on the Datadog Operator, use the following configuration:
 
 ```yaml
 apiVersion: datadoghq.com/v2alpha1
@@ -412,7 +411,7 @@ spec:
       enabled: true
 ```
 
-[1]: https://github.com/DataDog/datadog-operator
+[1]: /containers/datadog_operator 
 {{% /tab %}}
 {{% tab "Docker" %}}
 
@@ -474,10 +473,55 @@ services:
 [1]: https://app.datadoghq.com/organization-settings/api-keys
 {{% /tab %}}
 {{% tab "ECS" %}}
-To set up on Amazon ECS, see the [Amazon ECS][1] documentation page.
+To set up CNM on Amazon ECS, see the [Amazon ECS][1] documentation page.
 
 
 [1]: /agent/amazon_ecs/#network-performance-monitoring-collection-linux-only
+{{% /tab %}}
+
+{{% tab "ECS Fargate" %}}
+
+<div class="alert alert-info">ECS Fargate for CNM is in Preview. Reach out to your Datadog representative to sign up.</div>
+
+To enable Cloud Network Monitoring on ECS Fargate, use the following instructions:
+
+**Requires Agent version `7.58` or higher**.
+
+- For a new Fargate deployment, configure the Datadog Agent to monitor Fargate on ECS by enabling [process collection][1] on your Fargate hosts.
+
+- For existing deployments, update your `task.json` file to include the following configuration settings:
+
+```json
+{
+ "containerDefinitions": [
+   (...)
+     "environment": [
+       (...)
+       {
+         "name": "DD_SYSTEM_PROBE_NETWORK_ENABLED",
+         "value": "true"
+       },
+       {
+          "name": "DD_NETWORK_CONFIG_ENABLE_EBPFLESS",
+          "value": "true"
+       },
+       {
+          "name": "DD_PROCESS_AGENT_ENABLED",
+          "value": "true"
+       }      
+     ],
+     "linuxParameters": {
+      "capabilities": {
+        "add": [
+          "SYS_PTRACE"
+        ]
+      }
+    },
+ ],
+}
+```
+[1]: /integrations/ecs_fargate/?tab=webui#process-collection 
+
 {{% /tab %}}
 {{< /tabs >}}
 

content/en/observability_pipelines/set_up_pipelines/archive_logs/amazon_data_firehose.md

@@ -407,19 +407,9 @@ For the Datadog Archives destination, follow the instructions for the cloud prov
 {{% observability_pipelines/install_worker/docker %}}
 
 {{% /tab %}}
-{{% tab "Amazon EKS" %}}
-
-{{% observability_pipelines/install_worker/amazon_eks %}}
-
-{{% /tab %}}
-{{% tab "Azure AKS" %}}
-
-{{% observability_pipelines/install_worker/azure_aks %}}
-
-{{% /tab %}}
-{{% tab "Google GKE" %}}
+{{% tab "Kubernetes" %}}
 
-{{% observability_pipelines/install_worker/google_gke %}}
+{{% observability_pipelines/install_worker/kubernetes %}}
 
 {{% /tab %}}
 {{% tab "Linux (APT)" %}}

content/en/observability_pipelines/set_up_pipelines/archive_logs/amazon_s3.md

@@ -406,19 +406,9 @@ For the Datadog Archives destination, follow the instructions for the cloud prov
 {{% observability_pipelines/install_worker/docker %}}
 
 {{% /tab %}}
-{{% tab "Amazon EKS" %}}
-
-{{% observability_pipelines/install_worker/amazon_eks %}}
-
-{{% /tab %}}
-{{% tab "Azure AKS" %}}
-
-{{% observability_pipelines/install_worker/azure_aks %}}
-
-{{% /tab %}}
-{{% tab "Google GKE" %}}
+{{% tab "Kubernetes" %}}
 
-{{% observability_pipelines/install_worker/google_gke %}}
+{{% observability_pipelines/install_worker/kubernetes %}}
 
 {{% /tab %}}
 {{% tab "Linux (APT)" %}}

content/en/observability_pipelines/set_up_pipelines/archive_logs/kafka.md

@@ -410,19 +410,9 @@ For the Datadog Archives destination, follow the instructions for the cloud prov
 {{% observability_pipelines/install_worker/docker %}}
 
 {{% /tab %}}
-{{% tab "Amazon EKS" %}}
-
-{{% observability_pipelines/install_worker/amazon_eks %}}
-
-{{% /tab %}}
-{{% tab "Azure AKS" %}}
-
-{{% observability_pipelines/install_worker/azure_aks %}}
-
-{{% /tab %}}
-{{% tab "Google GKE" %}}
+{{% tab "Kubernetes" %}}
 
-{{% observability_pipelines/install_worker/google_gke %}}
+{{% observability_pipelines/install_worker/kubernetes %}}
 
 {{% /tab %}}
 {{% tab "Linux (APT)" %}}

content/en/observability_pipelines/set_up_pipelines/dual_ship_logs/amazon_data_firehose.md

@@ -360,19 +360,9 @@ For the Datadog Archives destination, follow the instructions for the cloud prov
 {{% observability_pipelines/install_worker/docker %}}
 
 {{% /tab %}}
-{{% tab "Amazon EKS" %}}
+{{% tab "Kubernetes" %}}
 
-{{% observability_pipelines/install_worker/amazon_eks %}}
-
-{{% /tab %}}
-{{% tab "Azure AKS" %}}
-
-{{% observability_pipelines/install_worker/azure_aks %}}
-
-{{% /tab %}}
-{{% tab "Google GKE" %}}
-
-{{% observability_pipelines/install_worker/google_gke %}}
+{{% observability_pipelines/install_worker/kubernetes %}}
 
 {{% /tab %}}
 {{% tab "Linux (APT)" %}}

content/en/observability_pipelines/set_up_pipelines/dual_ship_logs/amazon_s3.md

@@ -358,19 +358,9 @@ For the Datadog Archives destination, follow the instructions for the cloud prov
 {{% observability_pipelines/install_worker/docker %}}
 
 {{% /tab %}}
-{{% tab "Amazon EKS" %}}
+{{% tab "Kubernetes" %}}
 
-{{% observability_pipelines/install_worker/amazon_eks %}}
-
-{{% /tab %}}
-{{% tab "Azure AKS" %}}
-
-{{% observability_pipelines/install_worker/azure_aks %}}
-
-{{% /tab %}}
-{{% tab "Google GKE" %}}
-
-{{% observability_pipelines/install_worker/google_gke %}}
+{{% observability_pipelines/install_worker/kubernetes %}}
 
 {{% /tab %}}
 {{% tab "Linux (APT)" %}}

content/en/observability_pipelines/set_up_pipelines/dual_ship_logs/kafka.md

@@ -362,19 +362,9 @@ For the Datadog Archives destination, follow the instructions for the cloud prov
 {{% observability_pipelines/install_worker/docker %}}
 
 {{% /tab %}}
-{{% tab "Amazon EKS" %}}
+{{% tab "Kubernetes" %}}
 
-{{% observability_pipelines/install_worker/amazon_eks %}}
-
-{{% /tab %}}
-{{% tab "Azure AKS" %}}
-
-{{% observability_pipelines/install_worker/azure_aks %}}
-
-{{% /tab %}}
-{{% tab "Google GKE" %}}
-
-{{% observability_pipelines/install_worker/google_gke %}}
+{{% observability_pipelines/install_worker/kubernetes %}}
 
 {{% /tab %}}
 {{% tab "Linux (APT)" %}}