Skip to content

[DOCS-15447] Use DO version of Metabase README #25123

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

Draft
evazorro wants to merge 1 commit into
base: master
Choose a base branch
from
+21 −7
Draft

[DOCS-15447] Use DO version of Metabase README #25123

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
28 changes: 21 additions & 7 deletions metabase/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ Integrate Metabase with Datadog for:

**Data Lineage**: View end-to-end lineage across Metabase collections, dashboards, and cards to understand dependencies and downstream impact.

**Note**: Lineage is derived from your data warehouse, so the Metabase integration produces lineage only when at least one [supported data warehouse destination][3] is also connected to Datadog. Log collection has no such requirement.

## Setup

### Prerequisites
Expand Down Expand Up @@ -53,16 +55,25 @@ Integrate Metabase with Datadog for:

### Connect your Metabase account to Datadog

1. Add your Metabase instance type, DNS alias or self-hosted domain, and API key.
|Parameters|Description|
1. Navigate to the [Metabase integration tile][5] and enter the following information:

|Parameter|Description|
|--------------------|--------------------|
|Metabase instance type|The hosting type of your Metabase instance. Valid values are `cloud` or `self-hosted`. Default is `cloud`.|
|Metabase DNS alias|The DNS alias of your Metabase cloud instance (required for cloud instances only). Must be at least three characters long and contain only lowercase letters, dashes, and numbers.|
|Metabase self-hosted instance domain|The domain of your self-hosted Metabase instance (required for self-hosted instances only). Must be publicly accessible via HTTPS only (e.g., example.com).|
|Metabase API key|The API key used to authenticate the API requests.|
|Account name|Used to identify this account in Datadog.|
|Instance type|The hosting type of your Metabase instance. Valid values are `cloud` or `self-hosted`. Default is `cloud`.|
|DNS alias|The DNS alias of your Metabase cloud instance (required for cloud instances only). Must be at least three characters long and contain only lowercase letters, dashes, and numbers.|
|Self-hosted instance domain|The domain of your self-hosted Metabase instance (required for self-hosted instances only). Must be publicly accessible through HTTPS only (for example, `example.com`).|
|API key|The API key used to authenticate the API requests.|

2. Click **Save**.

## What's next

When your Metabase account is successfully connected, Datadog syncs and automatically derives lineage from warehouse tables and columns to Metabase cards and dashboards.

2. Click the Save button to save your settings.
Initial syncs may take up to several hours depending on the size of your Metabase deployment.

After syncing, you can explore your Metabase assets and their upstream dependencies in the [Data Observability Catalog][4].

## Data Collected

Expand All @@ -84,3 +95,6 @@ For further assistance, contact [Datadog Support][2].

[1]: https://www.metabase.com/
[2]: https://docs.datadoghq.com/help/
[3]: https://docs.datadoghq.com/data_observability/quality_monitoring/data_warehouses/
[4]: /data-obs/catalog
[5]: /integrations/metabase
Loading