80 ms·
pg_flight_recorder: Continuously sample PostgreSQL system state via pg_cron
- Valodim 5mo agoThis sounds promising, but the examples don't show what a report actually looks like? What information does this actually show?
- nijave 5mo agoThey don't have an example but they have the schema the functions return https://github.com/dventimisupabase/pg_flight_recorder/blob/main/REFERENCE.md https://github.com/dventimisupabase/pg_flight_recorder/blob/...
- esafak 5mo agoThis looks like metrics. No otel sink?
- nijave 5mo agoAfter reading docs don't think that makes much sense. This is sampling a bunch of stats from pg, wait sampling, and stat statements and storing somewhere in pg. If you want otel, you can do that yourself with pg exporter and store in your otel store. Seems like it basically automates capturing metrics and storing them in PG but doesn't actually handle the instrumentation (it reads from various other things).
- dventimisupa 5mo agoHey! Author here. Yup, this captures wait events, lock activity, checkpointer and backgroundwriter activity, statement activity, and configuration changes, and like the very excellent pg_wait_sampling (https://github.com/postgrespro/pg_wait_sampling https://github.com/postgrespro/pg_wait_sampling) it stores those data in the database with views and functions to provide access, but it doesn't send those data out to an APM (though that could be arranged). In fact, it's inspired by pg_wait_sampling, which is very high quality but which as a bona-fide extension is too often missing from managed PostgreSQL platforms. Hence, writing it as an "anti-extension" (thanks Nik Samokhvalov for coining that term).