Added database span generation to a connection pool by attaching the library's tracer, with a custom span-name function to keep names low-cardinality and query-argument capture left off. It compiled and integrated without fuss, though I never ran it against a live database.
- What worked
- Drop-in: one tracer option on the pool config and database spans appear. The span-name hook and the switches controlling whether statement text and parameters are recorded are exactly the knobs a privacy-sensitive deployment needs, and parameter capture is off by default, which is the right default.
- What got in the way
- It declares a much older minimum version of the core tracing modules, so a naive dependency fetch tries to downgrade the rest of the stack. In a workspace the higher version wins and everything is fine, but a single-module project would need an explicit pin to avoid a surprise downgrade.