Add Supabase Cloud DBM setup page and link to Postgres setup#35276
Add Supabase Cloud DBM setup page and link to Postgres setup#35276dalextorres wants to merge 22 commits intomasterfrom
Conversation
The Supabase setup guide existed but was not linked from the Postgres setup landing page. Add the card and logo. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Split Supabase DBM docs into two sub-pages mirroring the RDS pattern: - Supabase Cloud (_index.md): integration tile setup, no Agent required - Supabase Self-Hosted (agent.md): existing Agent-based setup Also adds Supabase Cloud and Supabase Self-Hosted menu entries. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
github-actions
bot
added
Architecture
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 21c79c64bf
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| parent: dbm_postgres_supabase | ||
| identifier: dbm_supabase_cloud |
There was a problem hiding this comment.
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 👍 / 👎.
Without this, the Supabase Cloud and Supabase Self-Hosted sub-menu items are hidden by d-none in the sidebar. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Preview links (active after the
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Keep both dbm_postgres_supabase (ours) and dev_tool_int_mcp_server (master). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Hi Alex, thank you for the PR! The content looks good, just a couple of structural items to address:
With the split page setup, two of the nav items (Supabase and Supabase Cloud) are now going to the same page (the Cloud page). We have 2 potential resolutions:
- (recommended) Turn the parent Supabase page (
supabase/_index.md) into a lightweight landing page. This could just entail a brief summary/overview of the Supabase setup options, and tiles for the Cloud and Self-Hosted pages, similar to the landing pages for Postgres, MySQL, etc. The existing Cloud sub-page would then need to be renamed something likesupabase/cloud.md. - Follow the RDS model and have a parent page and 1 sub-page (so i.e. the Cloud page could be the parent (
_index.html), and then self-hosted (agent.md) would be the single sub-page, or vice versa).
So the navigation would end up either:
- _index.md (Landing page)
-- cloud.md (Cloud page)
-- agent.md (Self-hosted page)
or
- _index.md (Cloud page)
-- agent.md (Self-hosted page)
(or vice versa)
We'll also need to add a redirect alias to the agent.md page, but I can help with that once we get the structure hashed out.
Please reach out on Slack if you want to jump on a call to discuss anything. Thank you!
| 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: |
There was a problem hiding this comment.
Just want to confirm that the 5 second interval here is hardcoded/not configurable.
There was a problem hiding this comment.
yes its hardcoded for now, might make it configurable later but no plans for now
Move Cloud content from _index.md to cloud.md and create a lightweight landing page with tiles for Cloud and Self-Hosted setup options. Update menu URL for Supabase Cloud accordingly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bf2cbbd556
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| title: Setting Up Database Monitoring for Supabase | ||
| description: Setting up Database Monitoring on a Supabase Postgres database. | ||
| disable_sidebar: true |
There was a problem hiding this comment.
In the parent revision, /database_monitoring/setup_postgres/supabase/ was the full self-hosted setup page and exposed anchors such as #grant-the-agent-access and #install-the-agent. Turning that same route into a chooser page means existing bookmarks, search results, or shared links to the old instructions now land on a page that has neither section, so previously published deep links stop working unless the old URL/anchors are preserved somehow.
Useful? React with 👍 / 👎.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c16a7e5e78
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| - 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**). |
There was a problem hiding this comment.
service_role key is required
Supabase exposes multiple project API keys under API; only the service_role key can read the hosted metrics endpoint that backs this integration. Describing the prerequisite as a generic “API key” will send many users to the anon/publishable key instead, and the new Cloud setup will fail even though they followed the page exactly. Please call out service_role here (and in the step at line 30) so the instructions are actionable for real projects.
Useful? React with 👍 / 👎.
Hugo shortcodes don't render inside raw HTML blocks in markdown, causing images to appear outside the cards. Use plain img tags instead. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 69b4fd6ad6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| 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**. |
There was a problem hiding this comment.
When a user follows this new Cloud setup flow exactly, the form shown just above still has an Account name field that the page never tells them to fill in. The screenshot’s own instruction panel lists that field as the first step, so readers who only enter Project ID, API key, and PAT may be unable to save the integration or at least won’t know what Datadog expects there.
Useful? React with 👍 / 👎.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0436be08fb
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| title: Setting Up Database Monitoring for Supabase Self-Hosted | ||
| description: Install and configure Database Monitoring for Supabase with the Datadog Agent. |
There was a problem hiding this comment.
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 👍 / 👎.
Inline img tags don't resolve correctly in the build pipeline. Use a dedicated partial like the other DBM setup pages do. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 025ffec30e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| </a> | ||
| </div> | ||
| <div class="col"> | ||
| <a class="card h-100" href="/database_monitoring/setup_postgres/supabase"> |
There was a problem hiding this comment.
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 👍 / 👎.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jeff-morgan-dd
left a comment
jeff-morgan-dd
left a comment
There was a problem hiding this comment.
Looks great! Thanks for making the updates.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e67a6486e9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| - link: '/integrations/supabase-cloud/' | ||
| tag: 'Documentation' | ||
| text: 'Supabase Cloud Integration' |
There was a problem hiding this comment.
The first further_reading entry points readers to /integrations/supabase-cloud/, but a repo-wide search only finds this new reference—there is no matching page or alias under content/en/integrations to serve that route. As written, anyone using the new Cloud setup page's “Supabase Cloud Integration” link will hit a missing internal docs page instead of the promised follow-up documentation.
Useful? React with 👍 / 👎.
3 participants
What does this PR do? What is the motivation?
/database_monitoring/setup_postgres/)static/images/integrations_logos/_index.md): Setup through the Supabase integration tile — no Agent requiredagent.md): Existing Agent-based setup (moved fromsupabase.md)Merge instructions
Merge readiness:
Additional notes
The Supabase Cloud page documents the integration tile flow (Project ID, API Key, Personal Access Token, "Enable Database Monitoring for query performance optimizations" checkbox) and the specific telemetry collected (query performance metrics, query samples, database instance metadata).
🤖 Generated with Claude Code