Supabase Alerts and Notifications: A Complete Setup Guide

Proactive monitoring means knowing about problems before your users do. In this guide, you'll learn how to design and implement a complete alerting and notification strategy for your Supabase project—from what to monitor, to how to wire alerts into your incident response workflow.

Why Alerts Matter

If you only look at metrics when something is already broken, you're reacting too late.

Consider this scenario:

• Your database connections are maxing out.
• New connections start queueing or failing.
• Users see errors, timeouts, or degraded performance.
• By the time someone notices in a dashboard, you've already lost trust and possibly revenue.

With proper alerting, you'd receive a notification when connections hit, for example, 70–80% of capacity. That gives you time to:

• Scale your instance or connection pool.
• Optimize queries or add indexes.
• Shed non-critical load or rate-limit abusive traffic.

The goal of alerting is early, actionable signals that let you intervene before users are impacted.

What to Monitor

You don't need to alert on every metric. Focus on signals that reflect user impact and system health.

Critical Alerts (Wake You Up)

These indicate immediate or imminent user-facing problems and should page someone (SMS, phone, high-priority Slack, PagerDuty, etc.):

• Database down or unreachable
• Health checks failing
• Connection attempts timing out or being refused
• Connection pool exhausted
• Connection count at or near max
• High wait times for new connections
• Disk space critical (< 10% remaining)
• Risk of write failures and database crashes
• Error rate spike (> 5% of requests)
• HTTP 5xx, database errors, or failed RPC calls
• Replication lag critical (if using read replicas)
• Replica too far behind primary to serve fresh reads

These alerts should be loud, infrequent, and always actionable.

Warning Alerts (Check Soon)

Warnings indicate developing issues that may become critical if ignored:

• Connection count above 80%
• Early signal that capacity is being approached
• Disk space below 25%
• Time to plan cleanup or storage expansion
• Slow query threshold exceeded
• p95/p99 latency above target for a sustained period
• Unusual traffic patterns
• Sudden spikes or drops in requests, signups, or errors
• Certificate expiration approaching
• TLS certs or custom domain certs expiring soon

Warnings are usually routed to Slack/Teams or email, not SMS.

Informational Alerts (Nice to Know)

Informational alerts keep you informed but shouldn't interrupt you:

• Daily/weekly usage summaries
• Requests, errors, latency, top endpoints, etc.
• New user signup milestones
• e.g., 1k, 10k, 100k users
• Backup completion status
• Success/failure of scheduled backups
• Scheduled maintenance reminders
• Planned downtime or migrations

These are ideal for email digests or low-noise channels.

Setting Up Alerts with Supabase

Supabase gives you multiple building blocks to implement alerting. You can combine them depending on your stack and preferences.

Method 1: Database Webhooks (Triggers + Functions)

Use PostgreSQL functions and triggers to emit events when certain conditions are met. These can feed into webhooks, queues, or notification systems.

Example: Basic Alert Function

```sql

-- Create a function to send alerts

create or replace function send_alert()

returns void as $$

Supabase Alerts and Notifications: A Complete Setup Guide

Quick Answer: To set up effective alerts for Supabase, monitor connection pool usage (alert at 80%), query latency (alert on p95 > 1s), error rates (alert at >1%), and storage capacity (alert at 75%). Use a combination of database triggers, Supabase Edge Functions, and dedicated monitoring tools like Supaview for proactive notifications via Slack, email, or webhooks.

Proactive monitoring means knowing about problems before your users do. In this comprehensive guide, you'll learn exactly how to design, implement, and maintain a complete alerting strategy for your Supabase project—from what to monitor, to how to wire alerts into your incident response workflow.

Why Alerts Matter for Production Applications

If you only look at metrics when something is already broken, you're reacting too late. Consider this all-too-common scenario:

The cascade of failure: