From 7d1a5b18458de330fb5a955f88ca214f38eb582f Mon Sep 17 00:00:00 2001 From: Adrien Boitreaud Date: Fri, 22 May 2026 11:30:47 +0200 Subject: [PATCH 1/2] Clarify Databricks networking restrictions vs Private Link guidance --- .../jobs_monitoring/databricks/_index.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/content/en/data_observability/jobs_monitoring/databricks/_index.md b/content/en/data_observability/jobs_monitoring/databricks/_index.md index f657a2e9cd3..a3f0059c3dd 100644 --- a/content/en/data_observability/jobs_monitoring/databricks/_index.md +++ b/content/en/data_observability/jobs_monitoring/databricks/_index.md @@ -16,7 +16,7 @@ further_reading: ## Setup -
Databricks Networking Restrictions can block some Datadog functions. Add the following Datadog IP ranges to your allow-list: {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IPs" >}}, {{< region-param key="ip_ranges_url_api" link="true" text="API IPs" >}}.
+
If your Databricks workspace has Networking Restrictions enabled, add Datadog's {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP ranges" >}} to your allow-list. If your workspace uses Private Link, see the Private Link Connectivity tab below.
Follow these steps to enable Data Observability: Jobs Monitoring for Databricks. @@ -491,11 +491,7 @@ Additionally, for Datadog to access your Databricks cost data in Data Observabil ### Set up Data Observability: Jobs Monitoring with Databricks Networking Restrictions With [Databricks Networking Restrictions][12], Datadog may not have access to your Databricks APIs, which is required to collect traces for Databricks job executions along with tags and other metadata. -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 workspace. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] to give Datadog API access. - -To monitor workspaces that use [Databricks Private Link][14] connectivity, see [Private Link Connectivity (Preview)][15]. - -[15]: /data_observability/jobs_monitoring/databricks/private_link +If you are controlling Databricks API access with [IP access lists][13], add Datadog's {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} to your allow-list. See Databricks's documentation for configuring IP access lists for [individual workspaces][16]. ## Further Reading @@ -509,7 +505,6 @@ To monitor workspaces that use [Databricks Private Link][14] connectivity, see [ [9]: https://app.datadoghq.com/data-jobs/configuration [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 [16]: https://docs.databricks.com/en/security/network/front-end/ip-access-list-workspace [18]: https://docs.databricks.com/api/workspace/clusters/edit#spark_env_vars [19]: https://docs.databricks.com/aws/en/security/auth/access-control#access-control-lists-overview From d8f2cda0cea521abb68d69485710029772c9fc83 Mon Sep 17 00:00:00 2001 From: Adrien Boitreaud Date: Fri, 22 May 2026 11:34:49 +0200 Subject: [PATCH 2/2] bring back sentence on PL at the end --- .../jobs_monitoring/databricks/_index.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/en/data_observability/jobs_monitoring/databricks/_index.md b/content/en/data_observability/jobs_monitoring/databricks/_index.md index a3f0059c3dd..02b870d2173 100644 --- a/content/en/data_observability/jobs_monitoring/databricks/_index.md +++ b/content/en/data_observability/jobs_monitoring/databricks/_index.md @@ -491,7 +491,11 @@ Additionally, for Datadog to access your Databricks cost data in Data Observabil ### Set up Data Observability: Jobs Monitoring with Databricks Networking Restrictions With [Databricks Networking Restrictions][12], Datadog may not have access to your Databricks APIs, which is required to collect traces for Databricks job executions along with tags and other metadata. -If you are controlling Databricks API access with [IP access lists][13], add Datadog's {{< region-param key="ip_ranges_url_webhooks" link="true" text="webhook IP addresses" >}} to your allow-list. See Databricks's documentation for configuring IP access lists for [individual workspaces][16]. +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 workspace. See Databricks's documentation for configuring IP access lists for [individual workspaces][16] to give Datadog API access. + +To monitor workspaces that use [Databricks Private Link][14] connectivity, see [Private Link Connectivity (Preview)][15]. + +[15]: /data_observability/jobs_monitoring/databricks/private_link ## Further Reading @@ -505,6 +509,7 @@ If you are controlling Databricks API access with [IP access lists][13], add Dat [9]: https://app.datadoghq.com/data-jobs/configuration [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 [16]: https://docs.databricks.com/en/security/network/front-end/ip-access-list-workspace [18]: https://docs.databricks.com/api/workspace/clusters/edit#spark_env_vars [19]: https://docs.databricks.com/aws/en/security/auth/access-control#access-control-lists-overview