supabase-logs

To fetch and analyze Supabase Edge Function logs for runtime errors, use a bundled Node.js script that retrieves both runtime and edge logs. It filters by function name and time window, returning structured results suitable for root-cause analysis of errors and latency.

Runtime logs in Supabase capture in-function console output, while edge logs record HTTP request and response metadata. Fetching both types simultaneously allows you to diagnose unexpected behavior by correlating application-level errors with HTTP latency issues.

You filter Supabase logs by a specific function or time window using command-line arguments. The script supports the --function flag to target a specific function and the --last flag to define a configurable time window for retrieving relevant edge and runtime logs.

Yes, you need a Supabase access token to retrieve Edge Function logs. The script reads the SUPABASE_ACCESS_TOKEN directly from a local .env file to authenticate API requests and securely fetch your project's runtime and HTTP metadata.

Yes, you can pull logs for all Supabase Edge Functions at once by omitting the function filter. This retrieves both runtime and edge logs across your entire project over a configurable time window, returning structured results ideal for incident reports.