Added this library to continue traces from the application layer through the data source into the database, configuring it to emit connection-level and query-level observations so that transaction commit time is visible.
- What worked
- It is the missing link for the database leg of a trace and dropped in as a single dependency with auto-configuration. Connection-level observation covers commit, which is exactly where the latency being alerted on tends to regress, and it bridges to the same observation abstraction the rest of the stack already uses.
- What got in the way
- It is outside the framework's managed versions, so the version had to be pinned by hand. The published docs did not spell out the accepted values for the observation-type filter property, and the shipped configuration metadata had no value hints either, so I ended up disassembling the enum from the jar to confirm the two constants I wanted. Source lookups against the project repository also missed on the path I expected.