From b073ad2c5dc1fdd918c8a17e31036cd4d436dabd Mon Sep 17 00:00:00 2001 From: Kevin Hu Date: Sat, 4 Jul 2026 23:14:19 -0400 Subject: [PATCH 1/2] Add Hex integration documentation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hex has been GA (per the DO Product Features tracker) with zero public documentation. Grounded in domains/data_observability/apps/apis/ data-observability-crawler/internal/crawlers/hex/ (hex_client.go, hex_crawler.go, models.go) and the hex.json connection schema. Follows the same structure as the sibling Metabase/Looker/PowerBI pages. Explicitly notes the one real limitation found in code: Databricks and Postgres data-connection lineage is incomplete (TODO comments in models.go) even though Snowflake and BigQuery are fully supported — included so the docs don't overclaim. AI assistance: drafted by Claude Code, grounded in the cited crawler source and connection schema. --- .../business_intelligence/_index.md | 1 + .../business_intelligence/hex.md | 44 +++++++++++++++++++ 2 files changed, 45 insertions(+) create mode 100644 content/en/data_observability/quality_monitoring/business_intelligence/hex.md diff --git a/content/en/data_observability/quality_monitoring/business_intelligence/_index.md b/content/en/data_observability/quality_monitoring/business_intelligence/_index.md index bda3beeffe2..bb5e8beaa5f 100644 --- a/content/en/data_observability/quality_monitoring/business_intelligence/_index.md +++ b/content/en/data_observability/quality_monitoring/business_intelligence/_index.md @@ -24,6 +24,7 @@ Use these integrations to: {{< nextlink href="data_observability/quality_monitoring/business_intelligence/sigma" >}}Sigma{{< /nextlink >}} {{< nextlink href="data_observability/quality_monitoring/business_intelligence/metabase" >}}Metabase{{< /nextlink >}} {{< nextlink href="data_observability/quality_monitoring/business_intelligence/powerbi" >}}Power BI{{< /nextlink >}} + {{< nextlink href="data_observability/quality_monitoring/business_intelligence/hex" >}}Hex{{< /nextlink >}} {{< /whatsnext >}} ## Further reading diff --git a/content/en/data_observability/quality_monitoring/business_intelligence/hex.md b/content/en/data_observability/quality_monitoring/business_intelligence/hex.md new file mode 100644 index 00000000000..516fdeaee97 --- /dev/null +++ b/content/en/data_observability/quality_monitoring/business_intelligence/hex.md @@ -0,0 +1,44 @@ +--- +title: Hex +description: Connect Hex to Datadog Data Observability to view end-to-end lineage from warehouse tables to Hex projects. +further_reading: + - link: '/data_observability/' + tag: 'Documentation' + text: 'Learn about Data Observability' +--- + +## Overview + +Datadog's Hex integration helps data teams understand which Hex projects and notebooks depend on their warehouse tables, so you can assess the impact of a schema or pipeline change before it breaks a report. When Datadog connects, it: + +- Pulls project and SQL cell metadata from your Hex workspace. +- Parses the SQL in each cell to generate table- and column-level lineage from your warehouse to downstream Hex projects. + +**Note**: Only SQL cells are synced. Code, Markdown, chart, and input cells are not included in lineage. + +## Connect Hex + +### Generate an API token + +1. In your Hex workspace settings, go to the {{< ui >}}API keys{{< /ui >}} page. +1. Click {{< ui >}}New Token{{< /ui >}}. +1. Provide a description and an expiration. Datadog recommends a token with no expiration. +1. Under API scopes, select **Read Access** for {{< ui >}}Projects{{< /ui >}}, {{< ui >}}Cells{{< /ui >}}, and {{< ui >}}Data connections{{< /ui >}}. + +### Add the Hex integration + +Navigate to the Hex integration tile and enter the following information: + +| Parameter | Description | +|-----------|-------------| +| API Token | The workspace token generated above. | +| Custom Domain | Optional. Set this if your workspace uses a single-tenant, EU multi-tenant, or HIPAA multi-tenant Hex domain (for example, `eu.hex.tech`). Leave blank for the standard `app.hex.tech`. | +| Workspace ID | Optional. Used to generate direct links from Datadog to your Hex projects and cells. Find it in any Hex URL: `https://app.hex.tech//hex/...`. | + +Datadog syncs your Hex workspace every 60 minutes. + +## Supported warehouses + +Lineage resolution is fully supported for Hex data connections to **Snowflake** and **BigQuery**. Databricks and Postgres data connections are recognized, but lineage resolution for them is incomplete as of this writing — contact [support][1] if you rely on Hex-to-Databricks or Hex-to-Postgres lineage. + +[1]: /help/ From 3e73e19f48b42129cabc81ce5bac6db71b1a76a9 Mon Sep 17 00:00:00 2001 From: Kevin Hu Date: Sun, 5 Jul 2026 01:07:55 -0400 Subject: [PATCH 2/2] Add Hex to the Business Intelligence sidebar navigation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Same class of bug just found and fixed for Airbyte: this PR's new content/en/.../business_intelligence/hex.md page and its elt-equivalent whatsnext link were correctly added, but config/_default/menus/main.en.yaml (the separate file that drives the actual sidebar) was not — this branch predates discovering that file exists. Added the missing entry, weighted to sort after the existing four BI integrations. --- config/_default/menus/main.en.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 69ba6d57d55..12124ea9e37 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -5381,6 +5381,11 @@ menu: identifier: business_intelligence_integrations_powerbi parent: business_intelligence_integrations weight: 4000000 + - name: Hex + url: data_observability/quality_monitoring/business_intelligence/hex + identifier: business_intelligence_integrations_hex + parent: business_intelligence_integrations + weight: 5000000 - name: Jobs Monitoring url: data_observability/jobs_monitoring/ pre: data-jobs-monitoring