Monitoring and logging in Supabase - Step-by-Step Execution

Process Flow - Monitoring and logging

Start Supabase Project

↓

Enable Monitoring Tools

↓

Collect Metrics & Logs

↓

Store Data in Dashboard

↓

Analyze Metrics & Logs

↓

Set Alerts if Issues Detected

↓

Respond to Alerts & Fix Issues

↓

Repeat Monitoring Cycle

This flow shows how Supabase monitoring collects data, stores it, analyzes it, and alerts you to keep your project healthy.

Execution Sample

Supabase

supabase logs --project-ref your-project-ref --since 1h
supabase metrics --project-ref your-project-ref

These commands fetch logs from the last hour and show performance metrics for your Supabase project.

Process Table

Step	Command	Action	Output/Result
1	supabase logs --project-ref your-project-ref --since 1h	Fetch logs from last 1 hour	List of recent logs with timestamps and event details
2	supabase metrics --project-ref your-project-ref	Retrieve performance metrics	Metrics like CPU usage, DB connections, query times
3	Analyze logs and metrics	Check for errors or slow queries	Identify any warnings or errors in logs
4	Set alert rules (via dashboard)	Configure alerts for thresholds	Alerts trigger on high CPU or error spikes
5	Receive alert notification	Alert sent to email or webhook	Notification received for immediate action
6	Fix issue based on alert	Apply fix or scale resources	System performance improves
7	Continue monitoring	Repeat data collection and analysis	Ongoing health tracking
8	Exit	Stop monitoring session	Monitoring paused or stopped

💡 Monitoring session ends when user stops or pauses monitoring

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Logs	empty	logs from last 1h	logs unchanged	logs filtered for errors	logs unchanged	logs unchanged	logs unchanged	logs unchanged
Metrics	empty	empty	metrics retrieved	metrics unchanged	metrics unchanged	metrics unchanged	metrics unchanged	metrics unchanged
Alerts	none	none	none	alert rules set	alert triggered	alert resolved	alert cleared	none

Key Moments - 3 Insights

Why do we fetch logs and metrics separately instead of together?

Logs and metrics are different data types; logs show events, metrics show performance numbers. Step 1 fetches logs, step 2 fetches metrics separately for clear analysis.

What happens if no alert rules are set?

Without alert rules (step 4), no notifications will be sent even if issues occur, so problems might go unnoticed as shown in step 5.

Why do we keep monitoring after fixing an issue?

Continuous monitoring (step 7) ensures the fix worked and detects new issues early, maintaining system health over time.

Visual Quiz - 3 Questions

Look at the execution table, what output do we get after running 'supabase logs --project-ref your-project-ref --since 1h'?

A Alert notification sent to email

B List of recent logs with timestamps and event details

C Metrics like CPU usage and query times

D Alert rules configuration screen

💡 Hint

Check Step 1 output column in the execution_table

At which step do alert notifications get sent according to the execution table?

A Step 5

B Step 3

C Step 2

D Step 7

💡 Hint

Look for 'Alert sent to email or webhook' in the Action column

If alert rules are not set, what will be the state of Alerts after Step 5 in variable_tracker?

A alert triggered

B alert cleared

C none

D alert resolved

💡 Hint

Refer to Alerts row in variable_tracker after Step 5

Concept Snapshot

Monitoring and logging in Supabase:
- Use 'supabase logs' to fetch event logs
- Use 'supabase metrics' to get performance data
- Analyze logs and metrics for issues
- Set alert rules to get notified
- Respond to alerts and fix problems
- Keep monitoring continuously for health

Full Transcript

This visual execution shows how to monitor and log in Supabase. First, you fetch logs from the last hour using the logs command. Then, you get performance metrics separately. You analyze both to find errors or slow queries. Next, you set alert rules to notify you if something goes wrong. When alerts trigger, you receive notifications and fix the issues. Finally, you continue monitoring to keep your project healthy. Variables like logs, metrics, and alerts change step by step as you run commands and respond to alerts.