Skip to content

Commit 58ab19e

Browse files
lkretvixlkretvix
committed
Merge branch 'master' of github.com:DataDog/documentation into lucas.kretvix/dsm-add-new-technology-pages
* 'master' of github.com:DataDog/documentation: (33 commits) Update databricks.md (#28979) [SCA] Change Repo Settings Link in SCA Setup + Troubleshooting page (#28975) add recommendation for RabbitMQ integration (#28945) add warning for openai byok (#28813) SDCD-1160: specifying dora change lead time limitation if previous deployment was too far in the past (#28956) Add helm to argocd docs (#28630) added that TCP is not available for gov site (#28972) Translation Pipeline PR (#28965) Update explorer.md (#28970) [DOCS-10642] Add Snowflake section to OP Amazon S3 destination (#28967) remove "preview" callout from datastore docs (#28963) Update check_references.md (#28855) Update Private Location Windows version to 1.56.1 (#28950) Improve Cdocs logging to catch environment issues (#28961) [DOCS-10446] changes to Resource Catalog policies (#28389) Add code snippet for Kotlin Multiplatform (#28954) minor rum edits (#28106) [DOCS-10699] add regions to restricted networks page (#28958) [DJM-218] Remove install logs section in Databricks page (#28948) [Debugger] Bump minimum Node.js tracer version (#28957) ...
2 parents 81b3aae + 92d599b commit 58ab19e

File tree

118 files changed

+3450
-4629
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

118 files changed

+3450
-4629
lines changed

‎.apigentools-info

+4-4
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2025-04-22 18:30:05.951046",
8-
"spec_repo_commit": "2b6fa951"
7+
"regenerated": "2025-04-24 13:40:52.400928",
8+
"spec_repo_commit": "4295fd1a"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-04-22 18:30:14.967308",
13-
"spec_repo_commit": "2b6fa951"
12+
"regenerated": "2025-04-24 13:41:01.298481",
13+
"spec_repo_commit": "4295fd1a"
1414
}
1515
}
1616
}

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

+4-4
Original file line numberDiff line numberDiff line change
@@ -7478,7 +7478,7 @@ menu:
74787478
- CreateOnCallSchedule
74797479
unstable: []
74807480
order: 1
7481-
- name: Update on call escalation policy
7481+
- name: Update on-call escalation policy
74827482
url: '#update-on-call-escalation-policy'
74837483
identifier: on-call-update-on-call-escalation-policy
74847484
parent: on-call
@@ -7490,7 +7490,7 @@ menu:
74907490
- UpdateOnCallEscalationPolicy
74917491
unstable: []
74927492
order: 6
7493-
- name: Get on call escalation policy
7493+
- name: Get on-call escalation policy
74947494
url: '#get-on-call-escalation-policy'
74957495
identifier: on-call-get-on-call-escalation-policy
74967496
parent: on-call
@@ -7502,7 +7502,7 @@ menu:
75027502
- GetOnCallEscalationPolicy
75037503
unstable: []
75047504
order: 7
7505-
- name: Delete on call escalation policy
7505+
- name: Delete on-call escalation policy
75067506
url: '#delete-on-call-escalation-policy'
75077507
identifier: on-call-delete-on-call-escalation-policy
75087508
parent: on-call
@@ -7514,7 +7514,7 @@ menu:
75147514
- DeleteOnCallEscalationPolicy
75157515
unstable: []
75167516
order: 8
7517-
- name: Create on call escalation policy
7517+
- name: Create on-call escalation policy
75187518
url: '#create-on-call-escalation-policy'
75197519
identifier: on-call-create-on-call-escalation-policy
75207520
parent: on-call

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

+11-6
Original file line numberDiff line numberDiff line change
@@ -2765,13 +2765,13 @@ menu:
27652765
- name: Cloud Resources Schema
27662766
url: infrastructure/resource_catalog/schema/
27672767
parent: infrastructure_resource_catalog
2768-
identifier: infrastructure_resource_catalog_schemat
2769-
weight: 20001
2770-
- name: Governance
2771-
url: infrastructure/resource_catalog/governance/
2768+
identifier: infrastructure_resource_catalog_schema
2769+
weight: 10001
2770+
- name: Policies
2771+
url: infrastructure/resource_catalog/policies/
27722772
parent: infrastructure_resource_catalog
2773-
identifier: infrastructure_resource_catalog_governance
2774-
weight: 20002
2773+
identifier: infrastructure_resource_catalog_policies
2774+
weight: 10002
27752775
- name: Universal Service Monitoring
27762776
url: universal_service_monitoring/
27772777
pre: usm
@@ -3792,6 +3792,11 @@ menu:
37923792
url: tracing/trace_explorer/trace_queries/
37933793
parent: trace_explorer
37943794
weight: 606
3795+
- name: Code Origins for Spans
3796+
url: tracing/guide/code_origins
3797+
parent: tracing
3798+
identifier: tracing_code_origins
3799+
weight: 7
37953800
- name: Service Observability
37963801
url: tracing/services/
37973802
parent: tracing

‎content/en/account_management/org_settings.md

+6-1
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,11 @@ The [**Safety Center**][14] page contains security alerts, warnings, and recomme
8888

8989
### Public sharing
9090

91-
The **Public Sharing** tab contains lists of shared dashboards and shared graphs. You can also edit your sharing settings by clicking the **Enabled** toggles.
91+
The **Public Sharing** tab includes org-wide settings for sharing, along with lists of shared dashboards and graphs. You can enable sharing features granularly and configure additional security options, such as setting a maximum invite duration.
92+
93+
To apply sharing settings across all your orgs, reach out to [Datadog Support][16].
94+
95+
**Note**: OrgAdmin permission is required to view and manage sharing settings and resources.
9296

9397
### OAuth Apps
9498

@@ -171,3 +175,4 @@ The session duration can be configured within the following limits:
171175
[13]: /synthetics/settings/?tab=specifyvalue#overview
172176
[14]: /account_management/safety_center
173177
[15]: /account_management/org_settings/oauth_apps
178+
[16]: /help/

‎content/en/account_management/rbac/permissions.md

+14-1
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ algolia:
1616
subcategory: Datadog Role Permissions
1717
---
1818

19-
## Overview
19+
## Permissions
2020

2121
Permissions define the type of access a user has to a given resource. Typically, permissions give a user the right to read, edit, or delete an object. Permissions underlie the access rights of all roles, including the three managed roles and custom roles.
2222

@@ -30,6 +30,19 @@ Some Datadog permissions provide access to more privileged functionality that is
3030

3131
Sensitive permissions are flagged in the Roles and Permissions interfaces to identify that they may need increased scrutiny. As a best practice, administrators configuring roles should pay special attention to these permissions, and confirm which of these permissions are assigned to their roles and users.
3232

33+
### Preview mode permissions
34+
35+
Some permissions appear in "preview mode" before becoming fully enforced. During this period:
36+
37+
- Preview permissions are marked in the app with a "Preview" badge
38+
- They do not restrict access until the preview period ends
39+
- The preview typically lasts 2-4 weeks before enforcement begins
40+
- Administrators should configure roles appropriately during this period
41+
42+
Preview mode gives your organization's administrators the ability to opt into certain new permissions, so they can prevent losing access to resources that were previously unrestricted. Release notes associated with each preview mode permission indicate when the permission is created and when it will be enforced. While these permissions don't restrict access during preview, Datadog recommends updating role configurations before they become enforced to prevent disruption.
43+
44+
## Roles
45+
3346
### Managed roles
3447

3548
By default, existing users are associated with one of the three managed roles:

‎content/en/actions/datastore/_index.md

-4
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,6 @@ further_reading:
1313
text: "Build Workflows"
1414
---
1515

16-
{{< callout url="https://docs.google.com/forms/d/1NvW3I0Ep-lQo4FbiSwOEjccoFsS9Ue2wYiYDmCxKDYg/viewform?edit_requested=true" btn_hidden="false" header="Try the Preview!">}}
17-
Datastore is in Preview. Use this form to request access today.
18-
{{< /callout >}}
19-
2016
## Overview
2117

2218
The Actions Datastore offers a scalable, structured data storage solution within Datadog's App Builder and Workflow Automation products. It supports CRUD (Create, Read, Update, and Delete) operations and integrates seamlessly with Datadog's ecosystem to optimize persistent data storage without the need for external databases.

‎content/en/agent/logs/log_transport.md

