Merge branch 'master' into sarah.stonehill/code-origin-new-doc

Author: tylfin

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-17 17:24:31.482433",
-            "spec_repo_commit": "c23f4c4f"
+            "regenerated": "2025-04-22 18:30:05.951046",
+            "spec_repo_commit": "2b6fa951"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-17 17:24:40.087890",
-            "spec_repo_commit": "c23f4c4f"
+            "regenerated": "2025-04-22 18:30:14.967308",
+            "spec_repo_commit": "2b6fa951"
         }
     }
 }

assets/styles/components/_integrations.scss

@@ -36,6 +36,7 @@ $screen-md-max: ($screen-lg-min - 1) !default;
   }
 
   table {
+    table-layout: fixed;
     tr {
         th:empty {
             display: none;

config/_default/menus/main.en.yaml

@@ -3172,11 +3172,16 @@ menu:
       parent: serverless_step_functions
       identifier: serverless_step_functions_redrive
       weight: 204
+    - name: Distributed Map States
+      url: serverless/step_functions/distributed-maps
+      parent: serverless_step_functions
+      identifier: serverless_step_functions_distributed_maps
+      weight: 205
     - name: Troubleshooting
       url: serverless/step_functions/troubleshooting
       parent: serverless_step_functions
       identifier: serverless_step_functions_troubleshooting
-      weight: 205
+      weight: 206
     - name: AWS Fargate
       identifier: serverless_aws_fargate
       url: integrations/ecs_fargate
@@ -6783,16 +6788,21 @@ menu:
       parent: synthetics_mobile_app_testing
       identifier: synthetics_mobile_app_testing_mobile_app_tests_advanced_options
       weight: 403
+    - name: Supported Devices
+      url: synthetics/mobile_app_testing/devices/
+      parent: synthetics_mobile_app_testing
+      identifier: synthetics_mobile_app_testing_devices
+      weight: 404
     - name: Restricted Networks
       url: synthetics/mobile_app_testing/mobile_app_tests/restricted_networks
       parent: synthetics_mobile_app_testing
       identifier: synthetics_mobile_app_testing_restricted_networks
-      weight: 404
+      weight: 405
     - name: Settings
       url: synthetics/mobile_app_testing/settings
       parent: synthetics_mobile_app_testing
       identifier: synthetics_mobile_app_testing_settings
-      weight: 405
+      weight: 406
     - name: Platform
       url: synthetics/platform/
       parent: synthetics
@@ -7987,15 +7997,19 @@ menu:
       url: account_management/billing/
       parent: account_management
       weight: 12
+    - name: Pricing
+      url: account_management/billing/pricing
+      parent: account_management_billing
+      weight: 1201
     - name: Product Allotments
       url: account_management/billing/product_allotments
       parent: account_management_billing
-      weight: 5
+      weight: 1202
     - name: Containers
       identifier: account_management_billing_containers
       url: account_management/billing/containers
       parent: account_management_billing
-      weight: 6
+      weight: 1203
     - name: Multi-org Accounts
       identifier: account_management_multi_org_accounts
       url: account_management/multi_organization/

config/_default/params.yaml

@@ -119,8 +119,6 @@ code_language_ids:
     otel: "OpenTelemetry API"
     status_legacy: "Status Page (Legacy)"
     status_page: "Status Page"
-    notebooks_legacy: "Notebooks (Legacy)"
-    notebooks_new: "Notebooks (New)"
     envoy: "Envoy"
     httpd: "Apache HTTP Server"
     istio: "Istio"

content/en/account_management/audit_trail/events.md

@@ -51,6 +51,7 @@ further_reading:
 - [Private Action Runners](#private-action-runners)
 - [Observability Pipelines](#observability-pipelines)
 - [On-Call](#on-call)
+- [Network Device Monitoring](#network-device-monitoring)
 
 
 See the [Audit Trail documentation][2] for more information on setting up and configuring Audit Trail.
@@ -364,6 +365,22 @@ See the [Audit Trail documentation][2] for more information on setting up and co
 | [Enable Container Image Trends][151]  | A user enabled Container Image Trends.  | `@evt.name:"Infrastructure Monitoring" @asset.type:configure_container_image_trends @action:enabled`  |
 | [Disable Container Image Trends][152] | A user disabled Container Image Trends. | `@evt.name:"Infrastructure Monitoring" @asset.type:configure_container_image_trends @action:disabled` |
 
+### Network Device Monitoring
+| Name                                  | Description of audit event                | Query in audit explorer                                                                    |
+|---------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------|
+| [Modify NetFlow port mappings][153]   | A user modified NetFlow port mappings.    | `@evt.name:"Network Device Monitoring" @asset.type:netflow_port_mappings @action:modified` |
+| [Delete NetFlow port mappings][154]   | A user deleted NetFlow port mappings.     | `@evt.name:"Network Device Monitoring" @asset.type:netflow_port_mappings @action:deleted`  |
+| [Access network device profiles][155] | A user accessed network device profiles.  | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+| [Access network device details][156]  | A user accessed network device details.   | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+| [Access network interfaces][157]      | A user accessed network interfaces.       | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+| [Access network devices list][158]    | A user accessed the network devices list. | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+| [Access network device facets][159]   | A user accessed network device facets.    | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+| [Access network device groups][160]   | A user accessed network device groups.    | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+| [Access network device tags][161]     | A user accessed network device tags.      | `@evt.name:"Network Device Monitoring" @asset.type:network_device_tags @action:accessed`   |
+| [Modify network device tags][162]     | A user modified network device tags."     | `@evt.name:"Network Device Monitoring" @asset.type:network_device_tags @action:modified`   |
+| [Access network MIB leaves][163]      | A user accessed network MIB leaves.       | `@evt.name:"Network Device Monitoring" @asset.type:network_device @action:accessed`        |
+
+
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
@@ -520,3 +537,14 @@ See the [Audit Trail documentation][2] for more information on setting up and co
 [150]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3AOn-Call%20%40action%3Adeleted%20%40asset.type%3Aoverride
 [151]: https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Infrastructure%20Monitoring%22%20%40asset.type%3Aconfigure_container_image_trends%20%40action%3Aenabled
 [152]: https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Infrastructure%20Monitoring%22%20%40asset.type%3Aconfigure_container_image_trends%20%40action%3Adisabled
+[153]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetflow_port_mappings%20%40action%3Amodified
+[154]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetflow_port_mappings%20%40action%3Adeleted
+[155]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed
+[156]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed
+[157]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed
+[158]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed
+[159]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed
+[160]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed
+[161]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device_tags%20%40action%3Aaccessed
+[162]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device_tags%20%40action%3Amodified
+[163]:https://app.datadoghq.com/audit-trail?query=%40evt.name%3A%22Network%20Device%20Monitoring%22%20%40asset.type%3Anetwork_device%20%40action%3Aaccessed

content/en/agent/basic_agent_usage/windows.md

@@ -58,14 +58,17 @@ When the install finishes, you are given the option to launch the Datadog Agent
 
 1. Open PowerShell with **Administrator** privileges.
 2. Run the following command to install the Datadog Agent:
-    ```powershell
-    Start-Process -Wait msiexec -ArgumentList '/qn /i datadog-agent-7-latest.amd64.msi APIKEY="<YOUR_DATADOG_API_KEY>"'
-    ```
+    {{< code-block lang="powershell" >}}
+$p = Start-Process -Wait -PassThru msiexec -ArgumentList '/qn /i https://windows-agent.datadoghq.com/datadog-agent-7-latest.amd64.msi /log C:\Windows\SystemTemp\install-datadog.log APIKEY="<DATADOG_API_KEY>"'
+if ($p.ExitCode -ne 0) {
+  Write-Host "msiexec failed with exit code $($p.ExitCode) please check the logs at C:\Windows\SystemTemp\install-datadog.log" -ForegroundColor Red
+}
+{{< /code-block >}}
 
 [1]: https://app.datadoghq.com/account/settings/agent/latest?platform=windows
 [2]: /agent/supported_platforms/?tab=windows
 [3]: /agent/faq/windows-agent-ddagent-user/
-[4]: https://s3.amazonaws.com/ddagent-windows-stable/datadog-agent-7-latest.amd64.msi
+[4]: https://windows-agent.datadoghq.com/datadog-agent-7-latest.amd64.msi
 [5]: https://app.datadoghq.com/organization-settings/api-keys
 
 {{% /tab %}}
@@ -135,16 +138,19 @@ When the install finishes, you are given the option to launch the Datadog Agent
 2. Run the following command to install the Datadog Agent:
 
 **Note:** Replace `DatadogGMSA$` with the username of your gMSA. The username **must end with a $ symbol.**
-  ```powershell
-  Start-Process -Wait msiexec -ArgumentList '/qn /i datadog-agent-7-latest.amd64.msi APIKEY="<YOUR_DATADOG_API_KEY>" DDAGENTUSER_NAME="<YOUR_DOMAIN_NAME>\DatadogGMSA$"'
-  ```
+  {{< code-block lang="powershell" >}}
+$p = Start-Process -Wait -PassThru msiexec -ArgumentList '/qn /i https://windows-agent.datadoghq.com/datadog-agent-7-latest.amd64.msi /log C:\Windows\SystemTemp\install-datadog.log APIKEY="<DATADOG_API_KEY>" DDAGENTUSER_NAME="<YOUR_DOMAIN_NAME>\DatadogGMSA$"'
+if ($p.ExitCode -ne 0) {
+  Write-Host "msiexec failed with exit code $($p.ExitCode) please check the logs at C:\Windows\SystemTemp\install-datadog.log" -ForegroundColor Red
+}
+{{< /code-block >}}
 
 [1]: https://app.datadoghq.com/account/settings/agent/latest?platform=windows
 [2]: /agent/supported_platforms/?tab=windows
 [3]: /agent/faq/windows-agent-ddagent-user/
 [4]: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/group-managed-service-accounts-overview#software-requirements
 [5]: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts
-[6]: https://ddagent-windows-stable.s3.amazonaws.com/installers_v2.json
+[6]: https://windows-agent.datadoghq.com/installers_v2.json
 
 {{% /tab %}}
 {{< /tabs >}}
@@ -200,7 +206,7 @@ If you're upgrading from a Datadog Agent version < 5.12.0, first upgrade to a mo
 
 #### Installation log files
 
-You can find Agent installation log files at `%TEMP%\MSI*.LOG`.
+Set the `/log <FILENAME>` msiexec option to configure an installation log file. If this option is not set, msiexec writes the log to `%TEMP%\MSI*.LOG` by default.
 
 #### Validation
 

content/en/agent/fleet_automation/_index.md

@@ -61,10 +61,13 @@ Selecting an Agent gives you more information about it, including its configurat
 
 After you enable Remote Configuration on an Agent, you can send a flare from Datadog. For instructions on sending a flare, see [Send a flare from the Datadog site][7].
 
+When contacting Datadog Support with Remote Configuration enabled for an Agent, the Support team may initiate a flare from your environment in order to better assist you in a timely manner. Flares provide troubleshooting information to Datadog Support to help you resolve your issue.
+
 ## Remote Agent Management
 
 Remote Agent Management simplifies the process of upgrading your Agent fleet by reducing the need to coordinate with multiple deployment or configuration management tools. For more information, see [Remote Agent Management][6].
 
+
 ## Control access to Fleet Automation
 
 Fleet Automation is available to all users in a Datadog organization. You can control access to specific functionality:

content/en/agent/guide/fips-agent.md

@@ -89,13 +89,16 @@ The Datadog FIPS Agent is in Preview and has not been fully audited. Install and
 The Datadog FIPS Agent is in preview and has not been fully audited. Install and test the Agent only on hosts that are not critical to production workloads.
 
 1. Follow the [Windows instructions][1] to uninstall the Datadog Agent.
-1. Run the command below to install the FIPS Agent, replacing `MY_API_KEY` with your API key:
+1. Run the command below to install the FIPS Agent, replacing `DATADOG_API_KEY` with your API key:
 
    **Note:** FIPS support is only available on Agent versions 7.63.0 and above:
 
-   ```powershell
-   Start-Process -Wait msiexec -ArgumentList '/qn /i "https://s3.amazonaws.com/ddagent-windows-stable/beta/datadog-fips-agent-7.63.0-rc.7-fips-preview-2.msi" APIKEY="MY_API_KEY" SITE="ddog-gov.com"'
-   ```
+   {{< code-block lang="powershell" >}}
+$p = Start-Process -Wait -PassThru msiexec -ArgumentList '/qn /i https://windows-agent.datadoghq.com/datadog-fips-agent-7.64.3.msi /log C:\Windows\SystemTemp\install-datadog.log APIKEY="<DATADOG_API_KEY>" SITE="ddog-gov.com"'
+if ($p.ExitCode -ne 0) {
+   Write-Host "msiexec failed with exit code $($p.ExitCode) please check the logs at C:\Windows\SystemTemp\install-datadog.log" -ForegroundColor Red
+}
+{{< /code-block >}}
 
    To install a different preview version of the FIPS Agent, search the [list of stable Agent versions][2] for `datadog-fips-agent` and replace the MSI in the command above with your desired version.
 
@@ -111,7 +114,7 @@ The Datadog FIPS Agent is in preview and has not been fully audited. Install and
 **Note**: The program name for the FIPS Agent in **Add or Remove Programs** is "Datadog FIPS Agent."
 
 [1]: /agent/basic_agent_usage/windows/#uninstall-the-agent
-[2]: https://s3.amazonaws.com/ddagent-windows-stable/beta/installers_v2.json
+[2]: https://windows-agent.datadoghq.com/installers_v2.json
 
 {{% /tab %}}
 {{< /tabs >}}

content/en/agent/guide/windows-agent-ddagent-user.md

@@ -34,9 +34,12 @@ If a user account is specified on the command line, but this user account is not
 
 To specify the optional USERNAME and PASSWORD on the command line, pass the following properties to the `msiexec` command (The bracket `<>` characters indicate a variable that should be replaced):
 
-```shell
-msiexec /i ddagent.msi DDAGENTUSER_NAME=<USERNAME> DDAGENTUSER_PASSWORD=<PASSWORD>
-```
+{{< code-block lang="powershell" >}}
+$p = Start-Process -Wait -PassThru msiexec -ArgumentList '/qn /i https://windows-agent.datadoghq.com/datadog-agent-7-latest.amd64.msi /log C:\Windows\SystemTemp\install-datadog.log APIKEY="<DATADOG_API_KEY>" DDAGENTUSER_NAME="<USERNAME>" DDAGENTUSER_PASSWORD="<PASSWORD>"'
+if ($p.ExitCode -ne 0) {
+  Write-Host "msiexec failed with exit code $($p.ExitCode) please check the logs at C:\Windows\SystemTemp\install-datadog.log" -ForegroundColor Red
+}
+{{< /code-block >}}
 
 Requirements:
 * The username must be 20 characters or fewer to comply with Microsoft's [Active Directory Schema (AD Schema) SAM-Account-Name attribute][1].
@@ -63,9 +66,12 @@ If a user account is specified on the command line, but this user account is not
 
 To specify a username from a domain account, use the following form for the `DDAGENTUSER_NAME` property:
 
-```shell
-msiexec /i ddagent.msi DDAGENTUSER_NAME=<DOMAIN>\<USERNAME> DDAGENTUSER_PASSWORD=<PASSWORD>
-```
+{{< code-block lang="powershell" >}}
+$p = Start-Process -Wait -PassThru msiexec -ArgumentList '/qn /i https://windows-agent.datadoghq.com/datadog-agent-7-latest.amd64.msi /log C:\Windows\SystemTemp\install-datadog.log APIKEY="<DATADOG_API_KEY>" DDAGENTUSER_NAME="<DOMAIN>\<USERNAME>" DDAGENTUSER_PASSWORD="<PASSWORD>"'
+if ($p.ExitCode -ne 0) {
+  Write-Host "msiexec failed with exit code $($p.ExitCode) please check the logs at C:\Windows\SystemTemp\install-datadog.log" -ForegroundColor Red
+}
+{{< /code-block >}}
 
 The `<DOMAIN>` can either be a fully-qualified domain name (in the form `mydomain.com`) or the NETBIOS name (the pre-Windows 2000 name).
 It must be separated from the `<USERNAME>` with a backslash `\`.

content/en/agent/troubleshooting/send_a_flare.md

@@ -28,6 +28,8 @@ A flare gathers all of the Agent's configuration files and logs into an archive
 
 The Datadog Agent is completely open source, which allows you to [verify the code's behavior][1]. If needed, the flare can be reviewed prior to sending since the flare prompts a confirmation before uploading it.
 
+When contacting Datadog Support with Remote Configuration enabled for an Agent, the Support team may initiate a flare from your environment in order to better assist you in a timely manner. Flares provide troubleshooting information to Datadog Support to help you resolve your issue. 
+
 ## Send a flare from the Datadog site
 
 To send a flare from the Datadog site, make sure you've enabled [Fleet Automation][2] and [Remote configuration][3] on the Agent.