Monitoring and logging in Supabase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of monitoring in Supabase?

Monitoring in Supabase helps track the health and performance of your database and services in real time, so you can quickly spot and fix problems.

beginner

What kind of data does logging capture in Supabase?

Logging records detailed events and actions happening inside your Supabase project, like queries run, errors, and system messages, which helps in troubleshooting.

beginner

How can you access logs in Supabase?

You can access logs through the Supabase dashboard under the 'Logs' section or use the Supabase CLI to fetch logs for your project.

intermediate

Why is it important to set up alerts in monitoring?

Alerts notify you immediately when something goes wrong, like a service outage or high error rate, so you can fix issues before users notice.

intermediate

What is the difference between metrics and logs in Supabase monitoring?

Metrics are numbers that show system performance over time (like CPU use), while logs are detailed records of events and errors. Both help understand system health.

Where do you find the logs for your Supabase project?

A In the Supabase dashboard under 'Logs'

B In the database schema

C In the Supabase billing section

D In the Supabase authentication settings

Logs are accessible in the Supabase dashboard under the 'Logs' section, where you can review system events and errors.

What does monitoring NOT typically track in Supabase?

A Database query performance

B CPU and memory usage

C User login events

D System uptime

User login events are part of authentication logs, not general system monitoring metrics.

Why are alerts useful in monitoring?

A They automatically fix errors

B They notify you when issues occur

C They increase database speed

D They backup your data

Alerts notify you immediately when something goes wrong so you can respond quickly.

Which tool can you use to fetch logs from Supabase besides the dashboard?

A Supabase Storage

B Supabase Studio

C Supabase Auth

D Supabase CLI

The Supabase CLI allows you to fetch logs and manage your project from the command line.

What is a metric in Supabase monitoring?

A A number showing system performance over time

B A detailed event record

C A user authentication token

D A database schema

Metrics are numbers that show how well the system is performing, like CPU usage or query times.

Explain how monitoring and logging work together in Supabase to keep your project healthy.

Think about how watching numbers and reading event details help you understand system status.

Describe the steps to access and use logs in Supabase for troubleshooting.

Consider both the web interface and command line options.

Practice

1. What is the main purpose of monitoring and logging in Supabase?

easy

A. To keep your app healthy and fix problems quickly

B. To increase the app's loading speed

C. To add new features automatically

D. To change the app's user interface

Solution

1. Step 1: Understand monitoring and logging roles

   Monitoring and logging track app behavior and errors to maintain health.

2. Step 2: Identify the main goal

   The goal is to detect and fix problems quickly to keep the app running well.

3. Final Answer:

   To keep your app healthy and fix problems quickly -> Option A

4. Quick Check:

   Monitoring and logging = keep app healthy [OK]

Hint: Monitoring = health check; logging = problem records [OK]

Common Mistakes:

• Confusing monitoring with adding features
• Thinking logging changes UI
• Believing monitoring speeds up app

2. Which of the following is the correct command to view logs for a Supabase project with ref abc123 for the last 1 hour?

easy

A. supabase logs --id abc123 --time 1h

B. supabase log --project abc123 --last 1h

C. supabase logs --project-ref abc123 --since 1h

D. supabase logs -p abc123 -t 1hour

Solution

1. Step 1: Recall the correct syntax for logs command

   The correct command uses supabase logs with --project-ref and --since flags.

2. Step 2: Match the options with correct flags

   supabase logs --project-ref abc123 --since 1h matches the correct syntax: supabase logs --project-ref abc123 --since 1h.

3. Final Answer:

   supabase logs --project-ref abc123 --since 1h -> Option C

4. Quick Check:

   Correct flags = --project-ref and --since [OK]

Hint: Use --project-ref and --since flags with supabase logs [OK]

Common Mistakes:

• Using 'log' instead of 'logs'
• Wrong flag names like --id or --last
• Incorrect time format like '1hour'

3. What will be the output of the command supabase logs --project-ref xyz789 --since 30m?

medium

A. Shows logs from all projects for the last 30 minutes

B. Shows logs from project xyz789 for the last 30 minutes

C. Shows logs from project xyz789 for the last 30 hours

D. Returns an error because --since requires seconds

Solution

1. Step 1: Understand the command flags

   The --project-ref xyz789 specifies the project, and --since 30m means last 30 minutes.

2. Step 2: Interpret the output meaning

   The command outputs logs only for project xyz789 from the last 30 minutes.

3. Final Answer:

   Shows logs from project xyz789 for the last 30 minutes -> Option B

4. Quick Check:

   --project-ref + --since 30m = last 30 minutes logs [OK]

Hint: Since 30m means last 30 minutes logs [OK]

Common Mistakes:

• Thinking it shows logs for all projects
• Confusing 30m with 30 hours
• Assuming --since needs seconds only

4. You ran supabase logs --project-ref myproj --since 2h but got no output. What is the most likely reason?

medium

A. The project ref is incorrect or does not exist

B. The command requires --until flag as well

C. Logs are only available for the last 1 hour

D. The --since flag must be in seconds, not hours

Solution

1. Step 1: Check project ref validity

   If the project ref is wrong or missing, no logs will show.

2. Step 2: Verify command flags and log availability

   The command syntax is correct; logs are available beyond 1 hour; --since accepts hours.

3. Final Answer:

   The project ref is incorrect or does not exist -> Option A

4. Quick Check:

   No output usually means wrong project ref [OK]

Hint: Check project ref first if logs show empty [OK]

Common Mistakes:

• Thinking --until is mandatory
• Assuming logs only keep 1 hour
• Believing --since needs seconds only

5. You want to set up alerts to notify you when errors appear in your Supabase logs. Which approach is best?

hard

A. Regularly run supabase logs manually and check for errors

B. Restart the Supabase project daily to clear logs

C. Ignore logs and fix errors only when users report them

D. Use a third-party monitoring tool connected to Supabase logs with alert rules

Solution

1. Step 1: Understand alerting needs

   Manual checks are slow and error-prone; ignoring logs delays fixes.

2. Step 2: Choose best practice for alerts

   Using a monitoring tool with alert rules automates error detection and notification.

3. Final Answer:

   Use a third-party monitoring tool connected to Supabase logs with alert rules -> Option D

4. Quick Check:

   Automated alerts = faster fixes [OK]

Hint: Automate alerts with monitoring tools, not manual checks [OK]

Common Mistakes:

• Relying on manual log checks
• Ignoring logs until problems grow
• Restarting project clears logs but not errors