[SIMI-271] Supabase Cloud: Dashboard, logs, and monitors #22339
Conversation
datadog-agent-integrations-bot
bot
added
documentation
qa/skip-qa
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
![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: e8fbfee510
ℹ️ 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".
supabase_cloud/assets/monitors/supabase_postgres_server_high_load.json
Outdated
Show resolved
Hide resolved
bskinny
force-pushed
the
external-pr/supabase-assets
branch
from
e8fbfee to
966bb6a
Compare
joepeeples
added
the
editorial review
|
Opened DOCS-13130 to assign a Docs writer and follow up with editorial review. |
bskinny
force-pushed
the
external-pr/supabase-assets
branch
4 times, most recently
from
2776a8c to
cccd5d4
Compare
bskinny
force-pushed
the
external-pr/supabase-assets
branch
from
cccd5d4 to
aecb189
Compare
bskinny
changed the title
bskinny
force-pushed
the
external-pr/supabase-assets
branch
from
b1c6265 to
3c13b24
Compare
bskinny
force-pushed
the
external-pr/supabase-assets
branch
from
3c13b24 to
176bb97
Compare
bskinny
force-pushed
the
external-pr/supabase-assets
branch
2 times, most recently
from
e37d98a to
176bb97
Compare
evazorro
left a comment
evazorro
left a comment
There was a problem hiding this comment.
Left some feedback on monitor titles and descriptions. Let me know if you have any questions!
| "version": 2, | ||
| "created_at": "2026-01-08", | ||
| "last_updated_at": "2026-01-08", | ||
| "title": "Postgres Server Filesystem Size Exceeds Alert Threshold", |
There was a problem hiding this comment.
Not feedback on this specific PR, but related to some other documentation I'm working on: are there guidelines for monitor titles and descriptions written out somewhere that you follow? In the official docs, on the wiki, somewhere else?
There was a problem hiding this comment.
Hi @evazorro Thanks for calling this out. I have been loosely referencing existing integrations, and in this case referenced one with non-sentence casing in the titles. I tend to elaborate in the description but a couple of these seem so self-explanatory I failed to come up with anything useful. Will look again.
There was a problem hiding this comment.
Makes sense, thank you! I'm adding some guidelines to the integration developer docs and was curious if there are other docs elsewhere I should reference or combine.
supabase_cloud/assets/monitors/supabase_postgres_filesystem_size.json
Outdated
Show resolved
Hide resolved
supabase_cloud/assets/monitors/supabase_postgres_server_high_load.json
Outdated
Show resolved
Hide resolved
supabase_cloud/assets/monitors/supabase_postgres_server_high_load.json
Outdated
Show resolved
Hide resolved
| "created_at": "2026-01-08", | ||
| "last_updated_at": "2026-01-08", | ||
| "title": "Postgres Server Filesystem Size Exceeds Alert Threshold", | ||
| "description": "The Postgres server filesystem usage is above the alert threshold.", |
There was a problem hiding this comment.
The description should ideally not just restate the title; is there additional detail you can add here?
Example of a good monitor description (for title "Unacknowledged messages are higher than usual"):
Unacked messages are those that have been delivered to a consumer but have not been acknowledged as processed or handled. This monitor tracks the ratio of unacked messages to avoid potential bottlenecks which could lead to delays in message processing.
supabase_cloud/assets/monitors/supabase_postgres_server_offline.json
Outdated
Show resolved
Hide resolved
| "created_at": "2026-01-08", | ||
| "last_updated_at": "2026-01-08", | ||
| "title": "Postgres Server is Offline", | ||
| "description": "The Postgres server is offline.", |
There was a problem hiding this comment.
Same comment on description here too
There was a problem hiding this comment.
@evazorro Just updated three of the descriptions.
There was a problem hiding this comment.
These look great, thank you so much for updating!
temporal-github-worker-1
bot
added
docs/requested-changes
and removed
docs/review-requested
labels
Co-authored-by: Eva Parish <eva.parish@datadoghq.com>
temporal-github-worker-1
bot
added
docs/approved
and removed
docs/requested-changes
labels
4 participants
New integration, Supabase Cloud, assets for initial release.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged