Repository navigation
Option to ignore specific Postgres (pg) spans #16536
Description
Activity
This was already requested in open-telemetry/opentelemetry-js-contrib#2017 and we might be able to use the workaround: open-telemetry/opentelemetry-js-contrib#2017 (comment)
@Lms24 I have a clarification question on this. A customer raised the problem that they're attempting to use
ignoreSpansin their express app on pg-pool.connect spans, using this syntax:ignoreSpans: [ /pg-pool\.connect/, ](SDK version:
sentry.javascript.node 9.13.0)I'd expect these spans to be ignored, but the customer is seeing them still:
Is the reason they're still showing up related to the fact that these are auto-instrumented by the OTel
pginstrumentation?(SDK version: sentry.javascript.node 9.13.0)
ignoreSpanswas introduced in10.2.0. I recommend upgrading and trying again. I opened getsentry/sentry-docs#14971 to clarify the required version in docs.Reacted by Chris Stavitsky- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Sep 18, 2025 - marked feat(node): Add
ignoreConnectSpansoption topostgresIntegration#19292 as a duplicate of this issueon Feb 11, 2026 A PR closing this issue has just been released 🚀
This issue was referenced by PR #19291, which was included in the 10.40.0 release.
Metadata
Metadata
Assignees
Projects
- Status
Problem Statement
Extracted from #16505 (comment), we should find a way to ignore certain spans emitted from the OTel
pginstrumentation. For example, thepg-pool.connectspans.Solution Brainstorm
Right now, I don't think there is a way to achieve this, given that the
pginstrumentation from OTel used in ourpostgresIntegrationdoesn't expose an option for (not) starting connect spans. Which means we'll likely need to contribute this upstream or vendor-in thepginstrumentation (withpgalready being Otel v2 compatible, we'd likely need to vendor-in anyway).