Skip to content

Commit 63004fd

Browse files
committed
Convert remaining BI integration pages to stubs pointing at the integrations docs
1 parent 9bd0dd4 commit 63004fd

5 files changed

Lines changed: 30 additions & 253 deletions

File tree

Lines changed: 6 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -1,61 +1,21 @@
11
---
22
title: Looker
3-
description: Connect Looker to Datadog Data Observability to view field-level lineage from warehouse tables to Looker explore fields, dashboards, and Looks.
3+
description: Looker integration for Data Observability lineage. See the integration documentation for setup.
44
further_reading:
55
- link: '/data_observability/'
66
tag: 'Documentation'
77
text: 'Learn about Data Observability'
88
---
99

10-
## Overview
10+
Datadog's Looker integration helps data teams make changes to their data platform without breaking dashboards and Looks, and identify unused content to remove.
1111

12-
Datadog's Looker integration helps data teams make changes to their data platform without breaking dashboards and Looks, and identify unused content to remove. The integration collects metadata and field-level lineage for objects in your Looker account. When Datadog connects, it:
12+
Lineage is derived from your data warehouse, so you also need at least one [supported data warehouse destination][2] connected to Datadog.
1313

14-
- Pulls metadata from your Looker instance, including projects, models, explores, views, dashboards, Looks, and folders
15-
- Generates field-level lineage between warehouse tables and columns and downstream Looker views and derived tables, and between Looker views and other Looker objects such as dashboards and explores
16-
- Parses LookML files directly from your linked Git repositories to extract richer lineage and metadata, including derived tables, view extensions, and refinements
17-
18-
## Setup
19-
20-
### Create a Looker API key
21-
22-
1. Go to your Looker dashboard (for example, at `https://<your_company>.cloud.looker.com`).
23-
2. Navigate to {{< ui >}}Admin{{< /ui >}} > {{< ui >}}Users{{< /ui >}}.
24-
3. Select the user you want to create an API key for.
25-
4. Next to {{< ui >}}API Keys{{< /ui >}}, click {{< ui >}}Edit Keys{{< /ui >}}.
26-
5. Click {{< ui >}}New API Key{{< /ui >}}.
27-
6. Copy the client ID and secret.
28-
29-
### Add the API credentials to Datadog
30-
31-
1. Navigate to the [Looker integration tile][2].
32-
2. Click {{< ui >}}Configure{{< /ui >}} > {{< ui >}}+ Add New Account{{< /ui >}}.
33-
3. Fill out the form with the following:
34-
- {{< ui >}}Account name{{< /ui >}}: A label to identify this Looker instance
35-
- {{< ui >}}Instance URL{{< /ui >}}: The URL of your Looker instance (for example, `https://company.cloud.looker.com`)
36-
- {{< ui >}}Client ID{{< /ui >}}: The client ID from the previous step
37-
- {{< ui >}}API Secret{{< /ui >}}: The client secret from the previous step
38-
4. Click {{< ui >}}Save{{< /ui >}}.
39-
40-
### Connect LookML repositories
41-
42-
Datadog parses LookML files to collect lineage and metadata for Looker views and derived tables.
43-
44-
Connect each LookML Git repository to Datadog using the [Source Code Integration][4]. The next time the Looker integration runs on its hourly schedule, it automatically detects the repositories and parses the LookML files.
45-
46-
If your Git repositories already appear on the Datadog [repositories page][5], no additional steps are required.
47-
48-
## What's next
49-
50-
It can take up to 60 minutes for data to appear after the initial setup.
51-
52-
After syncing, you can explore your Looker assets and their upstream dependencies in the [Data Observability Catalog][3].
14+
See the [Looker integration][1] documentation for setup and configuration.
5315

5416
## Further reading
5517

5618
{{< partial name="whats-next/whats-next.html" >}}
5719

