Skip to content

Add DCP startup OTEL tracing#136

Draft
davidfowl wants to merge 2 commits intomainfrom
davidfowl/otel-startup-tracing
Draft

Add DCP startup OTEL tracing#136
davidfowl wants to merge 2 commits intomainfrom
davidfowl/otel-startup-tracing

Conversation

@davidfowl
Copy link
Copy Markdown

Description

Adds startup OTEL tracing support for DCP and centralizes startup profiling instrumentation in internal/telemetry.

  • Adds DCP startup context propagation from Aspire via environment variables and resource annotations.
  • Configures DCP OTEL export so startup spans can correlate with Aspire CLI and Hosting profiling traces.
  • Adds startup spans for DCP command execution, API server startup, controller startup, resource reconciliation, executable/container/service management, and extension discovery.
  • Centralizes DCP startup span names, event names, and attribute names behind telemetry constants and a StartupSpan wrapper so call sites do not expose raw span details.

Validation

  • go test ./internal/telemetry ./internal/dcp/commands ./internal/dcp/bootstrap ./internal/dcpctrl/commands ./controllers ./cmd/dcp
  • go test ./... was attempted locally; it fails on existing local test prerequisites/environment issues such as missing .toolbin/delay.

Notes

This pairs with the Aspire startup OTEL harness work so exported traces can validate correlated CLI, Hosting, and DCP startup spans.

davidfowl and others added 2 commits May 3, 2026 14:55
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a startup span wrapper and centralize DCP startup span, event, and attribute names in the telemetry package so call sites no longer use raw span values or scattered string constants.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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