mirror of
https://github.com/supabase/supabase.git
synced 2026-09-06 09:59:03 +08:00
e0280cb650
<!-- 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>
65 lines
2.5 KiB
TypeScript
65 lines
2.5 KiB
TypeScript
import type { ContentListingGroup } from '~/lib/content-listings.schema'
|
|
|
|
export const logDrainsDestinations: ContentListingGroup = {
|
|
id: 'log-drains-destinations',
|
|
heading: 'Choose your destination',
|
|
type: 'grid',
|
|
columns: 3,
|
|
items: [
|
|
{
|
|
title: 'Custom Endpoint',
|
|
description: 'Forward logs as a POST request to any custom HTTP endpoint.',
|
|
href: '/guides/observability/log-drains#custom-endpoint',
|
|
icon: { kind: 'braces', color: '#3ECF8E', bg: 'rgba(62,207,142,0.1)' },
|
|
},
|
|
{
|
|
title: 'OpenTelemetry (OTLP)',
|
|
description: 'Send logs to any OTLP-compatible endpoint using Protocol Buffers over HTTP.',
|
|
href: '/guides/observability/log-drains#opentelemetry-otlp',
|
|
icon: { kind: 'otlp', color: '#F5A623', bg: 'rgba(245,166,35,0.1)' },
|
|
},
|
|
{
|
|
title: 'Datadog',
|
|
description: 'Stream logs directly into Datadog for monitoring and analysis.',
|
|
href: '/guides/observability/log-drains#datadog',
|
|
icon: { kind: 'datadog', color: '#632CA6', bg: 'rgba(99,44,166,0.1)' },
|
|
},
|
|
{
|
|
title: 'Loki',
|
|
description: 'Ingest logs into Grafana Loki using the HTTP push API.',
|
|
href: '/guides/observability/log-drains#loki',
|
|
icon: { kind: 'grafana', color: '#F05A28', bg: 'rgba(240,90,40,0.1)' },
|
|
},
|
|
{
|
|
title: 'Amazon S3',
|
|
description: 'Write batched log files directly to an S3 bucket you own.',
|
|
href: '/guides/observability/log-drains#amazon-s3',
|
|
icon: { kind: 'cloud', color: '#FF9900', bg: 'rgba(255,153,0,0.1)' },
|
|
},
|
|
{
|
|
title: 'Sentry',
|
|
description: "Send logs to Sentry's Logging product for filtering and grouping.",
|
|
href: '/guides/observability/log-drains#sentry',
|
|
icon: { kind: 'sentry', color: '#362D59', bg: 'rgba(54,45,89,0.1)' },
|
|
},
|
|
{
|
|
title: 'Axiom',
|
|
description: 'Forward logs to an Axiom dataset for storage and analysis.',
|
|
href: '/guides/observability/log-drains#axiom',
|
|
icon: { kind: 'axiom', color: '#6366F1', bg: 'rgba(99,102,241,0.1)' },
|
|
},
|
|
{
|
|
title: 'Last9',
|
|
description: 'Stream logs to Last9 for OpenTelemetry-native observability.',
|
|
href: '/guides/observability/log-drains#last9',
|
|
icon: { kind: 'last9', color: '#00B4A0', bg: 'rgba(0,180,160,0.1)' },
|
|
},
|
|
{
|
|
title: 'Syslog',
|
|
description: 'Forward logs to a remote Syslog receiver over TCP or TLS (RFC 5424).',
|
|
href: '/guides/observability/log-drains#syslog',
|
|
icon: { kind: 'server', color: '#64748B', bg: 'rgba(100,116,139,0.1)' },
|
|
},
|
|
],
|
|
}
|