From 035fdfa85e5749f1ae35fe4679987d37051fef5f Mon Sep 17 00:00:00 2001 From: aboitreaud <72934368+aboitreaud@users.noreply.github.com> Date: Tue, 21 Oct 2025 17:56:20 +0200 Subject: [PATCH 1/5] Update databricks.md --- content/en/data_jobs/databricks.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/data_jobs/databricks.md b/content/en/data_jobs/databricks.md index c7b0fdff1e1a8..e8cdb1668c5d2 100644 --- a/content/en/data_jobs/databricks.md +++ b/content/en/data_jobs/databricks.md @@ -438,7 +438,7 @@ With [Databricks Networking Restrictions][12], Datadog may not have access to yo If you are controlling Databricks API access with [IP access lists][13], allow-listing Datadog's specific {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} allows Datadog to connect to the Databricks APIs in your workspaces/account. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] and the [account console][17] to give Datadog API access. Updating the IP access lists **at both the workspace and account level is required** for the Databricks integration. **Note:** Datadog only uses Databricks account-level APIs to automatically refresh your service principal's client secret. -If you are using [Databricks Private Connectivity][14], reach out to the Datadog [support team][15] to discuss potential options. +Note that [Databricks Private Link][14] connectivity is not supported at this time. If you require private connectivity options, please reach out to your Datadog representative to discuss alternative solutions. ## Further Reading @@ -453,7 +453,6 @@ If you are using [Databricks Private Connectivity][14], reach out to the Datadog [12]: https://docs.databricks.com/en/security/network/front-end/index.html [13]: https://docs.databricks.com/en/security/network/front-end/ip-access-list.html [14]: https://www.databricks.com/trust/security-features/secure-your-data-with-private-networking -[15]: https://www.datadoghq.com/support/ [16]: https://docs.databricks.com/en/security/network/front-end/ip-access-list-workspace [17]: https://docs.databricks.com/aws/en/security/network/front-end/ip-access-list-account [18]: https://docs.databricks.com/api/workspace/clusters/edit#spark_env_vars From 3cb2ee9d27d0bf1c1b0f9ddd194de1d5b5fae948 Mon Sep 17 00:00:00 2001 From: aboitreaud <72934368+aboitreaud@users.noreply.github.com> Date: Tue, 21 Oct 2025 18:07:29 +0200 Subject: [PATCH 2/5] Update databricks.md --- content/en/data_jobs/databricks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/databricks.md b/content/en/data_jobs/databricks.md index e8cdb1668c5d2..63a0ab512c2b4 100644 --- a/content/en/data_jobs/databricks.md +++ b/content/en/data_jobs/databricks.md @@ -438,7 +438,7 @@ With [Databricks Networking Restrictions][12], Datadog may not have access to yo If you are controlling Databricks API access with [IP access lists][13], allow-listing Datadog's specific {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} allows Datadog to connect to the Databricks APIs in your workspaces/account. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] and the [account console][17] to give Datadog API access. Updating the IP access lists **at both the workspace and account level is required** for the Databricks integration. **Note:** Datadog only uses Databricks account-level APIs to automatically refresh your service principal's client secret. -Note that [Databricks Private Link][14] connectivity is not supported at this time. If you require private connectivity options, please reach out to your Datadog representative to discuss alternative solutions. +**Note**: [Databricks Private Link][14] connectivity is not supported at this time. If you require private connectivity options, please reach out to your Datadog representative to discuss alternative solutions. ## Further Reading From c69bda8f8f0d45c50e31f3893d20e250abc9b48c Mon Sep 17 00:00:00 2001 From: aboitreaud <72934368+aboitreaud@users.noreply.github.com> Date: Tue, 21 Oct 2025 18:08:21 +0200 Subject: [PATCH 3/5] Update databricks.md --- content/en/data_jobs/databricks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/databricks.md b/content/en/data_jobs/databricks.md index 63a0ab512c2b4..0fee2c49e5089 100644 --- a/content/en/data_jobs/databricks.md +++ b/content/en/data_jobs/databricks.md @@ -438,7 +438,7 @@ With [Databricks Networking Restrictions][12], Datadog may not have access to yo If you are controlling Databricks API access with [IP access lists][13], allow-listing Datadog's specific {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} allows Datadog to connect to the Databricks APIs in your workspaces/account. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] and the [account console][17] to give Datadog API access. Updating the IP access lists **at both the workspace and account level is required** for the Databricks integration. **Note:** Datadog only uses Databricks account-level APIs to automatically refresh your service principal's client secret. -**Note**: [Databricks Private Link][14] connectivity is not supported at this time. If you require private connectivity options, please reach out to your Datadog representative to discuss alternative solutions. +**Note**: [Databricks Private Link][14] connectivity is not supported at this time. If you require private connectivity options, reach out to your Datadog representative to discuss alternative solutions. ## Further Reading From a9538730223a6fbd3c0f04167169a3ac1463b6d0 Mon Sep 17 00:00:00 2001 From: Adrien Boitreaud <72934368+aboitreaud@users.noreply.github.com> Date: Tue, 21 Oct 2025 18:10:38 +0200 Subject: [PATCH 4/5] Apply suggestion from @warrierr Co-authored-by: Ryan Warrier --- content/en/data_jobs/databricks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/databricks.md b/content/en/data_jobs/databricks.md index 0fee2c49e5089..fca4c6e274417 100644 --- a/content/en/data_jobs/databricks.md +++ b/content/en/data_jobs/databricks.md @@ -438,7 +438,7 @@ With [Databricks Networking Restrictions][12], Datadog may not have access to yo If you are controlling Databricks API access with [IP access lists][13], allow-listing Datadog's specific {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} allows Datadog to connect to the Databricks APIs in your workspaces/account. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] and the [account console][17] to give Datadog API access. Updating the IP access lists **at both the workspace and account level is required** for the Databricks integration. **Note:** Datadog only uses Databricks account-level APIs to automatically refresh your service principal's client secret. -**Note**: [Databricks Private Link][14] connectivity is not supported at this time. If you require private connectivity options, reach out to your Datadog representative to discuss alternative solutions. +**Note**: Monitoring workspaces that use [Databricks Private Link][14] connectivity is not supported at this time. ## Further Reading From 8a05fdfaad5142fb374970eaa41d3ebed96c67a8 Mon Sep 17 00:00:00 2001 From: Adrien Boitreaud <72934368+aboitreaud@users.noreply.github.com> Date: Tue, 21 Oct 2025 22:53:35 +0200 Subject: [PATCH 5/5] Update content/en/data_jobs/databricks.md Co-authored-by: Bryce Eadie --- content/en/data_jobs/databricks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/data_jobs/databricks.md b/content/en/data_jobs/databricks.md index fca4c6e274417..e6022a62ab13e 100644 --- a/content/en/data_jobs/databricks.md +++ b/content/en/data_jobs/databricks.md @@ -438,7 +438,7 @@ With [Databricks Networking Restrictions][12], Datadog may not have access to yo If you are controlling Databricks API access with [IP access lists][13], allow-listing Datadog's specific {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} allows Datadog to connect to the Databricks APIs in your workspaces/account. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] and the [account console][17] to give Datadog API access. Updating the IP access lists **at both the workspace and account level is required** for the Databricks integration. **Note:** Datadog only uses Databricks account-level APIs to automatically refresh your service principal's client secret. -**Note**: Monitoring workspaces that use [Databricks Private Link][14] connectivity is not supported at this time. +**Note**: Monitoring workspaces that use [Databricks Private Link][14] connectivity is not supported. ## Further Reading