new·Earn with mozg — 20% of every monthSend somebody here and take a fifth of every plan payment they make, for as long as they keep paying — not a bounty on the first invoice. Your handle is the link, the window is thirty days, and the commission lands on your balance the second they pay. Free to join: if you have signed in, you already have the link. mozg.sh/earnall news →
mozg.beta
Sign in

Supabase · Realtime · all subjects

monitoring & debugging

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Realtime reports overview and access

Realtime reports provide insights into how applications use Supabase Realtime, including connections, broadcast and change events, execution times, and lag. They help monitor connection counts and message volumes against plan quotas, identify performance bottlenecks in RLS policies or database replication, troubleshoot errors and connection issues, and plan capacity upgrades. Reports are accessed from Project Settings > Product Reports > Realtime in the project dashboard.

Message Payload Size report and performance impact

The Message Payload Size report displays median payload size in bytes for messages sent through Realtime channels. Larger payloads require more bandwidth and processing time, which increases latency and reduces number of messages the system can handle per second. Broadcast payload size limits: Free (256 KB), Pro+ (3,000 KB). Postgres Changes payload size limit: 1,024 KB for all plans.

Total Requests report metrics

The Total Requests report monitors overall volume of HTTP requests for Realtime over time. The report includes WebSocket upgrade requests and REST API requests made to the Realtime service.

Response Errors report and error types

The Response Errors report monitors number of failed HTTP requests to Realtime service over time. These errors include HTTP error status codes (4xx client errors and 5xx server errors) from REST API requests, failed WebSocket upgrade requests, authorization failures, and other error responses. Monitoring error rates alongside total requests helps identify patterns and troubleshoot issues affecting Realtime service availability.

Response Speed report and performance monitoring

The Response Speed report monitors average response time in milliseconds for HTTP requests to Realtime service over time. This includes response times for REST API requests such as broadcast messages, WebSocket upgrade requests, and other HTTP-based interactions. Higher response times indicate performance bottlenecks, database load issues, or network problems that may impact real-time responsiveness of applications.

Give your agent this brain