mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 02:45:07 +03:00
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Stack Draft stack extracted from `docs/monitoring`. Merge bottom-up. The troubleshooting *catalog* rewrite (`content/troubleshooting` and the Diagnosing UI) stays out of scope. 1. #49503 move inspect and advisors 2. #49501 split Studio logs from ClickHouse queries 3. #49500 treat reports as signal dashboards 4. #49502 add Observe the data hub 5. #49506 add agent setup components 6. #49504 add hire-an-agent templates 7. **#49505** restructure observability nav, overview, Detecting, and flatten Observe the data ← **this PR** ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Docs update. Top layer in the observability stack. ## What is the current behavior? The section is still titled Monitoring and Debugging, with a Debugging / Monitoring split that does not match the new pages. The debugging guide is still the master layer-isolation + symptom table. Observe the data is split into “what data” vs “where to observe it,” which duplicates the source pages. ## What is the new behavior? - Section title is Observability - Overview groups Observe the data, Detect and resolve, Hire an agent, and Export - **Observe the data is flattened by source.** Logs, Metrics API, Database, Advisors, and Reports each list where to read that source. There is no separate MCP/API/CLI/Studio nav group. - **Observe vs Detecting:** Observe is the catalog (what exists, how to access it). Detecting is how to *use* those sources to pick up a Health / Security / Performance / Usage signal. Named errors skip to Diagnosing. - Studio Logs sits under Logs. Reports sits beside the other sources. - Troubleshooting stays in the global menu and also appears as Diagnosing under Detect and resolve ## Additional context This is the last PR in the stack. Together the seven PRs reconstruct the `docs/monitoring` observability IA and guide content, without shipping the troubleshooting catalog overhaul. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-a3cb5ece-925b-4046-b58a-5d69e9a9d794?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-a3cb5ece-925b-4046-b58a-5d69e9a9d794&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Saxon Fletcher <SaxonF@users.noreply.github.com> Co-authored-by: Nik Richers <nik@validmind.ai>
75 lines
2.1 KiB
Plaintext
75 lines
2.1 KiB
Plaintext
---
|
|
id: 'storage-logs'
|
|
title: 'Logs'
|
|
description: 'Learn how to check Storage Logs'
|
|
sidebar_label: 'Debugging'
|
|
---
|
|
|
|
The [Storage Logs](/dashboard/project/_/logs/storage-logs) provide a convenient way to examine all incoming request logs to your Storage service. You can filter by time and keyword searches.
|
|
|
|
For more advanced filtering needs, use the [SQL Editor](/dashboard/project/_/sql/new?skip=true&source=logs) with the query source set to **Logs** to query the Storage logs directly. A Logs query runs ClickHouse SQL rather than Postgres SQL. Every log line is a row in the `logs` table, tagged by a `source` column, with structured fields in a `log_attributes` map.
|
|
|
|
<Admonition type="note">
|
|
|
|
For more details on filtering the log tables, see [Query and filter logs](/docs/guides/observability/advanced-log-filtering)
|
|
|
|
</Admonition>
|
|
|
|
## Example Storage queries
|
|
|
|
### Filter by status 5XX error
|
|
|
|
```sql
|
|
select
|
|
id,
|
|
timestamp,
|
|
event_message,
|
|
toInt32OrZero(log_attributes['res.statusCode']) as statusCode,
|
|
log_attributes['error.message'] as errorMessage,
|
|
log_attributes['error.raw'] as rawError
|
|
from logs
|
|
where source = 'storage_logs'
|
|
and toInt32OrZero(log_attributes['res.statusCode']) >= 500
|
|
order by timestamp desc
|
|
limit 100;
|
|
```
|
|
|
|
### Filter by status 4XX error
|
|
|
|
```sql
|
|
select
|
|
id,
|
|
timestamp,
|
|
event_message,
|
|
toInt32OrZero(log_attributes['res.statusCode']) as statusCode,
|
|
log_attributes['error.message'] as errorMessage,
|
|
log_attributes['error.raw'] as rawError
|
|
from logs
|
|
where source = 'storage_logs'
|
|
and toInt32OrZero(log_attributes['res.statusCode']) between 400 and 499
|
|
order by timestamp desc
|
|
limit 100;
|
|
```
|
|
|
|
### Filter by method
|
|
|
|
```sql
|
|
select id, timestamp, event_message, log_attributes['req.method'] as method
|
|
from logs
|
|
where source = 'storage_logs'
|
|
and log_attributes['req.method'] in ('POST')
|
|
order by timestamp desc
|
|
limit 100;
|
|
```
|
|
|
|
### Filter by IP address
|
|
|
|
```sql
|
|
select id, timestamp, event_message, log_attributes['req.remoteAddress'] as remoteAddress
|
|
from logs
|
|
where source = 'storage_logs'
|
|
and log_attributes['req.remoteAddress'] in ('IP_ADDRESS')
|
|
order by timestamp desc
|
|
limit 100;
|
|
```
|