feat(o11y): self-tracing via runtime spans, adapter emit spans, and OTLP trace export (PIPE-1066) - #286
Open
Dylan-M wants to merge 1 commit into
Conversation
2 tasks
Contributor
Author
This was referenced Aug 6, 2026
feat(o11y): per-instance metrics via injectable MeterProvider, drop package globals (PIPE-1066)
#285
Open
Open
…TLP trace export (PIPE-1066) Assisted-by: Claude Opus 4.8
Dylan-M
force-pushed
the
dylanmyers/pipe-1066-self-tracing
branch
from
August 14, 2026 19:22
b122971 to
cb115bd
Compare
Dylan-M
force-pushed
the
dylanmyers/pipe-1066-per-instance-metrics
branch
from
August 14, 2026 19:22
9aee681 to
bad99f9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Proposed Change
Adds blitz's session-level self-tracing. The runtime emits a root
blitz.sessionspanfrom Start to Stop, with a child
blitz.generator.runspan per module. Consumer adaptersemit gated
blitz.emit.*spans. Trace export is opt-in through the newtelemetry.tracesconfig. With an OTLP endpoint set, spans export there. Without one, the nil TracerProvider
means spans are created and dropped by the global no-op provider.
PerBatchSpansgatesthe higher-volume per-emit spans and is off by default.
Each setting is exposed on all three config surfaces, like every other blitz option: the
telemetry.tracesconfig block,BLITZ_TELEMETRY_TRACES_*env vars, and--telemetry-traces-*flags.How to validate
go run ./cmd/blitz --generator-type apache-common --generator-apache-common-rate 1s --output-type stdout --telemetry-traces-otlpendpoint localhost:4317 --telemetry-traces-insecureblitz.sessionspan with a childblitz.generator.runspan arrives at thecollector.
--telemetry-traces-*flags and confirm blitz runs with no spans exported.go test ./internal/runtime/... ./internal/telemetry/traces/... ./output/...covers thespan lifecycle, the OTLP exporter seams, and the emit-span gating.
go test ./internal/config/...covers the flag, env, and default for each new setting.Checklist