[db/oracledb] Native traceparent propagation to V$SESSION #3975

Area(s)

oracledb

What's missing?

Feature Request: Native traceparent Propagation to V$SESSION

Context & Problem

It was discussed here. In distributed tracing with Oracle Database, out-of-band monitoring components (such as oracledbreceiver) operate as separate database sessions. As a result, they cannot read session-isolated Application Context (SYS_CONTEXT in the CLIENTCONTEXT namespace) maintained by active client sessions.

Currently, the specification relies on setting V$SESSION.ACTION (limited to 64 bytes) to expose W3C traceparent for external collector polling and correlation.

Proposed Feature / Long-term Solution

Propagate W3C traceparent natively into V$SESSION at the database engine/driver level, mirroring the existing native behavior for ECID (V$SESSION.ECID).

This will allow:

• Direct, native correlation of database sessions with distributed traces without custom application context workarounds.
• Clean out-of-band telemetry collection without occupying the V$SESSION.ACTION field.

Status & Internal Tracking

• Internal Alignment: Native traceparent projection into V$SESSION is already an identified feature request on the internal Oracle Database/driver roadmap.

Purpose of this GitHub Issue

This public issue serves to:

1. Track progress for the OpenTelemetry community as the engine-level feature evolves.
2. Provide transparency for implementers relying on the current V$SESSION.ACTION fallback mechanism in the semantic conventions spec.

Describe the solution you'd like

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}