+9
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,9 @@ When logs are sent through HTTPS, use the same [set of proxy settings][3] as the
107107
[2]: /agent/basic_agent_usage/#agent-overhead
108108
[3]: /agent/configuration/proxy/
109109
{{% /tab %}}
110+
110111
{{% tab "TCP" %}}
112+
{{< site-region region="us,eu,us3,us5,ap1" >}}
111113

112114
To enforce TCP transport, update the Agent's [main configuration file][1] (`datadog.yaml`) with:
113115

@@ -123,6 +125,13 @@ To send logs with environment variables, configure the following:
123125

124126
By default, the Datadog Agent sends its logs to Datadog over TLS-encrypted TCP. This requires outbound communication (on port `10516` for Datadog US site and port `443`for Datadog EU site).
125127

128+
{{< /site-region >}}
129+
130+
{{< site-region region="gov" >}}
131+
The TCP endpoint is not supported for this site.
132+
133+
{{< /site-region >}}
134+
126135
[1]: /agent/configuration/agent-configuration-files/
127136
{{% /tab %}}
128137
{{< /tabs >}}

‎content/en/api/v2/on-call/examples.json

+4-4
Large diffs are not rendered by default.

‎content/en/api/v2/on-call/request.UpdateOnCallEscalationPolicy.json

