feat(o11y): lifecycle startup-latency metrics via new runtime weaver registry (PIPE-1066) - #291
Open
Dylan-M wants to merge 1 commit into
Conversation
This was referenced Aug 6, 2026
feat(o11y): per-instance metrics via injectable MeterProvider, drop package globals (PIPE-1066)
#285
Open
Open
Contributor
Author
This was referenced Aug 6, 2026
Dylan-M
force-pushed
the
dylanmyers/pipe-1066-lifecycle-metrics
branch
from
August 11, 2026 19:32
2388758 to
be2b515
Compare
2 tasks
…registry (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-lifecycle-metrics
branch
from
August 14, 2026 19:22
be2b515 to
c52f955
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 startup-latency metrics through a new
internal/runtime/monitoringweaver registry:blitz.module.startup.duration(per module),blitz.session.startup.duration, and theprocess-level
blitz.startup.duration.runtime.Newnow takes a MeterProvider andreturns an error; both call sites (the embed runner and
service.New) are updated.runtime.Startrecords the per-module and session latencies. The main entry pointrecords the process-level latency best-effort, so a metric-build failure never fails
startup.
How to validate
go run ./cmd/blitz --generator-type apache-common --generator-apache-common-rate 1s --output-type stdout --metrics-port 9100curl -s localhost:9100/metrics | grep -E 'blitz_module_startup_duration|blitz_session_startup_duration|blitz_startup_duration'.go test ./internal/runtime/...covers the recording and theNewMetricserror path.make generate-o11y-checkregenerates the weaver metric code and fails on any drift fromthe committed files (needs Docker, matching CI).
Checklist