feat(o11y): self-logs via shared entry-point zap->OTel bridge + OTLP log export (PIPE-1066) - #287
Open
Dylan-M wants to merge 1 commit into
Open
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
…log 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-self-logs
branch
from
August 14, 2026 19:22
ce7f0a2 to
2a8a759
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
Bridges blitz's own zap logging into an OTel LoggerProvider so internal logs export as
OTLP records, opt-in through
telemetry.logs. The logger is bridged once at each processentry point (main for standalone;
config.LoadModulesand the embed runner for embed),and shared from there. A bridged zap logger propagates to the child loggers components
derive, so components do not re-bridge. Also collapses the host's flat provider fields
into the single
Host.Telemetrybundle, so one value carries all three signals.Each setting is exposed on all three config surfaces, like every other blitz option: the
telemetry.logsconfig block,BLITZ_TELEMETRY_LOGS_*env vars, and--telemetry-logs-*flags.
How to validate
go run ./cmd/blitz --generator-type apache-common --generator-apache-common-rate 1s --output-type stdout --telemetry-logs-otlpendpoint localhost:4317 --telemetry-logs-insecurerecords. They still print to stdout too.
--telemetry-logs-*flags and confirm logging stays stdout-only.go test ./embed/runsTestEmbed_HostBundleReceivesAllThreeSelfSignals, which assertsone host bundle receives metrics, spans, and bridged logs together.
go test ./internal/config/...covers the flag, env, and default for each new setting.Checklist