Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
131e6e8
Add Supabase link to DBM Postgres setup page
dalextorres Mar 13, 2026
21c79c6
Add Supabase Cloud DBM setup page and restructure Supabase docs
dalextorres Mar 13, 2026
47a494c
Add dbm_postgres_supabase to left-nav level-4 allowlist
dalextorres Mar 13, 2026
27245e4
Fix Supabase integration tile URL to supabase-cloud
dalextorres Mar 13, 2026
d84b566
Add first instance free callout and per-project config note
dalextorres Mar 13, 2026
8af7bb0
Add Supabase Cloud integration tile and product screenshots
dalextorres Mar 13, 2026
6a51296
Update Supabase Cloud integration tile screenshot
dalextorres Mar 13, 2026
afed047
Remove free instance language, keep per-project config note
dalextorres Mar 13, 2026
1c6861c
Merge master: resolve left-nav allowlist conflict
dalextorres Mar 13, 2026
4636609
Update Supabase Cloud integration tile screenshot with new API key field
dalextorres Mar 16, 2026
a380e48
Update Supabase Cloud integration tile screenshot
dalextorres Mar 16, 2026
bf2cbbd
Restructure Supabase DBM docs with landing page
dalextorres Mar 18, 2026
a6bf3c7
Fix database instance metadata collection interval to 5 minutes
dalextorres Mar 18, 2026
b7b84da
Add Supabase logo to landing page cards
dalextorres Mar 18, 2026
c16a7e5
Add Recommended badge to Supabase Cloud card
dalextorres Mar 18, 2026
2c689d4
Fix landing page cards to use inline img tags
dalextorres Mar 18, 2026
69b4fd6
Use parenthesized Recommended label on Supabase Cloud card
dalextorres Mar 18, 2026
0436be0
Add Supabase Cloud integration link to further reading
dalextorres Mar 18, 2026
025ffec
Use Hugo partial for Supabase landing page cards
dalextorres Mar 18, 2026
27a85d4
Fix database instance metadata collection interval to 30 seconds
dalextorres Mar 18, 2026
96068b1
Update database instance metadata collection interval to 5 minutes
dalextorres Mar 18, 2026
e67a648
Merge branch 'master' into alejandro.torres/add-supabase-link-dbm-pos…
jeff-morgan-dd Mar 19, 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
10 changes: 10 additions & 0 deletions config/_default/menus/main.en.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4680,6 +4680,16 @@ menu:
parent: dbm_setup_postgres
identifier: dbm_postgres_supabase
weight: 307
- name: Supabase Cloud
url: database_monitoring/setup_postgres/supabase
parent: dbm_postgres_supabase
identifier: dbm_supabase_cloud
Comment on lines +4697 to +4698

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add Supabase to level-4 sidebar allowlist

These new entries are attached under dbm_postgres_supabase, which creates a fourth navigation level, but the left-nav renderer hides level-4 submenus with d-none unless the parent identifier is explicitly allowlisted (layouts/partials/nav/left-nav.html, around lines 69-72, currently only includes dbm_setup_postgres_rds for this DBM section). Because dbm_postgres_supabase is not in that allowlist, the new “Supabase Cloud”/“Supabase Self-Hosted” items will not appear in the sidebar even when Supabase is expanded, so users can’t discover them through primary docs navigation.

Useful? React with 👍 / 👎.

weight: 1000
- name: Supabase Self-Hosted
url: database_monitoring/setup_postgres/supabase/agent
parent: dbm_postgres_supabase
identifier: dbm_supabase_agent
weight: 2000
- name: Heroku
url: database_monitoring/setup_postgres/heroku
parent: dbm_setup_postgres
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,71 @@
---
title: Setting Up Database Monitoring for Supabase Cloud
description: Install and configure Database Monitoring for Supabase with the Supabase Cloud integration.
further_reading:
- link: '/integrations/postgres/'
tag: 'Documentation'
text: 'Basic Postgres Integration'
- link: '/database_monitoring/setup_postgres/supabase/agent'
tag: 'Documentation'
text: 'Supabase Self-Hosted Setup (Agent Installation)'
---

Database Monitoring for Supabase Cloud provides visibility into your Supabase databases by exposing query performance metrics and query samples — without requiring a self-hosted Datadog Agent.

<div class="alert alert-info">For self-hosted Supabase deployments that require a Datadog Agent, see <a href="/database_monitoring/setup_postgres/supabase/agent">Supabase Self-Hosted Setup</a>.</div>

## Prerequisites

- A Supabase project with a Postgres database.
- Your Supabase **Project ID** (found in your Supabase project settings).
- Your Supabase **API key** (found in your Supabase project settings under **API**).
- A Supabase **Personal Access Token** with access to the Management API.

## Setup

1. Navigate to the [Supabase integration tile][1] in Datadog.
1. Click **Add Account**.
1. Enter your Supabase **Project ID** and **API Key**.
1. Select **Enable Database Monitoring for query performance optimizations**.
1. Enter your **Personal Access Token**.
1. Click **Save**.

Datadog connects to your Supabase project and begins collecting Database Monitoring telemetry. No Agent installation is required.

## Data collected

After you enable Database Monitoring, Datadog collects the following telemetry from your Supabase Cloud database:

### Query performance metrics
Sourced from `pg_stat_statements`, collected every 5 seconds:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to confirm that the 5 second interval here is hardcoded/not configurable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes its hardcoded for now, might make it configurable later but no plans for now

- Call count and rows processed
- Total and average execution time
- Shared and local buffer hit/read/dirty/write statistics
- Block I/O read and write time
- Temporary buffer read and write counts

### Query samples
Sourced from `pg_stat_activity`, collected every 5 seconds:
- Active and idle query snapshots
- Obfuscated query text and query signatures
- Wait event types and event names
- Session state and backend type
- Blocking PIDs
- Connection aggregates grouped by application, state, user, and database

### Database instance metadata
Collected every 5 seconds:
- PostgreSQL version
- Instance identifier and hostname
- Connection mode (direct or pooler)

## Validate

After setup, navigate to the [Database Monitoring][2] page in Datadog to see your Supabase database queries and performance metrics.

## Further reading

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

[1]: https://app.datadoghq.com/integrations/supabase
[2]: https://app.datadoghq.com/databases
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Setting Up Database Monitoring for Supabase
description: Install and configure Database Monitoring for Supabase.
title: Setting Up Database Monitoring for Supabase Self-Hosted
description: Install and configure Database Monitoring for Supabase with the Datadog Agent.
Comment on lines +2 to +3

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Stop labeling the cloud-oriented Agent guide as self-hosted

This rename makes the only Supabase Self-Hosted path point to instructions that still assume managed Supabase Cloud features: the same file later tells readers to use the Supabase SQL Editor and mentions the Pro-plan IPv4 add-on. Real self-hosted deployments do not have those dashboard controls or hosted-networking plans, so anyone choosing the new self-hosted option is sent to a setup flow they cannot actually follow.

Useful? React with 👍 / 👎.

further_reading:
- link: '/integrations/postgres/'
tag: 'Documentation'
Expand Down
7 changes: 7 additions & 0 deletions layouts/partials/dbm/dbm-setup-postgres.html
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,13 @@
</div>
</a>
</div>
<div class="col">
<a class="card h-100" href="/database_monitoring/setup_postgres/supabase">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the shared landing-page copy for the new agentless path

This Postgres card partial is reused on content/en/database_monitoring/_index.md, whose getting-started copy still says users must "configure your database and install the Datadog Agent" before choosing a Postgres setup. Adding the new Supabase entry here makes that statement wrong for the recommended Supabase Cloud flow, which content/en/database_monitoring/setup_postgres/supabase/cloud.md explicitly describes as requiring no Agent. Readers who start from the main DBM landing page now get contradictory setup guidance unless the shared intro is adjusted or this card is scoped to the Postgres-only chooser.

Useful? React with 👍 / 👎.

<div class="card-body text-center py-2 px-1">
{{ partial "img.html" (dict "root" . "src" "integrations_logos/supabase.png" "class" "img-fluid" "alt" "Supabase" "width" "175") }}
</div>
</a>
</div>
</div>

</div>
Expand Down
Binary file added static/images/integrations_logos/supabase.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading