Repository navigation
feat(performance): add bounded monitoring contracts and benchmark harness - #949
Merged
Merged
Conversation
Define collection ownership, bounded local evidence, user-facing investigation flows, and measurable rollout gates before changing production diagnostics. Refs #944
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.
The always-on monitor needs a bounded, content-minimized foundation before production collection is enabled. This adds a finite operation vocabulary, strict renderer record validation, queues bounded by count and conservative wire bytes, and mergeable latency histograms that retain sample weighting and explicitly represent overflow.
A synthetic producer benchmark measures validation/queue/histogram cost without reading user data or claiming whole-application overhead. The detailed rollout plan is included as the first branch commit. Production collection and UI are unchanged in this first stage.
Fixes #948
Refs #944
Validation:
The remaining collector, product UI, incident, durable history, and profiling stages stay open under #944. Packaged-app/Intel/long soak validation has not been performed at this foundation stage.
Review: two independent Agent Code orchestration agents reviewed this PR. Sparse histogram buckets, fabricated empty-window totals, and impossible bucket-weighted sums were corrected with regressions; both reviewers verified the final head with no further findings. No baseline collection or UI is enabled by this foundation PR alone.
CI passed on head 5cda062 (quality gate and minimum-Node fixture gate).