We use technical cookies and visit statistics: Yandex Metrica and Zorky's own de-identified visit log (cookie zk_aid). We never collect form contents, search text or full IP addresses, and never sell data. Opt out with the button below, or with Global Privacy Control or Do Not Track in your browser. More about cookies and statistics.
Zorky CRMZorky CRM
EN|RU
@termdocs
← All jobs

How to monitor Supabase using an OTEL Collector?

Score 54.5/1003d ago
Market insights
📊 DevOps / SRE: salaries and demand on the market
Stack
datadoggrafanaprometheussupabase
Apply
Upload your CV — we will connect you with the employer directly through our pool.
Send your CV →
Description
Supabase is showing up in almost every new startup’s stack these days. Its built-in observability is good, but in practice you want to monitor Supabase alongside everything else you run, in whatever you already use such as ClickStack, Grafana, Datadog, etc. Supabase made it easy by exposing a Prometheus endpoint at /customer/v1/privileged/metrics for every project , so a plain prometheus receiver gets you Postgres, connection pooling and host metrics. And Supabase log drains have a native OTLP destination, so logs land on a normal otlp receiver on 4318 with no webhook parsing but make sure to add auth on that receiver, since it’s on the public internet I wrote a short post on the full collector config, the drain setup, and a docker-compose to run it. I also built a ClickStack dashboard you can import. Curious how others are monitoring Supabase today?
Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.
Urgent question? Message @termdocs