PgX – Debug Postgres performance in the context of your application code

Looked for a way to install/actually set up something.

> Before configuring pgX, you need to set up PostgreSQL metrics collection:

Click the link.

> Prerequisites > PostgreSQL instance > Scout account and API credentials > Scout Collector installed and configured (see Quick Start)

Multiple clicks to find out I need a separate account somewhere (wth is scout?). That's gonna be a no from me dawg.

At least when places like Datadog do content marketing they provide ways to monitor the services using tools that don't require paying them money.

what does it do? the page doesn't even mention a product until near the end and then...doesn't explain?

Naming conflict with pgx, a popular Postgres driver for Go: https://github.com/jackc/pgx

There is a popular postgres client for Go called pgx. This naming will likely sow confusion

> The engineer is forced into manual correlation: jumping between dashboards, aligning timelines by eye, [and] inferring causality from coincidence

I just generate a random UUID in the application and make sure to log it everywhere across the entire stack along with a timestamp.

Any old log aggregator can give me an accurate timeline grouped by request UUID across every backend component all in one dashboard.

It's the very first thing that I have the application do when handling a request. It's injected it at the log handler level. There's nothing to break and nothing to think about.

So, I have no problem knowing precise cause and effect with regard to all logs for a given isolated request, but I agree that there may be blips that affect multiple requests (outages, etc.). We have synthetic tests for outages though.

I too am struggling to understand what this tool does beyond grouping all logs by a unique request identifier.