mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
bf5a729f2d
## Summary - Renames the **Telemetry** nav section to **Monitoring and Debugging** (nav label + sidebar title) - Rewrites the section overview (`telemetry.mdx`) as a clean navigation page using `ContentListings` — three panels (Debugging / Monitoring / AI & automation) with no how-to prose - Adds new `telemetry.data.ts` content-listings data file with three groups registered in `index.ts` - Adds a new **Debugging** guide (`debugging.mdx`) — request-stack model, symptom-to-layer router with troubleshooting links for every service, logging guidance - Adds cross-links between `debugging.mdx`, `logs.mdx`, and `advanced-log-filtering.mdx` - Adds a new **AI agents and MCP** page (`ai-agents.mdx`) — MCP tools table, `get_logs` usage, debugging skill workflow - Restructures sidebar into three groups: **Debugging** / **Monitoring** / **AI & automation** ## Motivation - No central entry point existed for debugging — content was scattered across products with no index - The overview page had almost no links for agents to follow - The section name "Telemetry" caused confusion (also used for CLI usage telemetry) - Unblocks the `supabase` debugging skill, which routes agents to this section as its source of truth ## Test plan - [ ] `/docs/guides/telemetry` — three ContentListings panels render, no prose how-to text - [ ] `/docs/guides/telemetry.md` (markdown) — clean link list, navigable by LLMs - [ ] `/docs/guides/telemetry/debugging` — renders correctly, symptom table links resolve - [ ] `/docs/guides/telemetry/ai-agents` — new page renders correctly - [ ] Sidebar shows 3 groups: Debugging / Monitoring / AI & automation - [ ] All cross-links between debugging, logs, and advanced-log-filtering resolve <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Summary - **New Features** - Added new documentation coverage for AI agent–assisted monitoring and debugging, including an observability-driven troubleshooting workflow. - **Documentation** - Updated the “Telemetry” area to “Monitoring and Debugging” with a refreshed landing page and reorganized sections (Debugging, Monitoring, and AI). - Revised the debugging and logs guides to improve step-by-step guidance and highlight advanced log filtering. - **Navigation** - Renamed and restructured the top-level navigation entry to reflect the new Monitoring and Debugging content layout. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Jeremias Menichelli <jmenichelli@gmail.com>
65 lines
2.6 KiB
TypeScript
65 lines
2.6 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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/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/monitoring-and-debugging/log-drains#syslog',
|
|
icon: { kind: 'server', color: '#64748B', bg: 'rgba(100,116,139,0.1)' },
|
|
},
|
|
],
|
|
}
|