From 8cedf11e8bd6eee0ecfe89fbccbea217e3783fb0 Mon Sep 17 00:00:00 2001 From: Steven Eubank <47563310+smeubank@users.noreply.github.com> Date: Fri, 19 Dec 2025 14:46:04 +0100 Subject: [PATCH] fix(docs)bad-links (#41489) * fix(docs)bad-links These links are not routing correctly. It was also discussed that such a UI feature in docs should be discussed an implemented in way that could be scaled out more anyway. * Prettier --------- Co-authored-by: Chris Chinchilla --- apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx | 2 -- .../content/guides/telemetry/metrics/grafana-self-hosted.mdx | 2 -- apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx | 2 -- 3 files changed, 6 deletions(-) diff --git a/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx b/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx index 275fedf70a6..7441f959c61 100644 --- a/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx +++ b/apps/docs/content/guides/telemetry/metrics/grafana-cloud.mdx @@ -59,5 +59,3 @@ The [`docs/example-alerts.md`](https://github.com/supabase/supabase-grafana/blob - Metrics missing? Ensure the Grafana Cloud agent can reach `https://.supabase.co` and that the selected service role key is still valid. - 401 errors? Rotate the service role key from the [API settings page](/dashboard/project/_/settings/api-keys) and update the Grafana Cloud credentials. - Long scrape durations? Reduce label cardinality in your Grafana queries or lower the time range to focus on recent data. - -[← Back to the Metrics API landing](/guides/telemetry/metrics) diff --git a/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx b/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx index ba6c02670ef..fea8055e4e9 100644 --- a/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx +++ b/apps/docs/content/guides/telemetry/metrics/grafana-self-hosted.mdx @@ -80,5 +80,3 @@ You now have over 200 production-ready panels covering CPU, IO, WAL, replication - **Multiple projects:** add one scrape job per project ref so you can separate metrics and labels cleanly. - **Right-sizing guidance:** pair the dashboards with Supabase’s [Query Performance report](/dashboard/project/_/observability/query-performance) and [Advisors](/dashboard/project/_/observability/database) to decide when to optimize vs upgrade. - **Security:** rotate the service role key on a regular cadence and update the Prometheus config accordingly. - -[← Back to the Metrics API landing](/guides/telemetry/metrics) diff --git a/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx b/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx index 0b766eb3ea3..611009bab8a 100644 --- a/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx +++ b/apps/docs/content/guides/telemetry/metrics/vendor-agnostic.mdx @@ -68,5 +68,3 @@ No matter which collector you use, you need to hit the Metrics API once per minu - Create one scrape job per project ref so you can control sampling individually. - If you run many projects, consider templating the scrape jobs via Helm, Terraform, or the Grafana Agent Operator. - Use label joins (`project`, `instance_class`, `org`) to aggregate across tenants or environments. - -[← Back to the Metrics API landing](/guides/telemetry/metrics)