Skip to content

feat(telemetry): add first-class OpenTelemetry tracing - #23

Open
psteinroe wants to merge 1 commit into
feat/wait-for-eventfrom
feat/otel-core
Open

psteinroe wants to merge 1 commit into
feat/wait-for-eventfrom
feat/otel-core

Conversation

@psteinroe

Copy link
Copy Markdown
Owner

Add direct OpenTelemetry API instrumentation at durable runtime boundaries without prototype patching or a generic observability adapter. Global OTel registration is zero-config, telemetry: false opts out, and pgconductor never owns SDK/exporter lifecycle.

This core slice persists bounded W3C execution context and instruments committed invoke sends, finite handler attempts, settlement transactions, batch links, and uncached durable steps using current messaging semantic conventions. Telemetry is fail-open and the API remains an external peer dependency.

Stacked on #22. The next PR adds event/cron/child/DLQ propagation and metrics.

Refs #7

@psteinroe
psteinroe added this pull request to stack #25 September 15, 2026 03:35
@psteinroe
psteinroe force-pushed the feat/otel-core branch 2 times, most recently from 9c75d56 to 5f96a43 Compare September 15, 2026 04:50
fix(telemetry): persist debounce trace context
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant