Merge branch 'merge' into pr-27150

* merge: (30 commits)
  Revert "Update minimum Ruby tracer version for dynamic instrumentation to 2.9.0 (#27233)"
  Update custom-javascript-assertion.md (#26973)
  [DOCS-9908] Update RUM react initialization parameter (#27231)
  Update minimum Ruby tracer version for dynamic instrumentation to 2.9.0 (#27233)
  (DOCS-9604) Update images and text to match new panel style (#27173)
  Bump otel-agent version to 7.61  (#27221)
  Add note about key validation delay to API and Application keys docum… (#27210)
  Add support for vulnerability management - GetSBOM new endpoint (#27128)
  [ACCESS-3116] Show display name of permissions on permissions page (#27218)
  [DOCS-9912] Remove SDS via agent (#27215)
  [SDCI-880] Add K8s explanation for infra correlation for Gitlab (#27061)
  [AWSX] Update AWS integration role documentation (#27205)
  Include Weaver as a supported framework in Test Optimization for Java (#27152)
  (DOCS-9872) Add docs for Form component (#27118)
  OTel Troubleshooting Update (#27010)
  DOCS-9641 Take 2 (#27213)
  init (#27212)
  Updates the language on the serverless init cloud run page to push customers to use the sidecar (#27101)
  add additional note to the getlog limitation (#27209)
  fix ref numbers (#27206)
  ...

Author: p

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-17 21:42:34.411023",
-            "spec_repo_commit": "27e609f7"
+            "regenerated": "2025-01-22 15:55:44.650228",
+            "spec_repo_commit": "7a8ea4b1"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-17 21:42:42.448005",
-            "spec_repo_commit": "27e609f7"
+            "regenerated": "2025-01-22 15:55:52.977760",
+            "spec_repo_commit": "7a8ea4b1"
         }
     }
 }

config/_default/menus/api.en.yaml

@@ -2587,7 +2587,20 @@ menu:
           - ListVulnerabilities
         unstable:
           - v2
-        order: 3
+        order: 25
+    - name: Get SBOM
+      url: '#get-sbom'
+      identifier: security-monitoring-get-sbom
+      parent: security-monitoring
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - GetSBOM
+        unstable:
+          - v2
+        order: 27
     - name: List vulnerable assets
       url: '#list-vulnerable-assets'
       identifier: security-monitoring-list-vulnerable-assets
@@ -2600,7 +2613,7 @@ menu:
           - ListVulnerableAssets
         unstable:
           - v2
-        order: 4
+        order: 26
     - name: Get a finding
       url: '#get-a-finding'
       identifier: security-monitoring-get-a-finding

config/_default/menus/main.en.yaml

@@ -1904,6 +1904,31 @@ menu:
       parent: service_catalog
       identifier: service_catalog_use_cases
       weight: 3
+    - name: API Management
+      url: service_catalog/use_cases/api_management
+      parent: service_catalog_use_cases
+      identifier: service_catalog_use_cases_api_management
+      weight: 301
+    - name: Cloud Cost Management
+      url: service_catalog/use_cases/cloud_cost_management
+      parent: service_catalog_use_cases
+      identifier: service_catalog_use_cases_cloud_cost_management
+      weight: 302
+    - name: Application Security Management
+      url: service_catalog/use_cases/appsec_management
+      parent: service_catalog_use_cases
+      identifier: service_catalog_use_cases_appsec_management
+      weight: 303
+    - name: Developer Onboarding
+      url: service_catalog/use_cases/dev_onboarding
+      parent: service_catalog_use_cases
+      identifier: service_catalog_use_cases_dev_onboarding
+      weight: 304
+    - name: Dependency Management
+      url: service_catalog/use_cases/dependency_management
+      parent: service_catalog_use_cases
+      identifier: service_catalog_use_cases_dependency_management
+      weight: 305     
     - name: Manage a Component
       url: service_catalog/manage
       parent: service_catalog

content/en/account_management/api-app-keys.md

@@ -56,6 +56,7 @@ To add a Datadog API key or client token:
 
 - Your org must have at least one API key and at most 50 API keys.
 - Key names must be unique across your organization.
+- Newly created API keys typically take a few seconds to become valid.
 
 ## Remove API keys or client tokens
 
@@ -70,6 +71,7 @@ To add a Datadog application key, navigate to [**Organization Settings** > **App
 **Notes:**
 
 - Application key names cannot be blank.
+- Newly created Application keys typically take a few seconds to become valid.
 
 ## Remove application keys
 

content/en/account_management/org_settings/oauth_apps.md

@@ -14,13 +14,13 @@ Use the **OAuth Apps** management page under [Organization Settings][1] to manag
 ## Setup
 ### Permissions
 
-By default, users with [Datadog Standard and Datadog Admin roles][2] can access the OAuth Apps management page. If your organization has [custom roles][3] defined, add your user to any custom role with `org_authorized_apps_read` and `org_authorized_apps_write` permissions. 
+By default, users with the [Datadog Admin role][2] can access the OAuth Apps management page. If your organization has [custom roles][3] defined, add your user to any custom role with the `org_management` permission.
 
-Only users with the Datadog Admin role or the `org_authorized_apps_write` permission can manage OAuth applications on this page, such as disabling applications or revoking OAuth access for a user.
+Only users with the Datadog Admin role or the `org_management` permission can manage OAuth applications on this page, such as disabling applications or revoking OAuth access for a user.
 
 ### Enable
 
-Enabled OAuth applications allow users with necessary permissions to authorize access on their behalf. OAuth applications include the Datadog Mobile App<!-- and your custom [UI Extensions][4] that have [OAuth API Access][5]-->. 
+Enabled OAuth applications allow users with necessary permissions to authorize access on their behalf. OAuth applications include the Datadog Mobile App<!-- and your custom [UI Extensions][4] that have [OAuth API Access][5]-->.
 
 ### Disable
 

content/en/agent/configuration/network.md

@@ -46,6 +46,9 @@ Add the following domains to your inclusion list to allow for Agent installation
 : `trace.agent.`{{< region-param key="dd_site" code="true" >}}<br>
 `instrumentation-telemetry-intake.`{{< region-param key="dd_site" code="true" >}}
 
+[LLM Observabilty][23]
+: `llmobs-intake.`{{< region-param key="dd_site" code="true" >}}
+
 [Container Images][13]
 : `contimage-intake.`{{< region-param key="dd_site" code="true" >}}
 
@@ -393,4 +396,5 @@ To avoid running out of storage space, the Agent stores the metrics on disk only
 [19]: /agent/faq/network-time-protocol-ntp-offset-issues/
 [20]: /integrations/ntp/#overview
 [21]: /logs/log_collection/#logging-endpoints
-[22]: /containers/guide/cluster_agent_autoscaling_metrics
+[22]: /containers/guide/cluster_agent_autoscaling_metrics
+[23]: /llm_observability/

content/en/agent/logs/advanced_log_collection.md

@@ -258,10 +258,6 @@ spec:
 
 ## Scrub sensitive data from your logs
 
-{{< callout url="https://www.datadoghq.com/private-beta/sensitive-data-scanner-using-agent-in-your-premises/" >}}
-  Sensitive Data Scanner using the Agent is in Preview. See the <a href="https://www.datadoghq.com/blog/sensitive-data-scanner-using-the-datadog-agent/">blog post</a> and <a href="https://docs.datadoghq.com/sensitive_data_scanner/">documentation</a> for more information. To request access, fill out this form.
-{{< /callout >}}
-
 If your logs contain sensitive information that need redacting, configure the Datadog Agent to scrub sensitive sequences by using the `log_processing_rules` parameter in your configuration file with the `mask_sequences` type.
 
 This replaces all matched groups with the value of the `replace_placeholder` parameter.

content/en/api/v2/ci-visibility-pipelines/examples.json

@@ -0,0 +1,23 @@
+{
+  "data": {
+    "attributes": {
+      "provider_name": "example-provider",
+      "resource": {
+        "level": "pipeline",
+        "unique_id": "3eacb6f3-ff04-4e10-8a9c-46e6d054024a",
+        "name": "Deploy to AWS",
+        "url": "https://my-ci-provider.example/pipelines/my-pipeline/run/1",
+        "start": "2021-11-11T11:09:11+00:00",
+        "end": "2021-11-11T11:10:41+00:00",
+        "status": "success",
+        "partial_retry": false,
+        "git": {
+          "repository_url": "https://github.com/DataDog/datadog-agent",
+          "sha": "7f263865994b76066c4612fd1965215e7dcb4cd2",
+          "author_email": "[email protected]"
+        }
+      }
+    },
+    "type": "cipipeline_resource_request"
+  }
+}

content/en/api/v2/ci-visibility-pipelines/request.CreateCIAppPipelineEvent_819339921.json

@@ -76,8 +76,7 @@ You can use out-of-the-box tags to break down and allocate your Datadog cost dat
 [4]: https://app.datadoghq.com/billing/usage
 [5]: /account_management/plan_and_usage/cost_details/#cost-summary-sub-organization
 [6]: /account_management/rbac/
-[7]: /account_management/rbac/permissions
-[8]: /account_management/plan_and_usage/cost_details/
-[9]: /account_management/billing/usage_attribution/
-[10]: /account_management/plan_and_usage/cost_details/#cost-summary
-[11]: /account_management/plan_and_usage/cost_details/#cost-chargebacks
+[7]: /account_management/plan_and_usage/cost_details/
+[8]: /account_management/billing/usage_attribution/
+[9]: /account_management/plan_and_usage/cost_details/#cost-summary
+[10]: /account_management/plan_and_usage/cost_details/#cost-chargebacks

content/en/api/v2/security-monitoring/examples.json

@@ -280,7 +280,7 @@ multifiltersearch:
       cloud_provider: AWS
       resource_type: Kubernetes containers
       recommendation_type: Over-provisioned Kubernetes Containers
-      recommendation_description: Containers with less than 30% CPU and memory utilization.
+      recommendation_description: Containers with less than 30% max CPU or memory utilization.
       recommendation_prerequisites: "[Datadog profiling agent](/profiler/enabling/)"
     - category: Over-provisioned resource
       cloud_provider: AWS

content/en/cloud_cost_management/datadog_costs/_index.md

@@ -20,27 +20,27 @@ further_reading:
 
 ## Overview
 
-[GitLab][19] is a DevOps platform that automates the software development lifecycle with integrated CI/CD features, enabling you to deploy applications quickly and securely.
+[GitLab][18] is a DevOps platform that automates the software development lifecycle with integrated CI/CD features, enabling automated, continuous deployment of applications with built-in security controls.
 
 Set up tracing in GitLab to collect data on your pipeline executions, analyze performance bottlenecks, troubleshoot operational issues, and optimize your deployment workflows.
 
 ### Compatibility
 
 | Pipeline Visibility | Platform | Definition |
 |---|---|---|
-| [Running pipelines][25] | Running pipelines | View pipeline executions that are running. Queued or waiting pipelines show with status "Running" on Datadog. |
-| [Partial retries][20] | Partial pipelines | View partially retried pipeline executions. |
-| [Manual steps][21] | Manual steps | View manually triggered pipelines. |
-| [Queue time][22] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. |
+| [Running pipelines][24] | Running pipelines | View pipeline executions that are running. Queued or waiting pipelines show with status "Running" on Datadog. |
+| [Partial retries][19] | Partial pipelines | View partially retried pipeline executions. |
+| [Manual steps][20] | Manual steps | View manually triggered pipelines. |
+| [Queue time][21] | Queue time | View the amount of time pipeline jobs sit in the queue before processing. |
 | Logs correlation | Logs correlation | Correlate pipeline spans to logs and enable [job log collection][12]. |
 | Infrastructure metric correlation | Infrastructure metric correlation | Correlate jobs to [infrastructure host metrics][14] for self-hosted GitLab runners. |
 | Custom pre-defined tags | Custom pre-defined tags | Set [custom tags][10] to all generated pipeline, stages, and job spans. |
 | [Custom tags][15] [and measures at runtime][16] | Custom tags and measures at runtime | Configure [custom tags and measures][13] at runtime. |
 | Parameters | Parameters | Set custom `env` or `service` parameters when a pipeline is triggered. |
 | [Pipeline failure reasons][11] | Pipeline failure reasons | Identify pipeline failure reasons from [error messages][15]. |
-| [Approval wait time][23] | Approval wait time  | View the amount of time jobs and pipelines wait for manual approvals. |
-| [Execution time][24] | Execution time  | View the amount of time pipelines have been running jobs. Gitlab refers to this metric as `duration`. Duration in Gitlab and execution time may show different values. Gitlab does not take into consideration jobs that failed due to certain kinds of failures (such as runner system failures). |
-| [Custom spans][26] | Custom spans | Configure custom spans for your pipelines. |
+| [Approval wait time][22] | Approval wait time  | View the amount of time jobs and pipelines wait for manual approvals. |
+| [Execution time][23] | Execution time  | View the amount of time pipelines have been running jobs. Gitlab refers to this metric as `duration`. Duration in Gitlab and execution time may show different values. Gitlab does not take into consideration jobs that failed due to certain kinds of failures (such as runner system failures). |
+| [Custom spans][25] | Custom spans | Configure custom spans for your pipelines. |
 
 The following GitLab versions are supported:
 
@@ -253,34 +253,46 @@ If you are using self-hosted GitLab runners, you can correlate jobs with the inf
 
 Datadog infrastructure correlation is possible using different methods:
 
-#### Tagging runners with hostname
-
-The GitLab runner must have a tag of the form `host:<hostname>`. Tags can be added while [registering a new runner][6]. As a result, this method is only available when the runner is directly running the job.
+{{< tabs >}}
+{{% tab "Non autoscaling executors" %}}
+The GitLab runner must have a tag in the form `host:<hostname>`. Tags can be added while [registering a new runner][1]. As a result, this method is only available when the runner is directly running the job.
 
 This excludes executors that are autoscaling the infrastructure in order to run the job (such as the Kubernetes, Docker Autoscaler, or Instance executors) as it is not possible to add tags dynamically for those runners.
 
 For existing runners:
 
-{{< tabs >}}
-{{% tab "GitLab &gt;&equals; 15.8" %}}
-Add tags through the UI by going to **Settings > CI/CD > Runners** and editing the appropriate runner.
+- GitLab >= 15.8: Add tags through the UI by going to **Settings > CI/CD > Runners** and editing the appropriate runner.
+
+- GitLab < 15.8: Add tags by updating the runner's `config.toml`. Or add tags through the UI by going to **Settings > CI/CD > Runners** and editing the appropriate runner.
+
+After these steps, CI Visibility adds the hostname to each job. To see the metrics, click on a job span in the trace view. In the drawer, a new tab named **Infrastructure** appears which contains the host metrics.
+
+[1]: https://docs.gitlab.com/runner/register/
 {{% /tab %}}
 
-{{% tab "GitLab &lt; 15.8" %}}
-Add tags by updating the runner's `config.toml`. Or add tags
-through the UI by going to **Settings > CI/CD > Runners** and editing the appropriate runner.
+{{% tab "Docker Autoscaler" %}}
+CI Visibility supports Infrastructure metrics for "Docker Autoscaler" executors. For more information, see the [Correlate Infrastructure Metrics with GitLab Jobs guide][1].
+
+[1]: /continuous_integration/guides/infrastructure_metrics_with_gitlab
 {{% /tab %}}
-{{< /tabs >}}
 
-After these steps, CI Visibility adds the hostname to each job. To see the metrics, click on a job span in the trace view. In the drawer, a new tab named **Infrastructure** appears which contains the host metrics.
+{{% tab "Instance" %}}
+CI Visibility supports Infrastructure metrics for "Instance" executors. For more information, see the [Correlate Infrastructure Metrics with GitLab Jobs guide][1].
 
-#### Instance and Docker Autoscaler executors
+[1]: /continuous_integration/guides/infrastructure_metrics_with_gitlab
+{{% /tab %}}
 
-CI Visibility also supports Infrastructure metrics for "Instance" and "Docker Autoscaler" executors. For more information, see the [Correlate Infrastructure Metrics with GitLab Jobs guide][18].
+{{% tab "Kubernetes" %}}
+CI Visibility supports Infrastructure metrics for the Kubernetes executor. For this, it is necessary to have the Datadog Agent monitoring the Kubernetes Gitlab infrastructure. See [Install the Datadog Agent on Kubernetes][1] to install the Datadog Agent in a Kubernetes cluster.
 
-#### Other executors
+[1]: /containers/kubernetes/installation/?tab=datadogoperator
+{{% /tab %}}
 
-CI Visibility does not support Infrastructure metrics for other executors such as the Kubernetes executor.
+{{% tab "Other executors" %}}
+CI Visibility does not support Infrastructure metrics for other executors.
+{{% /tab %}}
+
+{{< /tabs >}}
 
 ### View error messages for pipeline failures
 
@@ -366,13 +378,13 @@ The <a href="https://docs.gitlab.com/ee/administration/object_storage.html#amazo
 {{% /tab %}}
 {{< /tabs >}}
 
-Logs are billed separately from CI Visibility. Log retention, exclusion, and indexes are configured in [Log Management][29]. Logs for GitLab jobs can be identified by the `datadog.product:cipipeline` and `source:gitlab` tags.
+Logs are billed separately from CI Visibility. Log retention, exclusion, and indexes are configured in [Log Management][6]. Logs for GitLab jobs can be identified by the `datadog.product:cipipeline` and `source:gitlab` tags.
 
 For more information about processing job logs collected from the GitLab integration, see the [Processors documentation][17].
 
 ## View partial and downstream pipelines
 
-You can use the following filters to customize your search query in the [CI Visibility Explorer][27].
+You can use the following filters to customize your search query in the [CI Visibility Explorer][26].
 
 {{< img src="ci/partial_retries_search_tags.png" alt="The Pipeline executions page with Partial Pipeline:retry entered in the search query" style="width:100%;">}}
 
@@ -390,7 +402,7 @@ You can also apply these filters using the facet panel on the left hand side of
 
 Once the integration is successfully configured, the [**CI Pipeline List**][4] and [**Executions**][5] pages populate with data after the pipelines finish.
 
-The **CI Pipeline List** page shows data for only the default branch of each repository. For more information, see [Search and Manage CI Pipelines][28].
+The **CI Pipeline List** page shows data for only the default branch of each repository. For more information, see [Search and Manage CI Pipelines][27].
 
 ## Further reading
 
@@ -401,7 +413,7 @@ The **CI Pipeline List** page shows data for only the default branch of each rep
 [3]: https://docs.gitlab.com/ee/user/project/integrations/webhooks.html
 [4]: https://app.datadoghq.com/ci/pipelines
 [5]: https://app.datadoghq.com/ci/pipeline-executions
-[6]: https://docs.gitlab.com/runner/register/
+[6]: /logs/guide/best-practices-for-log-management/
 [7]: https://docs.gitlab.com/ee/administration/job_artifacts.html#using-object-storage
 [8]: https://docs.gitlab.com/ee/administration/feature_flags.html
 [9]: /logs/
@@ -413,15 +425,13 @@ The **CI Pipeline List** page shows data for only the default branch of each rep
 [15]: /continuous_integration/pipelines/gitlab/?tab=gitlabcom#view-error-messages-for-pipeline-failures
 [16]: /account_management/teams/
 [17]: /logs/log_configuration/processors/
-[18]: /continuous_integration/guides/infrastructure_metrics_with_gitlab
-[19]: https://about.gitlab.com/
-[20]: /glossary/#partial-retry
-[21]: /glossary/#manual-step
-[22]: /glossary/#queue-time
-[23]: /glossary/#approval-wait-time
-[24]: /glossary/#pipeline-execution-time
-[25]: /glossary/#running-pipeline
-[26]: /glossary/#custom-span
-[27]: /continuous_integration/explorer
-[28]: /continuous_integration/search/#search-for-pipelines
-[29]: /logs/guide/best-practices-for-log-management/
+[18]: https://about.gitlab.com/
+[19]: /glossary/#partial-retry
+[20]: /glossary/#manual-step
+[21]: /glossary/#queue-time
+[22]: /glossary/#approval-wait-time
+[23]: /glossary/#pipeline-execution-time
+[24]: /glossary/#running-pipeline
+[25]: /glossary/#custom-span
+[26]: /continuous_integration/explorer
+[27]: /continuous_integration/search/#search-for-pipelines