Monitoring a Supabase app: supabase-js calls show up as HTTP, not database queries #52437
virajrakholiya
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Something worth knowing if you add monitoring or tracing to an app that uses Supabase.
If your server talks to Supabase through
supabase-js, those calls go over HTTP (PostgREST). Most APM and tracing tools therefore record them as outgoing HTTP requests, not as database queries. You see something likeGET https://<project>.supabase.co/rest/v1/orderswith a duration, but not the query behind it.If you connect with a Postgres driver directly (
pgin Node, psycopg or SQLAlchemy in Python), the same tools record real database spans with timings.What helps:
GET /rest/v1/ordersshows up as a pattern instead of scattered requests.Question: how do you watch query performance in production when everything goes through
supabase-js? Has anyone traced through PostgREST in a way that keeps the SQL?(Disclosure: I'm building Relia, a monitoring tool, and this is a gap I'm working on. Curious how others handle it.)
All reactions