The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
docs: fix stale links to the Metrics guide after move to /telemetry (#46816)
SOUFIAN3HMebcd052018df
diff --git a/apps/docs/content/guides/database/connection-management.mdx b/apps/docs/content/guides/database/connection-management.mdxindex eab783c2928..48b2c4f1b7b 100644--- a/apps/docs/content/guides/database/connection-management.mdx+++ b/apps/docs/content/guides/database/connection-management.mdx@@ -51,7 +51,7 @@ For more details on using these monitoring charts, see the [Reports guide](/docs#### Grafana Dashboard-Supabase offers a Grafana Dashboard that records and visualizes over 200 project metrics, including connections. For setup instructions, check the [metrics docs](/docs/guides/platform/metrics).+Supabase offers a Grafana Dashboard that records and visualizes over 200 project metrics, including connections. For setup instructions, check the [metrics docs](/docs/guides/telemetry/metrics).Its "Client Connections" graph displays connections for both Supavisor and Postgresdiff --git a/apps/docs/content/guides/database/inspect.mdx b/apps/docs/content/guides/database/inspect.mdxindex 0f0fc5a3945..cce91f7b3b5 100644--- a/apps/docs/content/guides/database/inspect.mdx+++ b/apps/docs/content/guides/database/inspect.mdx@@ -262,4 +262,4 @@ Using the query plan analyzer to optimize your queries is a large topic, with a- [Postgres Wiki.](https://wiki.postgresql.org/wiki/Using_EXPLAIN)- [Enterprise DB.](https://www.enterprisedb.com/blog/postgresql-query-optimization-performance-tuning-with-explain-analyze)-You can pair the information available from `pg_stat_statements` with the detailed system metrics available [via your metrics endpoint](../platform/metrics) to better understand the behavior of your DB and the queries you're executing against it.+You can pair the information available from `pg_stat_statements` with the detailed system metrics available [via your metrics endpoint](../telemetry/metrics) to better understand the behavior of your DB and the queries you're executing against it.diff --git a/apps/docs/content/guides/platform/performance.mdx b/apps/docs/content/guides/platform/performance.mdxindex fbd2666be1d..1bc78848a4c 100644--- a/apps/docs/content/guides/platform/performance.mdx+++ b/apps/docs/content/guides/platform/performance.mdx@@ -29,7 +29,7 @@ In such a scenario, you can consider:### Configuring clients to use fewer connections-You can use the [pg_stat_activity](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW) view to debug which clients are holding open connections on your DB. `pg_stat_activity` only exposes information on direct connections to the database. Information on the number of connections to Supavisor is available [via the metrics endpoint](../platform/metrics).+You can use the [pg_stat_activity](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW) view to debug which clients are holding open connections on your DB. `pg_stat_activity` only exposes information on direct connections to the database. Information on the number of connections to Supavisor is available [via the metrics endpoint](../telemetry/metrics).Depending on the clients involved, you might be able to configure them to work with fewer connections (e.g. by imposing a limit on the maximum number of connections they're allowed to use), or shift specific workloads to connect via [Supavisor](/docs/guides/database/connecting-to-postgres#connection-pooler) instead. Transient workflows, which can quickly scale up and down in response to traffic (e.g. serverless functions), can especially benefit from using a connection pooler rather than connecting to the DB directly.diff --git a/apps/docs/content/guides/platform/read-replicas.mdx b/apps/docs/content/guides/platform/read-replicas.mdxindex f4e0da1ba04..2fb83ea8c4f 100644--- a/apps/docs/content/guides/platform/read-replicas.mdx+++ b/apps/docs/content/guides/platform/read-replicas.mdx@@ -151,7 +151,7 @@ For API logs, logs can originate from the API Load Balancer as well. The upstreaObservability and metrics for Read Replicas are available on the Supabase Dashboard. Resource utilization for a specific Read Replica can be viewed on the [Database Reports page](/dashboard/project/_/observability/database) by toggling for `Source`. Likewise, metrics on API requests going through either a Read Replica or Load Balancer API endpoint are also available on the dashboard through the [API Reports page](/dashboard/project/_/observability/api-overview)-We recommend ingesting your [project's metrics](/docs/guides/platform/metrics#accessing-the-metrics-endpoint) into your own environment. If you have an existing ingestion pipeline set up for your project, you can [update it](https://github.com/supabase/supabase-grafana?tab=readme-ov-file#read-replica-support) to additionally ingest metrics from your Read Replicas.+We recommend ingesting your [project's metrics](/docs/guides/telemetry/metrics) into your own environment. If you have an existing ingestion pipeline set up for your project, you can [update it](https://github.com/supabase/supabase-grafana?tab=readme-ov-file#read-replica-support) to additionally ingest metrics from your Read Replicas.### Centralized configuration managementdiff --git a/apps/docs/content/guides/platform/read-replicas/getting-started.mdx b/apps/docs/content/guides/platform/read-replicas/getting-started.mdxindex 9a9b17cb961..c4f768b47d5 100644--- a/apps/docs/content/guides/platform/read-replicas/getting-started.mdx+++ b/apps/docs/content/guides/platform/read-replicas/getting-started.mdx@@ -129,7 +129,7 @@ There is no single threshold to indicate when you should address replication lag<Admonition type="tip">-If you are already ingesting your [project's metrics](/docs/guides/platform/metrics#accessing-the-metrics-endpoint) into your own environment, you can also keep track of replication lag and set alarms with the `physical_replication_lag_physical_replica_lag_seconds` metric.+If you are already ingesting your [project's metrics](/docs/guides/telemetry/metrics) into your own environment, you can also keep track of replication lag and set alarms with the `physical_replication_lag_physical_replica_lag_seconds` metric.</Admonition>diff --git a/apps/docs/content/troubleshooting/exhaust-disk-io.mdx b/apps/docs/content/troubleshooting/exhaust-disk-io.mdxindex 5e191365a86..73249158f86 100644--- a/apps/docs/content/troubleshooting/exhaust-disk-io.mdx+++ b/apps/docs/content/troubleshooting/exhaust-disk-io.mdx@@ -25,7 +25,7 @@ Running out of Disk IO Budget means that your instance is using more disk than iTo check your Disk IO Budget on the Supabase Platform, head over to [Database Health in the Observability section](/dashboard/project/_/observability/database).-It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. With Grafana you will be able to pinpoint potential causes and see more fine-grained metrics like how much of your RAM is used for caching and your Swap usage. Read the [Metrics Guide](/docs/guides/platform/metrics) to learn more.+It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. With Grafana you will be able to pinpoint potential causes and see more fine-grained metrics like how much of your RAM is used for caching and your Swap usage. Read the [Metrics Guide](/docs/guides/telemetry/metrics) to learn more.## Common reasons for high disk IO usagediff --git a/apps/docs/content/troubleshooting/exhaust-ram.mdx b/apps/docs/content/troubleshooting/exhaust-ram.mdxindex a19bc56ae64..ccea52cea00 100644--- a/apps/docs/content/troubleshooting/exhaust-ram.mdx+++ b/apps/docs/content/troubleshooting/exhaust-ram.mdx@@ -31,7 +31,7 @@ High RAM usage could come with a range of issues:To check your RAM usage on the Supabase Platform, head over to [Database Health in the Observability section](/dashboard/project/_/observability/database).-It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. With Grafana you will be able to see how much of your RAM is used for caching and you can track other metrics such as your Swap usage. Read the [Metrics Guide](/docs/guides/platform/metrics) to learn more.+It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. With Grafana you will be able to see how much of your RAM is used for caching and you can track other metrics such as your Swap usage. Read the [Metrics Guide](/docs/guides/telemetry/metrics) to learn more.## Common reasons for high RAM usagediff --git a/apps/docs/content/troubleshooting/exhaust-swap.mdx b/apps/docs/content/troubleshooting/exhaust-swap.mdxindex 7b6272dabfb..c137d293a86 100644--- a/apps/docs/content/troubleshooting/exhaust-swap.mdx+++ b/apps/docs/content/troubleshooting/exhaust-swap.mdx@@ -33,7 +33,7 @@ High Swap usage can affect your database performance. For example, you might see## Monitor your swap-You can monitor your resources and set up alerts using Prometheus/Grafana. See the [metrics guide](/docs/guides/platform/metrics) for more information.+You can monitor your resources and set up alerts using Prometheus/Grafana. See the [metrics guide](/docs/guides/telemetry/metrics) for more information.An [example repository](https://github.com/supabase/supabase-grafana) to ingest metrics and visualize them with Grafana is provided in the linked guide, where we maintain a [list of the exported metrics](https://github.com/supabase/supabase-grafana/blob/main/docs/metrics.md).diff --git a/apps/docs/content/troubleshooting/high-cpu-usage.mdx b/apps/docs/content/troubleshooting/high-cpu-usage.mdxindex 943461aee2a..e710d5df09e 100644--- a/apps/docs/content/troubleshooting/high-cpu-usage.mdx+++ b/apps/docs/content/troubleshooting/high-cpu-usage.mdx@@ -25,7 +25,7 @@ You can check your CPU usage directly on the Supabase Platform. For this go to d-It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. You can find a guide for this [here](/docs/guides/platform/metrics).+It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. You can find a guide for this [here](/docs/guides/telemetry/metrics).## Common reasons for high CPU usagediff --git a/apps/docs/content/troubleshooting/how-to-view-database-metrics-uqf2z_.mdx b/apps/docs/content/troubleshooting/how-to-view-database-metrics-uqf2z_.mdxindex 86ea9f1a726..e5a1b47614d 100644--- a/apps/docs/content/troubleshooting/how-to-view-database-metrics-uqf2z_.mdx+++ b/apps/docs/content/troubleshooting/how-to-view-database-metrics-uqf2z_.mdx@@ -7,6 +7,6 @@ keywords = [ "metrics", "grafana", "monitoring" ]database_id = "da2d95e5-abc5-47c8-8389-1554d12abf91"----To monitor real-time metrics of your database, like CPU, EBS, active database connections, and memory usage, you can deploy a Grafana Dashboard. Check our [GitHub repo](https://github.com/supabase/supabase-grafana) for setup instructions for local or free [Fly.io](http://fly.io/) deployments. Refer to our concise [documentation](/docs/guides/platform/metrics) to learn more about the metrics endpoint.+To monitor real-time metrics of your database, like CPU, EBS, active database connections, and memory usage, you can deploy a Grafana Dashboard. Check our [GitHub repo](https://github.com/supabase/supabase-grafana) for setup instructions for local or free [Fly.io](http://fly.io/) deployments. Refer to our concise [documentation](/docs/guides/telemetry/metrics) to learn more about the metrics endpoint.While the [Dashboard's Reports Page](/dashboard/project/_/observability) displays some metric data, it provides hourly averages, not real-time by the second data. However, it offers query metrics, which the Grafana Dashboard does not include.diff --git a/apps/docs/content/troubleshooting/interpreting-supabase-grafana-io-charts-MUynDR.mdx b/apps/docs/content/troubleshooting/interpreting-supabase-grafana-io-charts-MUynDR.mdxindex 9d5e0b77009..bb66f23d10a 100644--- a/apps/docs/content/troubleshooting/interpreting-supabase-grafana-io-charts-MUynDR.mdx+++ b/apps/docs/content/troubleshooting/interpreting-supabase-grafana-io-charts-MUynDR.mdx@@ -7,7 +7,7 @@ keywords = [ "io", "disk", "database", "grafana" ]database_id = "0056cd40-df04-4045-bbfb-c245cb15b85d"----> [Supabase Grafana Installation Guide](/docs/guides/platform/metrics#deploying-supabase-grafana)+> [Supabase Grafana Installation Guide](/docs/guides/telemetry/metrics/grafana-self-hosted)There are two primary values that matter for IO:diff --git a/apps/docs/content/troubleshooting/monitor-supavisor-postgres-connections.mdx b/apps/docs/content/troubleshooting/monitor-supavisor-postgres-connections.mdxindex da380ce6df5..53f589b8b87 100644--- a/apps/docs/content/troubleshooting/monitor-supavisor-postgres-connections.mdx+++ b/apps/docs/content/troubleshooting/monitor-supavisor-postgres-connections.mdx@@ -19,7 +19,7 @@ _Visual of Grafana Dashboard_It can be run locally within Docker. Alternatively, you can deploy it to fly.io or Grafana Cloud, which are better for long-term data collection.-Installation instructions can be found in it the [metrics docs ](/docs/guides/platform/metrics#deploying-supabase-grafana)+Installation instructions can be found in it the [metrics docs ](/docs/guides/telemetry/metrics/grafana-self-hosted)## Observing connectionsdiff --git a/apps/docs/content/troubleshooting/steps-to-improve-query-performance-with-indexes-q8PoC9.mdx b/apps/docs/content/troubleshooting/steps-to-improve-query-performance-with-indexes-q8PoC9.mdxindex 29d1228cde3..edabf7e92c2 100644--- a/apps/docs/content/troubleshooting/steps-to-improve-query-performance-with-indexes-q8PoC9.mdx+++ b/apps/docs/content/troubleshooting/steps-to-improve-query-performance-with-indexes-q8PoC9.mdx@@ -23,7 +23,7 @@ Supabase has an [open-source Grafana Repo](https://github.com/supabase/supabase-_Visual of Grafana Dashboard_-It can be run locally within Docker or can be deployed for free to fly.io. Installation instructions can be found in [Supabase's metrics docs](/docs/guides/platform/metrics#deploying-supabase-grafana)+It can be run locally within Docker or can be deployed for free to fly.io. Installation instructions can be found in [Supabase's metrics docs](/docs/guides/telemetry/metrics/grafana-self-hosted)## Query optimization through indexesdiff --git a/apps/docs/content/troubleshooting/supabase-grafana-memory-charts.mdx b/apps/docs/content/troubleshooting/supabase-grafana-memory-charts.mdxindex 0e7eeb60dcd..3f7239eeeb5 100644--- a/apps/docs/content/troubleshooting/supabase-grafana-memory-charts.mdx+++ b/apps/docs/content/troubleshooting/supabase-grafana-memory-charts.mdx@@ -7,7 +7,7 @@ date_created = "2024-06-05"database_id = "179d70f3-1e26-4346-9ee8-d340fad382a3"----> [Supabase Grafana Installation Guide](/docs/guides/platform/metrics#deploying-supabase-grafana)+> [Supabase Grafana Installation Guide](/docs/guides/telemetry/metrics/grafana-self-hosted)Here are examples of unhealthy memory usage:diff --git a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdxindex 981a0024565..f75c004363a 100644--- a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx+++ b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx@@ -159,7 +159,7 @@ As a rule of thumb, if you're using the DB REST API or multiple app-based "user+Connection usage can be monitored with a Supabase Grafana Dashboard. It provides realtime visibility of over 200 database metrics, such as graphs of CPU, EBS, and active direct/pooler connections. It can be extremely useful for monitoring and debugging instances.-You can check our [GitHub repo](https://github.com/supabase/supabase-grafana) for setup instructions for local deployments or free cloud deployments on [Fly.io](http://fly.io/). Refer to Supabase [documentation](/docs/guides/platform/metrics) to learn more about the metrics endpoint.+You can check our [GitHub repo](https://github.com/supabase/supabase-grafana) for setup instructions for local deployments or free cloud deployments on [Fly.io](http://fly.io/). Refer to Supabase [documentation](/docs/guides/telemetry/metrics) to learn more about the metrics endpoint.### **Can Supavisor really support a million connections?**