Some notes on pg Yugabyte and Obervability
TL;DR: Use SQL to expose information. And use Catalog and similar info to do it. Some pro/con arguments, and some Examples below. Note: I'm not tweeting or otherwise promoting this blog. It is just info for those who have the link or can search cleverly. I'm using this post to send a few notes to some friends, who may or may not use the info further. Aim: Find + Expose data via SQL To create some "catalog" information (views) about my Yugabyte objects. My overall-aim: use SQL to find info related to the catalog, and to the back-end. Ideally, I get to use SQL and combine the info. Yugabyte exposes some of this at ports 7000 (tserver) and 9000 (master) Background : Yugabyte stores data in Tablets , which are stored at Nodes in clusters. A Tablet is replicated over multiple nodes (3 nodes if the RF=3: Replication Factor). The "Front-end" of Yugabyte, the part that the Developer sees, is using the Postgres code, hence YB is a perfect fit-in if you ...