feat(o11y): bring stdout/nop outputs fully into the self-telemetry spine (PIPE-1066) - #290
Open
Dylan-M wants to merge 1 commit into
Open
Conversation
This was referenced Aug 6, 2026
feat(o11y): per-instance metrics via injectable MeterProvider, drop package globals (PIPE-1066)
#285
Open
Contributor
Author
This was referenced Aug 6, 2026
Open
…ine (PIPE-1066) Assisted-by: Claude Opus 4.8
Dylan-M
force-pushed
the
dylanmyers/pipe-1066-stdout-nop-spine
branch
from
August 14, 2026 19:22
40fce24 to
f92de7b
Compare
Dylan-M
force-pushed
the
dylanmyers/pipe-1066-output-send-spans
branch
from
August 14, 2026 19:22
0cdadc6 to
eea38d6
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
Pulls the last two outputs into the spine. stdout and nop now take a
TelemetrySettings,build per-instance metrics, and share the bridged logger like every other output. stdout
gets a gated
blitz.output.stdout.flushspan around the real I/O. nop gets arecords-written counter but no span, since it is a synchronous no-op already inside the
emit span. The counter lets a load run measure how many records a nop output absorbed.
How to validate
go run ./cmd/blitz --generator-type apache-common --generator-apache-common-rate 1s --output-type stdout --metrics-port 9100 --telemetry-traces-otlpendpoint localhost:4317 --telemetry-traces-insecure --telemetry-traces-perbatchspanscurl -s localhost:9100/metrics | grep blitz_output_) anda
blitz.output.stdout.flushspan at the collector.--output-type nopand confirm its records-written counter climbs:curl -s localhost:9100/metrics | grep blitz_output_entries_received.go test ./output/nop/... ./output/stdout/...covers metrics, the flush span, and thenop counter.
Checklist