Files
supabase/apps/docs/data/content-listings/telemetry.data.ts
Steven EubankandClaude Sonnet 4.6 4730e3a640 docs: remove Generalist monitoring agent (#50784)
The Generalist is too broad and doesn't do any one thing well. Removing
it to focus on dogfooding the four targeted agents (Health, Security,
Performance, Capacity) before revisiting a combined agent.

https://github.com/supabase/supabase/pull/50396 new PR since this one
became messy with many upstream changes

## Problem

I don't like the generalist

## Solution

I am removing the generalist

<!--
## Preview links

If relevant, include links to changed pages for easy review access.

Copy the preview base URL from the Vercel bot comment on this PR. Use
the following table as an example template.

| Site | Live | Preview | Search for |
| -------------- |
-------------------------------------------------------------------------
|
------------------------------------------------------------------------------------------------------------
| ----------------------------- |
| WWW | [/blog/your-post](https://supabase.com/blog/your-post) |
[/blog/your-post](https://zone-www-dot-com-git-branch-name-supabase.vercel.app/blog/your-post)
| unique phrase from the change |
| Docs |
[/docs/guides/your-page](https://supabase.com/docs/guides/your-page) |
[/docs/guides/your-page](https://docs-git-branch-name-supabase.vercel.app/docs/guides/your-page)
| unique phrase from the change |
| Studio | [/dashboard](https://supabase.com/dashboard) |
[/dashboard](https://studio-git-branch-name-supabase.vercel.app/dashboard)
| unique phrase from the change |
| Design system | [/design-system](https://supabase.com/design-system) |
[/design-system](https://design-system-git-branch-name-supabase.vercel.app/design-system)
| unique phrase from the change |
| UI library | [/library](https://supabase.com/library) |
[/library](https://ui-library-git-branch-name-supabase.vercel.app/library)
| unique phrase from the change |
| Knowledge base |
[/kb/guides/your-page](https://supabase.com/kb/guides/your-page) |
[/kb/guides/your-page](https://kb-git-branch-name-supabase.vercel.app/kb/guides/your-page)
| unique phrase from the change |
-->

<!-- ## Additional context

Optionally add any other context or screenshots.

-->

## Review instructions

Simply removing generalist:

https://supabase.com/docs/guides/observability/automate-with-agents

<img width="305" height="339" alt="image"
src="https://github.com/user-attachments/assets/bb537038-799f-4ec6-a357-c4cb3c552cba"
/>

So generalist will be no mas

## Checklist

Check all before review:

- [x] I have read
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
- [x] If I wrote a new docs topic or edited an existing topic, I used
the `/write-the-docs` or `/edit-the-docs` skill, which references
[WORD_LIST](https://github.com/supabase/supabase/blob/master/apps/docs/WORD_LIST.md)
and the docs
[CONTRIBUTING](https://github.com/supabase/supabase/blob/master/apps/docs/CONTRIBUTING.md)
guide


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Removed the combined Generalist monitoring guide and its navigation
entry. Separate guides for health, security, performance, and usage
monitoring remain.
* The Generalist agent card and combined monitoring prompt are no longer
available.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-09-23 15:31:35 +02:00

133 lines
4.2 KiB
TypeScript

import { monitoringAgents } from '~/data/monitoring-agents.data'
import { getScheduleLabel } from '~/data/monitoring-agents.utils'
import type { ContentListingGroup } from '~/lib/content-listings.schema'
export const telemetryAccessWhat: ContentListingGroup = {
id: 'telemetry-access-what',
type: 'grid',
columns: 2,
items: [
{
title: 'Query logs with SQL',
href: '/guides/observability/advanced-log-filtering',
description: 'Query ClickHouse events through MCP, the API, or Explorer.',
},
{
title: 'Logs in Studio',
href: '/guides/observability/logs',
description: 'Filter, inspect, and export events in the unified Logs view.',
},
{
title: 'Log sources and fields',
href: '/guides/observability/log-field-reference',
description: 'Look up sources, ClickHouse query fields, and capture limits.',
},
{
title: 'Metrics API',
href: '/guides/observability/metrics',
description: 'Scrape Prometheus-compatible database metrics, or chart a subset in Reports.',
},
{
title: 'Inspect the database',
href: '/guides/observability/inspect',
description: 'Inspect live Postgres stats from the CLI, Explorer, or MCP.',
},
{
title: 'Advisors',
href: '/guides/observability/advisors',
description: 'Pull security and performance findings from Studio, MCP, the CLI, or the API.',
},
{
title: 'Reports',
href: '/guides/observability/reports',
description: 'Studio dashboards for API, Auth, Storage, Realtime, and database signals.',
},
],
}
export const telemetryDetect: ContentListingGroup = {
id: 'telemetry-detect',
type: 'grid',
items: [
{
title: 'Detect issues',
href: '/guides/observability/detecting',
description:
'Run health, security, performance, and capacity checks against logs and database statistics to pick up a signal.',
},
],
}
export const telemetryDiagnose: ContentListingGroup = {
id: 'telemetry-diagnose',
type: 'grid',
items: [
{
title: 'Diagnose and resolve',
href: '/guides/troubleshooting',
description:
'Use a concrete finding, symptom, or error code to identify the cause and apply a known solution.',
},
],
}
export const telemetryHireAgent: ContentListingGroup = {
id: 'telemetry-hire-agent',
type: 'grid',
columns: 2,
items: [
{
title: monitoringAgents.health.name,
href: '/guides/observability/automate-with-agents/health',
subtitle: getScheduleLabel(monitoringAgents.health),
description: 'Check API and Auth server errors and connection pressure.',
},
{
title: monitoringAgents.security.name,
href: '/guides/observability/automate-with-agents/security',
subtitle: getScheduleLabel(monitoringAgents.security),
description: 'Review advisor findings and authorization failures.',
},
{
title: monitoringAgents.performance.name,
href: '/guides/observability/automate-with-agents/performance',
subtitle: getScheduleLabel(monitoringAgents.performance),
description: 'Review sessions, query regressions, and performance advisors.',
},
{
title: monitoringAgents.usage.name,
href: '/guides/observability/automate-with-agents/usage',
subtitle: getScheduleLabel(monitoringAgents.usage),
description: 'Track sizes, connections, request growth, and supported forecasts.',
},
],
}
export const telemetryExport: ContentListingGroup = {
id: 'telemetry-export',
type: 'grid',
columns: 3,
items: [
{
title: 'Configure logging',
href: '/guides/observability/configure-logging',
description: 'Record additional Postgres and Realtime events.',
},
{
title: 'Log drains',
href: '/guides/observability/log-drains',
description: 'Send project logs to your own destination.',
},
{
title: 'Client-side tracing',
href: '/guides/observability/client-side-tracing',
description: 'Propagate W3C trace context from the client through Supabase services.',
},
{
title: 'Sentry integration',
href: '/guides/observability/sentry-monitoring',
description: 'Capture supabase-js errors and spans in Sentry.',
},
],
}