Supabase and Postgres app telemetry

Test the integration

Send and verify events with Supabase and Postgres app telemetry

Use Supabase and Postgres app telemetry where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.

1
Choose the outcome
API reliability
2
Define the contract
function_name, route_template, method, status_code, and region
3
Log the final result
Keep the Telemetry key and Supabase secret or service-role credentials in server-side function secrets; never expose them to browser code.
4
Check the stored event
Exercise a known fixture, then inspect api_request_completed for one correctly typed terminal row.

Before you start

A Supabase Edge Function or other trusted server runtime with a Telemetry secret
Row Level Security and application authorization enforced before privileged database work
A pooled or serverless-friendly Postgres connection path for direct database access

Delivery setup

Install and initialize server-side

Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

supabase-postgres-install

npm installation

bash

npm install telemetry-sh

1Create one reusable server-side client. Set its timeout and retry limit.
2Log an event when the operation succeeds, fails, retries, or times out.
3Send test events with known results and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

supabase-postgres

Supabase and Postgres app telemetry event

javascript

await telemetry.log("api_request_completed", {
  function_name: "sync-project",
  route_template: "/api/projects/:id/sync",
  method: "POST",
  status_code: 200,
  status: "success",
  latency_ms: 266,
  database_operation: "sync_project",
  team_id: team.id,
  region: Deno.env.get("SB_REGION"),
});

Event schema

function_name, route_template, method, status_code, and region

status, latency_ms, database_operation, rows_affected, and error_type

request_id, account_id, release, and environment

Check your setup

Checkpoint 1

Keep the Telemetry key and Supabase secret or service-role credentials in server-side function secrets; never expose them to browser code.

Checkpoint 2

Log the application outcome rather than SQL text, connection strings, request bodies, or unrestricted database errors.

Checkpoint 3

Separate function latency from database-operation latency when the distinction is needed for diagnosis.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

supabase-postgres-verification

Supabase and Postgres app telemetry verification query

sql

SELECT *
FROM api_request_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Database reliability use case Structured logging guide Database latency SQL Supabase Edge Functions Supabase Edge Function secrets

Where to log

Keep the outcome event small and recoverable

This pattern provides

Record the outcome as an event you can query with SQL.
Stable fields for dashboards, alerts, and cross-event correlation.
Test events for checking success, failure, retries, and timeouts.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Product lifecycle7 fields