58-
[2]: https://app.datadoghq.com/integrations/looker
59-
[3]: https://app.datadoghq.com/data-obs/catalog
60-
[4]: https://app.datadoghq.com/integrations/github
61-
[5]: https://app.datadoghq.com/source-code/repositories
20+
[1]: /integrations/looker/
21+
[2]: /data_observability/quality_monitoring/data_warehouses/
Lines changed: 6 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -1,78 +1,21 @@
11
---
22
title: Metabase
3-
description: Connect Metabase to Datadog Data Observability to view end-to-end lineage from warehouse tables to dashboards.
3+
description: Metabase integration for Data Observability lineage. See the integration documentation for setup.
44
further_reading:
55
- link: '/data_observability/'
66
tag: 'Documentation'
77
text: 'Learn about Data Observability'
88
---
99

10-
## Overview
10+
Datadog's Metabase integration helps data teams make changes to their data platform without breaking Metabase dashboards, and identify unused cards or dashboards. The integration also collects Metabase activity, view, and query logs.
1111

12-
Datadog's Metabase integration helps data teams make changes to their data platform without breaking Metabase dashboards, and identify unused cards or dashboards. When Datadog connects, it:
12+
Lineage is derived from your data warehouse, so you also need at least one [supported data warehouse destination][2] connected to Datadog. Log collection has no such requirement.
1313

