From f8899ac3290f42b36541a81a78a1d4f696a27fa5 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 5 May 2026 17:15:05 -0400 Subject: [PATCH 1/3] Document Custom alias URLs field on Snowflake integration The Snowflake integration setup now exposes a Custom alias URLs field for registering alternative names that other tools use to reference the same account (PrivateLink URLs, dbt account identifiers, etc.). Add a short subsection that explains when the field is needed and how lineage stitching uses it. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../data_warehouses/snowflake.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md index f6995f1258f..d2c1f0ca4b2 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md @@ -161,7 +161,21 @@ To configure the Snowflake integration in Datadog: 3. Follow the flow to enter your account details and upload a private key. 4. Turn on {{< ui >}}Enable Data Observability for Snowflake tables{{< /ui >}}. -5. Click {{< ui >}}Save & Test{{< /ui >}}. +5. (Optional) Under {{< ui >}}Custom alias URLs{{< /ui >}}, register any additional names used to reference this Snowflake account from other tools — for example, the account identifier configured in dbt, the connection string used by a BI tool, or an AWS PrivateLink URL. See [Custom alias URLs](#custom-alias-urls) below for when this is needed. +6. Click {{< ui >}}Save & Test{{< /ui >}}. + +### Custom alias URLs + +This field is optional. Use it when the Snowflake account name Datadog connects to does not match how other tools reference the same account. + +Lineage events arriving from sources outside Datadog — OpenLineage emitters, dbt manifests, query history from other tools — identify the warehouse using whichever name was configured upstream. If those names differ from the canonical account URL Datadog uses, lineage from those sources is not stitched to this Snowflake integration. + +Registering each alternative name as a {{< ui >}}Custom alias URL{{< /ui >}} tells Datadog to treat them as references to the same Snowflake account, so cross-tool lineage resolves correctly. Common cases include: + +- The account is reached through an AWS PrivateLink URL. +- A dbt project, BI tool, or other connector is configured with an account identifier that does not match the canonical URL. + +To add an alias, expand {{< ui >}}Configure Data Observability{{< /ui >}} during integration setup and click {{< ui >}}+ Add Alias{{< /ui >}} under {{< ui >}}Custom alias URLs{{< /ui >}}. Add one entry per alternative name. Aliases apply only to the Snowflake account being configured; each Snowflake integration manages its own alias list. ## Snowflake tasks and Snowpipes From 7ac304cfd5d80165f1b6d2c6509758a38f92646c Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 5 May 2026 17:20:28 -0400 Subject: [PATCH 2/3] Address Vale: drop spaced em dashes; shorten step 5 sentence MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace " — " with parenthetical or split sentence to satisfy the Datadog Vale style (no spaces around dashes; sentence length ≤25 words). Co-Authored-By: Claude Opus 4.7 (1M context) --- .../quality_monitoring/data_warehouses/snowflake.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md index d2c1f0ca4b2..6fb085fd691 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md @@ -161,14 +161,14 @@ To configure the Snowflake integration in Datadog: 3. Follow the flow to enter your account details and upload a private key. 4. Turn on {{< ui >}}Enable Data Observability for Snowflake tables{{< /ui >}}. -5. (Optional) Under {{< ui >}}Custom alias URLs{{< /ui >}}, register any additional names used to reference this Snowflake account from other tools — for example, the account identifier configured in dbt, the connection string used by a BI tool, or an AWS PrivateLink URL. See [Custom alias URLs](#custom-alias-urls) below for when this is needed. +5. (Optional) Under {{< ui >}}Custom alias URLs{{< /ui >}}, register any additional names other tools use to reference this Snowflake account. Examples include the account identifier configured in dbt, the connection string used by a BI tool, or an AWS PrivateLink URL. See [Custom alias URLs](#custom-alias-urls) below for when this is needed. 6. Click {{< ui >}}Save & Test{{< /ui >}}. ### Custom alias URLs This field is optional. Use it when the Snowflake account name Datadog connects to does not match how other tools reference the same account. -Lineage events arriving from sources outside Datadog — OpenLineage emitters, dbt manifests, query history from other tools — identify the warehouse using whichever name was configured upstream. If those names differ from the canonical account URL Datadog uses, lineage from those sources is not stitched to this Snowflake integration. +Lineage events arriving from sources outside Datadog (OpenLineage emitters, dbt manifests, query history from other tools) identify the warehouse using whichever name was configured upstream. If those names differ from the canonical account URL Datadog uses, lineage from those sources is not stitched to this Snowflake integration. Registering each alternative name as a {{< ui >}}Custom alias URL{{< /ui >}} tells Datadog to treat them as references to the same Snowflake account, so cross-tool lineage resolves correctly. Common cases include: From e5063ec955b3aaec60d5fedb4650ff13995a87f5 Mon Sep 17 00:00:00 2001 From: Harel Shein Date: Tue, 5 May 2026 17:24:50 -0400 Subject: [PATCH 3/3] =?UTF-8?q?Address=20Vale:=20split=20two=20long=20sent?= =?UTF-8?q?ences=20to=20=E2=89=A425=20words?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.7 (1M context) --- .../quality_monitoring/data_warehouses/snowflake.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md index 6fb085fd691..1b68d13e59a 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md @@ -168,9 +168,9 @@ To configure the Snowflake integration in Datadog: This field is optional. Use it when the Snowflake account name Datadog connects to does not match how other tools reference the same account. -Lineage events arriving from sources outside Datadog (OpenLineage emitters, dbt manifests, query history from other tools) identify the warehouse using whichever name was configured upstream. If those names differ from the canonical account URL Datadog uses, lineage from those sources is not stitched to this Snowflake integration. +Lineage events from outside Datadog include OpenLineage emitters, dbt manifests, and query history from other tools. These events identify the warehouse using whatever name the upstream tool was configured with. If those names differ from the canonical account URL Datadog uses, lineage from those sources is not stitched to this Snowflake integration. -Registering each alternative name as a {{< ui >}}Custom alias URL{{< /ui >}} tells Datadog to treat them as references to the same Snowflake account, so cross-tool lineage resolves correctly. Common cases include: +Registering each alternative name as a {{< ui >}}Custom alias URL{{< /ui >}} tells Datadog to treat them as references to the same Snowflake account. Cross-tool lineage then resolves correctly. Common cases include: - The account is reached through an AWS PrivateLink URL. - A dbt project, BI tool, or other connector is configured with an account identifier that does not match the canonical URL.