Skip to content

Document Custom alias URLs field on Snowflake integration #36492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
harels merged 3 commits into from
May 6, 2026
Merged

Document Custom alias URLs field on Snowflake integration #36492

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f8899ac
Document Custom alias URLs field on Snowflake integration
harels May 5, 2026
7ac304c
Address Vale: drop spaced em dashes; shorten step 5 sentence
harels May 5, 2026
e5063ec
Address Vale: split two long sentences to ≤25 words
harels May 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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 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. 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.

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

Expand Down
Loading