Skip to content

feat(pg): add pg-pool.release span#3364

Open
MUSKANNISHAD wants to merge 1 commit intoopen-telemetry:mainfrom
MUSKANNISHAD:feat/pg-capture-pool-release
Open

feat(pg): add pg-pool.release span#3364
MUSKANNISHAD wants to merge 1 commit intoopen-telemetry:mainfrom
MUSKANNISHAD:feat/pg-capture-pool-release

Conversation

@MUSKANNISHAD
Copy link

Fixes #1976

This PR adds a pg-pool.release span by instrumenting client.release() on the
client returned from pool.connect().

This allows tracing the full PostgreSQL pool lifecycle
(connect → query → release) while keeping existing pool metrics behavior unchanged.

@MUSKANNISHAD
Copy link
Author

I’ve added tracing for pg-pool.release by wrapping client.release() on the client returned from pool.connect(). This captures the full pool lifecycle while keeping metrics unchanged. I’ve opened a PR for review.

@maryliag
Copy link
Contributor

maryliag commented Feb 5, 2026

please add tests to validate your changes

@MUSKANNISHAD MUSKANNISHAD force-pushed the feat/pg-capture-pool-release branch from 3e3a878 to a61b987 Compare February 6, 2026 07:47
@MUSKANNISHAD
Copy link
Author

please add tests to validate your changes
Thanks for the review!
I’ve added tests covering the new pg-pool.release span and updated the existing test suite accordingly.
The changes are included in the latest commit — please let me know if you’d like additional coverage or adjustments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

opentelemetry-instrumentation-pg: capture pg pool release events

2 participants