14-
- Pulls metadata from your Metabase environment, including cards and dashboards.
15-
- Automatically generates lineage from warehouse tables and columns to downstream Metabase cards, as well as from those cards to downstream dashboards.
16-
17-
## Connect Metabase
18-
19-
### Prerequisites
20-
21-
This integration requires a Metabase Pro or Enterprise plan.
22-
23-
### Generate an API key
24-
25-
Follow [Metabase's API documentation][1] to generate an API key.
26-
27-
### Get DNS alias (required for cloud instances only)
28-
29-
1. Log into your Metabase cloud instance as an administrator.
30-
1. Click on the gear icon in the upper right corner.
31-
1. Select {{< ui >}}Admin settings{{< /ui >}}.
32-
1. Go to the {{< ui >}}Settings{{< /ui >}} tab.
33-
1. Click on the {{< ui >}}Cloud{{< /ui >}} tab from the left menu.
34-
1. Click on {{< ui >}}Go to the Metabase Store{{< /ui >}}.
35-
1. Log into your Metabase Store using Metabase credentials.
36-
1. Go to the {{< ui >}}Instances{{< /ui >}} tab.
37-
1. Click on the DNS alias section to get the DNS alias value.
38-
39-
### Get self-hosted instance domain (required for self-hosted instances only)
40-
41-
**Note**: Your self-hosted Metabase instance must be accessible from the internet through HTTPS only.
42-
43-
1. Log in to your Metabase instance as an administrator.
44-
1. Click on the gear icon in the upper right corner.
45-
1. Select {{< ui >}}Admin settings{{< /ui >}}.
46-
1. Go to the {{< ui >}}Settings{{< /ui >}} tab.
47-
1. Click on the {{< ui >}}General{{< /ui >}} tab from the left menu.
48-
1. Under {{< ui >}}SITE URL{{< /ui >}}, copy the domain portion of the URL. For example, if the URL is `https://example.com`, copy `example.com`.
49-
50-
### Add the Metabase integration
51-
52-
1. Navigate to the [Metabase integration tile][2] and enter the following information:
53-
54-
| Parameter | Description |
55-
|-----------|-------------|
56-
| Account name | Datadog-only account name associated with these credentials. |
57-
| Instance type | The hosting type of your Metabase instance. Valid values are `cloud` or `self-hosted`. Default is `cloud`. |
58-
| 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. |
59-
| 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`). |
60-
| Metabase API key | The API key used to authenticate the API requests. |
61-
62-
2. After you've entered these credentials, click {{< ui >}}Save{{< /ui >}}.
63-
64-
## What's next
65-
66-
When your Metabase account is successfully connected, Datadog syncs and automatically derives lineage from warehouse tables/columns to Metabase cards and dashboards.
67-
68-
Initial syncs may take up to several hours depending on the size of your Metabase deployment.
69-
70-
After syncing, you can explore your Metabase assets and their upstream dependencies in the [Data Observability Catalog][3].
14+
See the [Metabase integration][1] documentation for setup and configuration.
7115

7216
## Further reading
7317

7418
{{< partial name="whats-next/whats-next.html" >}}
7519

76-
[1]: https://www.metabase.com/docs/latest/people-and-groups/api-keys#create-an-api-key
77-
[2]: https://app.datadoghq.com/integrations/metabase
78-
[3]: https://app.datadoghq.com/data-obs/catalog
20+
[1]: /integrations/metabase/
21+
[2]: /data_observability/quality_monitoring/data_warehouses/
Lines changed: 6 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -1,78 +1,21 @@
11
---
22
title: Power BI
3-
description: Connect Power BI to Datadog Data Observability to view end-to-end lineage from warehouse tables to dashboards.
3+
description: Power BI integration for Data Observability lineage. See the integration documentation for setup.
44
further_reading:
55
- link: '/data_observability/'
66
tag: 'Documentation'
77
text: 'Learn about Data Observability'
88
---
99

10-
## Overview
10+
Datadog's Power BI integration helps data teams make changes to their data platform without breaking dashboards, and identify unused reports and dashboards to remove.
1111

12-
Datadog's Power BI integration helps data teams make changes to their data platform without breaking dashboards, and identify unused reports and dashboards to remove. When Datadog connects, it:
12+
Lineage is derived from your data warehouse, so you also need at least one [supported data warehouse destination][2] connected to Datadog.
1313

14-
- Pulls metadata from your Power BI account like datasets, reports, and dashboards.
15-
- Automatically generates lineage between warehouse tables with downstream datasets, reports, and dashboards.
16-
17-
## Connect Power BI
18-
19-
### Create an app registration and security group
20-
21-
#### App registration
22-
23-
1. Sign into Microsoft Azure.
24-
2. Search for {{< ui >}}App registrations{{< /ui >}}.
25-
3. Click {{< ui >}}New registration{{< /ui >}}.
26-
4. Fill in the required fields and register an application for Datadog.
27-
5. Copy the Application (client) ID somewhere safe.
28-
6. Go to {{< ui >}}Certificates & secrets{{< /ui >}} in sidebar and click {{< ui >}}New client secret{{< /ui >}}.
29-
7. Add a secret for Datadog.
30-
8. Copy the secret value somewhere safe.
31-
32-
#### Security group
33-
34-
1. Search for {{< ui >}}Azure Active Directory{{< /ui >}}.
35-
2. Go to {{< ui >}}Groups{{< /ui >}} in the sidebar and click {{< ui >}}New group{{< /ui >}}.
36-
3. Create a group for the app registration.
37-
4. Click into the newly created group. You may need to refresh the page for it to show up.
38-
5. Go to {{< ui >}}Members{{< /ui >}} in the sidebar and click {{< ui >}}Add members{{< /ui >}}.
39-
6. Find the app registration created earlier and add it as a member.
40-
41-
### Grant access in Power BI
42-
43-
#### Enable API and admin API access for security group in Power BI Admin
44-
45-
1. Go to the Power BI Admin portal.
46-
2. In Tenant settings, enable {{< ui >}}Service principals can call Fabric APIs{{< /ui >}} for your security group.
47-
3. In Tenant settings, find {{< ui >}}Admin API settings{{< /ui >}}.
48-
4. Enable the following for your security group:
49-
- {{< ui >}}Allow service principals to use read-only admin APIs{{< /ui >}}
50-
- {{< ui >}}Enhance admin APIs responses with detailed metadata{{< /ui >}}
51-
- {{< ui >}}Enhance admin APIs responses with DAX and mashup expressions{{< /ui >}}
52-
53-
#### Grant access to workspaces
54-
55-
From the Power BI Admin portal:
56-
57-
1. From the sidebar, click {{< ui >}}Workspaces{{< /ui >}} to open the Workspaces pane.
58-
2. Grant Viewer permissions to the service principal in each workspace you want Datadog to have access to.
59-
60-
### Add the Power BI integration
61-
62-
1. Navigate to the [Power BI integration tile][1] and enter your tenant ID, and the client ID and secret from earlier.
63-
2. After you've entered these credentials, click {{< ui >}}Save{{< /ui >}}.
64-
65-
## What's next
66-
67-
When your Power BI account is successfully connected, Datadog syncs and automatically derives lineage from warehouse tables/columns to Power BI datasets, reports, and dashboards.
68-
69-
Initial syncs may take up to several hours depending on the size of your Power BI deployment.
70-
71-
After syncing, you can explore your Power BI assets and their upstream dependencies in the [Data Observability Catalog][2].
14+
See the [Power BI integration][1] documentation for setup and configuration.
7215

7316
## Further reading
7417

7518
{{< partial name="whats-next/whats-next.html" >}}
7619

77-
[1]: https://app.datadoghq.com/integrations/power-bi
78-
[2]: https://app.datadoghq.com/data-obs/catalog
20+
[1]: /integrations/power-bi/
21+
[2]: /data_observability/quality_monitoring/data_warehouses/
Lines changed: 6 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,49 +1,21 @@
11
---
22
title: Sigma
3-
description: Connect Sigma to Datadog Data Observability to view end-to-end lineage from warehouse tables to workbooks.
3+
description: Sigma integration for Data Observability lineage. See the integration documentation for setup.
44
further_reading:
55
- link: '/data_observability/'
66
tag: 'Documentation'
77
text: 'Learn about Data Observability'
88
---
99

10-
## Overview
10+
Datadog's Sigma integration helps data teams make changes to their data platform without breaking Sigma workbooks, and identify unused workbooks or datasets.
1111

12-
Datadog's Sigma integration helps data teams make changes to their data platform without breaking Sigma workbooks, and identify unused workbooks or datasets. When Datadog connects, it:
12+
Lineage is derived from your data warehouse, so you also need at least one [supported data warehouse destination][2] connected to Datadog.
1313

14-
- Pulls metadata from your Sigma site, including workbooks and queries.
15-
- Automatically generates lineage between warehouse tables and columns and downstream Sigma datasets and workbooks.
16-
17-
## Connect Sigma
18-
19-
### Retrieve API keys
20-
21-
Follow [Sigma's API client instructions][1] to retrieve a Client ID and Client Secret (also called an API token).
22-
23-
### Add the Sigma integration
24-
25-
1. Navigate to the [Sigma integration tile][2] and enter the following information:
26-
27-
- Account name
28-
- Client ID
29-
- Client secret
30-
- Cloud provider. If you don't know your cloud provider, you can find it using Sigma's [Supported cloud platforms and regions documentation][3].
31-
32-
2. After you've entered these credentials, click {{< ui >}}Save{{< /ui >}}.
33-
34-
## What's next
35-
36-
When your Sigma account is successfully connected, Datadog syncs and automatically derives lineage from warehouse tables/columns to Sigma workbooks.
37-
38-
Initial syncs may take up to several hours depending on the size of your Sigma deployment.
39-
40-
After syncing, you can explore your Sigma assets and their upstream dependencies in the [Data Observability Catalog][4].
14+
See the [Sigma integration][1] documentation for setup and configuration.
4115

4216
## Further reading
4317

4418
{{< partial name="whats-next/whats-next.html" >}}
4519

46-
[1]: https://help.sigmacomputing.com/reference/generate-client-credentials
47-
[2]: https://app.datadoghq.com/integrations/sigma-computing
48-
[3]: https://help.sigmacomputing.com/docs/region-warehouse-and-feature-support#supported-cloud-platforms-and-regions
49-
[4]: https://app.datadoghq.com/data-obs/catalog
20+
[1]: /integrations/sigma-computing/
21+
[2]: /data_observability/quality_monitoring/data_warehouses/
Lines changed: 6 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -1,62 +1,21 @@
11
---
22
title: Tableau
3-
description: Connect Tableau to Datadog Data Observability to view end-to-end lineage from warehouse tables to dashboards.
3+
description: Tableau integration for Data Observability lineage. See the integration documentation for setup.
44
further_reading:
55
- link: '/data_observability/'
66
tag: 'Documentation'
77
text: 'Learn about Data Observability'
88
---
99

10-
## Overview
10+
Datadog's Tableau integration helps data teams make changes to their data platform without breaking dashboards, and identify unused workbooks and data sources to remove.
1111

12-
Datadog's Tableau integration helps data teams make changes to their data platform without breaking dashboards, and identify unused workbooks and data sources to remove. When Datadog connects, it:
12+
Lineage is derived from your data warehouse, so you also need at least one [supported data warehouse destination][2] connected to Datadog.
1313

14-
- Pulls metadata from your Tableau site like fields, worksheets, dashboards, workbooks, and data sources
15-
- Automatically generates lineage between warehouse tables/columns with downstream Tableau fields, worksheets, dashboards, and workbooks.
16-
17-
## Connect Tableau
18-
19-
### Tableau requirements
20-
21-
In order for Datadog to extract your metadata from Tableau, you must meet all of the [Tableau Metadata GraphQL][1] requirements:
22-
23-
- Tableau Cloud/Server v2019.3+
24-
- Tableau REST API must be enabled
25-
- The Metadata API must be [enabled][2]
26-
27-
### Create a personal access token
28-
29-
For details on how to create a Personal Access Token (PAT), see the [Tableau Documentation][3]. Scope the PAT to the target site if needed.
30-
31-
### Add the Tableau integration
32-
33-
To connect Tableau to Datadog:
34-
35-
1. Navigate to the [Tableau integration tile][4] and enter the following information:
36-
37-
- Account name (for use within Datadog only)
38-
- Site name (optional, leave blank to use the default site)
39-
- Server version (example: 2025.2.0). Find this in your Tableau Server or Cloud admin settings.
40-
- Server endpoint (example: https://prod-useast-b.online.tableau.com)
41-
- Token name
42-
- Token value
43-
44-
2. After you've entered these credentials, click {{< ui >}}Save{{< /ui >}}.
45-
46-
## What's next
47-
48-
When your Tableau account is successfully connected, Datadog syncs and automatically derives lineage from warehouse tables/columns to Tableau fields, worksheets, dashboards, workbooks, and data sources.
49-
50-
Initial syncs may take up to several hours depending on the size of your Tableau deployment.
51-
52-
After syncing, you can explore your Tableau assets and their upstream dependencies in the [Data Observability Catalog][5].
14+
See the [Tableau integration][1] documentation for setup and configuration.
5315

5416
## Further reading
5517

5618
{{< partial name="whats-next/whats-next.html" >}}
5719

58-
[1]: https://help.tableau.com/current/api/metadata_api/en-us/index.html#metadata-api-and-graphql
59-
[2]: https://help.tableau.com/current/api/metadata_api/en-us/docs/meta_api_start.html#enable-the-tableau-metadata-api-for-tableau-server
60-
[3]: https://help.tableau.com/current/pro/desktop/en-us/useracct.htm#create-and-revoke-personal-access-tokens
61-
[4]: https://app.datadoghq.com/integrations/tableau
62-
[5]: https://app.datadoghq.com/data-obs/catalog
20+
[1]: /integrations/tableau/
21+
[2]: /data_observability/quality_monitoring/data_warehouses/

0 commit comments

Comments
 (0)