+2-2
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,14 @@
1212
"id": "00000000-aba1-0000-0000-000000000000",
1313
"targets": [
1414
{
15-
"id": "c1d4eb9e-8bb0-974d-85a5-a7dd9db46bee",
15+
"id": "string",
1616
"type": "users"
1717
}
1818
]
1919
}
2020
]
2121
},
22-
"id": "string",
22+
"id": "ab000000-0000-0000-0000-000000000000",
2323
"relationships": {
2424
"teams": {
2525
"data": [

‎content/en/continuous_delivery/deployments/argocd.md

+42-2
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,11 @@ Datadog CD Visibility integrates with Argo CD by using [Argo CD Notifications][2
3131

3232
The setup below uses the [Webhook notification service][5] of Argo CD to send notifications to Datadog.
3333

34-
First, add your [Datadog API Key][11] in the `argocd-notifications-secret` secret with the `dd-api-key` key. See [the Argo CD guide][2] for information on modifying the `argocd-notifications-secret`.
34+
First, add your [Datadog API Key][11] in the `argocd-notifications-secret` secret with the `dd-api-key` key. See [the Argo CD guide][2] for information on modifying the `argocd-notifications-secret`. For sending notifications, the setup is different depending on whether you installed Argo CD using Helm or the regular setup (using `kubectl apply`).
3535

36-
Then, modify the `argocd-notifications-cm` ConfigMap to create the notification service, template, and trigger to send notifications to Datadog:
36+
{{< tabs >}}
37+
{{% tab "Regular setup (with kubectl apply)" %}}
38+
Modify the `argocd-notifications-cm` ConfigMap to create the notification service, template, and trigger to send notifications to Datadog:
3739

3840
```yaml
3941
apiVersion: v1
@@ -68,6 +70,44 @@ data:
6870
- when: app.status.operationState.phase == 'Running' and app.status.health.status in ['Healthy', 'Degraded']
6971
send: [cd-visibility-template]
7072
```
73+
{{% /tab %}}
74+
{{% tab "Helm" %}}
75+
If you used Helm to install Argo CD, add the following configuration to your `values.yaml`:
76+
77+
```yaml
78+
notifications:
79+
notifiers:
80+
service.webhook.cd-visibility-webhook: |
81+
url: https://webhook-intake.{{< region-param key="dd_site" code="true" >}}/api/v2/webhook
82+
headers:
83+
- name: "DD-CD-PROVIDER-ARGOCD"
84+
value: "true"
85+
- name: "Content-Type"
86+
value: "application/json"
87+
- name: "DD-API-KEY"
88+
value: $dd-api-key
89+
templates:
90+
template.cd-visibility-template: |
91+
webhook:
92+
cd-visibility-webhook:
93+
method: POST
94+
body: |
95+
{
96+
"app": {{toJson .app}},
97+
"context": {{toJson .context}},
98+
"service_type": {{toJson .serviceType}},
99+
"recipient": {{toJson .recipient}},
100+
"commit_metadata": {{toJson (call .repo.GetCommitMetadata .app.status.operationState.syncResult.revision)}}
101+
}
102+
triggers:
103+
trigger.cd-visibility-trigger: |
104+
- when: app.status.operationState.phase in ['Succeeded', 'Failed', 'Error'] and app.status.health.status in ['Healthy', 'Degraded']
105+
send: [cd-visibility-template]
106+
- when: app.status.operationState.phase == 'Running' and app.status.health.status in ['Healthy', 'Degraded']
107+
send: [cd-visibility-template]
108+
```
109+
{{% /tab %}}
110+
{{< /tabs >}}
71111

72112
The following resources have been added:
73113
1. The `cd-visibility-webhook` service targets the Datadog intake and configures the correct headers for the request. The `DD-API-KEY` header references the `dd-api-key` entry added previously in the `argocd-notifications-secret`.

‎content/en/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path.md

+2-11
Original file line numberDiff line numberDiff line change
@@ -28,15 +28,6 @@ The exclusive time of a job on the critical path represents the amount of time t
2828

2929
If a CI job `job1` is on the critical path with a duration of 100ms and runs in parallel with a CI job `job2`, which has a duration of 80ms, the exclusive time of `job1` on the critical path is 20ms. This means that reducing the duration of the `job1` by more than 20ms would still only decrease the overall pipeline duration by 20ms.
3030

31-
### Supported CI providers
32-
33-
Filtering and computing the Exclusive Time of CI jobs on the critical path is available for the following CI providers:
34-
* [GitLab][3]
35-
36-
<div class="alert alert-info">If you are interested in critical path but your CI provider is not supported yet, fill out <a href="https://forms.gle/zDgiDSGQxA1HgjXh6" target="_blank">this form</a>.</div>
37-
38-
Even without Filtering and computing Exclusive Time, you can still [highlight which CI jobs are on the critical path][4] using the Pipeline Execution detail view across all CI providers.
39-
4031
## Identify the key CI jobs to improve your CI pipeline
4132

4233
### Using the facet
@@ -50,7 +41,7 @@ Notice that these facets are only available using the `ci_level:job` in your que
5041
### Using the dashboard template
5142

5243
You can also import the [CI Visibility - Critical Path][1] dashboard template:
53-
- Open the [civisibility-critical-path-gitlab-dashboard.json][1] dashboard template and copy the content in the clipboard.
44+
- Open the [civisibility-critical-path-dashboard.json][1] dashboard template and copy the content in the clipboard.
5445
- Create a [New Dashboard][2] in Datadog.
5546
- Paste the copied content in the new dashboard.
5647
- Save the dashboard.
@@ -77,7 +68,7 @@ Since we know this CI job is on the critical path 43.5% of the time, we could po
7768

7869
{{< partial name="whats-next/whats-next.html" >}}
7970

80-
[1]: /resources/json/civisibility-critical-path-gitlab-dashboard.json
71+
[1]: /resources/json/civisibility-critical-path-dashboard.json
8172
[2]: /dashboards/
8273
[3]: /continuous_integration/pipelines/gitlab/?tab=gitlabcom
8374
[4]: /continuous_integration/search/#highlight-critical-path

‎content/en/continuous_integration/pipelines/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -145,13 +145,13 @@ If your CI provider is not supported, you can try setting up Pipeline Visibility
145145
| {{< ci-details title="Pipeline trace visualization" >}}Visualization of pipeline executions with associated tracing.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} |
146146
| {{< ci-details title="Job failure analysis" >}}Analysis and categorization of job failures using LLM models based on relevant logs. <a href="https://docs.datadoghq.com/continuous_integration/guides/use_ci_jobs_failure_analysis/">More info</a>.{{< /ci-details >}} | | {{< X >}} | | | {{< X >}} | | | | | |
147147
| {{< ci-details title="Running pipelines" >}}Identification of pipelines executions that are running with associated tracing.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | | {{< X >}} | | | | {{< X >}} | {{< X >}} |
148-
| {{< ci-details title="Filter CI Jobs on the critical path" >}}Identification of CI jobs that are on the critical path of the pipeline.{{< /ci-details >}} | | {{< X >}} | | | | | | | | |
148+
| {{< ci-details title="Filter CI Jobs on the critical path" >}}Identification of CI jobs that are on the critical path of the pipeline.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} |
149149
| {{< ci-details title="Partial retries" >}}Identification of partial retries (for example, when only a subset of jobs were retried).{{< /ci-details >}} | | {{< X >}} | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} |
150150
| {{< ci-details title="Step spans" >}}Step level spans are available for more granular visibility.{{< /ci-details >}} | {{< X >}} (_But are presented as job spans_) | | | | {{< X >}} | | {{< X >}} | | | {{< X >}} |
151151
| {{< ci-details title="Manual steps" >}}Identification of when there is a job with a manual approval phase in the overall pipeline.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} |
152152
| {{< ci-details title="Approval wait time">}}Time for which a pipeline or job has been waiting for a manual approval.{{< /ci-details >}} | | {{< X >}} | | | {{< X >}} | {{< X >}} | | | {{< X >}} | |
153153
| {{< ci-details title="Queue time" >}}Time for which a pipeline or job was in the queue before execution.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | {{< X >}} |
154-
| {{< ci-details title="Execution time" >}}Time for which a pipeline has been actively running jobs.{{< /ci-details >}} | | {{< X >}} | | | | | | | | |
154+
| {{< ci-details title="Execution time" >}}Time for which a pipeline has been actively running jobs.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} |
155155
| {{< ci-details title="Logs correlation" >}}Retrieval of pipeline or job logs from the CI provider. Logs are displayed on the <strong>Logs</strong> tab in the Pipeline Execution view.{{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | | {{< X >}} | |
156156
| {{< ci-details title="Infrastructure metric correlation" >}}Correlation of host-level information for the Datadog Agent, CI pipelines, or job runners to CI pipeline execution data.{{< /ci-details >}} | {{< X >}} | {{< X >}} | | {{< X >}} | {{< X >}} | | | | | |
157157
| {{< ci-details title="Custom spans for traced commands using datadog-ci" >}}Support for sending command-level events to CI Visibility to be incorporated into pipeline flame graph visualization. You can then query and analyze <a href="https://docs.datadoghq.com/continuous_integration/pipelines/custom_commands/">these events</a>. {{< /ci-details >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | | {{< X >}} | |

‎content/en/continuous_integration/pipelines/awscodepipeline.md

+4
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,8 @@ Set up tracing on AWS CodePipeline to collect data about pipeline executions, an
3636
| **Logs correlation | Logs correlation | Correlate pipeline and job spans to logs and enable [job log correlation](#collect-job-logs). |
3737
| [Approval wait time][17] | Approval wait time | View the amount of time jobs and pipelines wait for manual approvals. |
3838
| [Custom spans][18] | Custom spans | Configure custom spans for your pipelines. |
39+
| [Filter CI Jobs on the critical path][19] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. |
40+
| [Execution time][20] | Execution time | View the amount of time pipelines have been running jobs. |
3941

4042
*AWS CodePipeline running pipelines don't have Git information until they have finished.\
4143
**AWS CodePipeline logs correlation is only available for AWS CodeBuild actions.
@@ -160,3 +162,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep
160162
[16]: /logs/guide/send-aws-services-logs-with-the-datadog-lambda-function
161163
[17]: /glossary/#approval-wait-time
162164
[18]: /glossary/#custom-span
165+
[19]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/
166+
[20]: /glossary/#pipeline-execution-time

‎content/en/continuous_integration/pipelines/azure.md

+4
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ Set up tracing on Azure Pipelines to gain real time insights into your CI/CD wor
3434
|---|---|---|
3535
| [Custom tags][10] [and measures at runtime][11] | Custom tags and measures at runtime | Configure [custom tags and measures][6] at runtime. |
3636
| [Custom spans][15] | Custom spans | Configure custom spans for your pipelines. |
37+
| [Filter CI Jobs on the critical path][19] | Filter CI Jobs on the critical path | Filter by jobs on the critical path. |
38+
| [Execution time][20] | Execution time | View the amount of time pipelines have been running jobs. |
3739

3840
## Configure the Datadog integration
3941

@@ -157,3 +159,5 @@ The **CI Pipeline List** page shows data for only the default branch of each rep
157159
[16]: /integrations/azure_devops/
158160
[17]: /continuous_integration/search/#search-for-pipelines
159161
[18]: /logs/guide/best-practices-for-log-management/
162+
[19]: /continuous_integration/guides/identify_highest_impact_jobs_with_critical_path/
163+
[20]: /glossary/#pipeline-execution-time

0 commit comments

Comments
 (0)