Monitoring and logging in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Supabase Logs Retrieval Command Output

You run the command to fetch the latest 5 logs from your Supabase project:

supabase logs tail --limit 5

What is the expected output format of this command?

A A JSON array with 5 log entries, each containing timestamp, level, and message fields.

B A plain text list of 5 log messages without timestamps or levels.

C An error message stating 'Command not found' because 'logs' is not a valid subcommand.

D A CSV file download prompt with log data.

💡 Hint

Think about how CLI tools usually format logs for easy parsing.

The 'supabase logs tail' command outputs logs in JSON format by default, showing structured data including timestamp, level, and message for each log entry.

🧠 Conceptual

intermediate

Understanding Supabase Monitoring Metrics

Which of the following metrics is NOT typically monitored by Supabase's built-in monitoring tools?

A Database query latency and error rates.

B Realtime subscription connection counts.

C CPU usage of the client machine running the Supabase CLI.

D Storage bucket usage and file upload errors.

💡 Hint

Supabase monitoring focuses on cloud resources, not local client machines.

Supabase monitoring tracks server-side metrics like database performance and storage usage, but does not monitor the CPU usage of the user's local machine.

❓ Troubleshoot

advanced

Diagnosing Missing Logs in Supabase

You notice that your Supabase project logs are not showing any entries for recent API requests. Which configuration issue is the MOST likely cause?

A Realtime subscriptions are disabled in the project settings.

B The Supabase CLI is outdated and needs to be updated.

C The database connection string is incorrect.

D The API logging level is set to 'error' instead of 'info'.

💡 Hint

Logs depend on the logging level to capture different types of events.

If the logging level is set too high (like 'error'), informational logs about API requests won't appear. Setting it to 'info' or lower captures more details.

🔀 Workflow

advanced

Setting Up Alerting for Supabase Logs

You want to get notified immediately when your Supabase project logs show any 'error' level messages. Which workflow correctly sets this up?

A Configure a webhook in Supabase to send logs to an external alerting service filtering for 'error' level messages.

B Run 'supabase logs tail' manually every hour and check for errors yourself.

C Enable realtime subscriptions on the database to receive error messages as notifications.

D Set the Supabase CLI to verbose mode to print errors to the console.

💡 Hint

Automated alerting requires integration with external services.

Supabase allows configuring webhooks to forward logs to alerting tools that can filter and notify on error messages automatically.

✅ Best Practice

expert

Best Practice for Long-Term Log Storage in Supabase

What is the recommended best practice for storing Supabase logs for long-term analysis beyond the default retention period?

A Use the Supabase CLI to save logs locally on your development machine.

B Export logs regularly to an external storage service like AWS S3 or Google Cloud Storage.

C Store logs only in the Supabase dashboard and rely on screenshots for backup.

D Increase the Supabase project plan to get unlimited log retention.

💡 Hint

Think about durable, scalable storage solutions for logs.

Exporting logs to external storage services ensures logs are preserved long-term and can be analyzed with other tools.

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