Log sources and fields

Each event is a row in the ClickHouse logs table. Filter the source column to select a service. The tables below list its fields; a field is not necessarily populated on every event.

id, timestamp, event_message, severity_text, and source are top-level columns. Service fields are string values in log_attributes, even when the original event contains a number or boolean. Use the ClickHouse query field column directly. See Query logs with SQL for casting and field discovery.

Sources

For postgres_logs, statement text and error details can appear in event_message. A missing structured field does not mean the event has no detail.

Captured HTTP headers

API Gateway logs capture only the headers below. Other headers still reach the application and client but are omitted from these logs.

Request headers:

• accept
• cf-connecting-ip
• cf-ipcountry
• host
• user-agent
• x-forwarded-proto
• referer
• content-length
• x-real-ip
• x-client-info
• x-forwarded-user-agent
• range
• prefer

Response headers:

• cf-cache-status
• cf-ray
• content-location
• content-range
• content-type
• content-length
• date
• transfer-encoding
• x-kong-proxy-latency
• x-kong-upstream-latency
• sb-gateway-mode
• sb-gateway-version

Capture limits

• Hosted Postgres events longer than 100,000 characters and Edge Function log messages longer than 10,000 characters are truncated.
• Internal Supabase service connection events are not recorded in hosted Postgres logs.
• An Edge Function invocation uses function_edge_logs; its console output uses function_logs.
• For API Load Balancer traffic, log_attributes['load_balancer_redirect_identifier'] identifies the upstream database.

Fields by source