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.