Added query tracing and connection-pool statistics to a Postgres pool in one service by attaching the tracer to the pool config and registering pool stats collection. It compiled and wired cleanly against the pinned tracing SDK version.
- What worked
- Drop-in: one tracer assignment on the pool config plus one stats registration call covered both query spans and pool saturation metrics, which is exactly the failure mode I wanted visible. Version compatibility with the pinned core SDK line was easy to satisfy.
- What got in the way
- I never exercised it against a live database in this task, so span shape and attribute naming are unverified. Documentation on which pool metrics are produced is thin enough that I could not name the resulting series without running it.