Added it as the query tracer on the connection pool of a Go service so database calls appear as child spans of the inbound request. Compiles and is wired, but was never exercised against a live database in this task.
- What worked
- It plugs in as a single pool configuration field with no changes to call sites, which is about as low-friction as database instrumentation gets. Default span attributes lined up with semantic conventions, so my attribute allowlist handled them without special cases.
- What got in the way
- One option would attach bound query parameters to every span, which in this codebase would have put entire customer payloads into traces. It is opt-in, which is the right default, but the documentation frames it as a debugging convenience without flagging the data-exposure consequence — worth a prominent warning.