feat: headless-host metrics and stress fleet#269
Draft
eugypalu wants to merge 5 commits into
Draft
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
…ing-bot, per-VU metrics)
…pt mislabel, wire-layout test, doc/fleet cleanup)
eugypalu
force-pushed
the
eugenio/headless-host-stress
branch
from
July 17, 2026 11:04
c9d02de to
59e99a9
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
1 participant
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 measurement layer for the headless host, plus a first stress fleet on top of it.
Both pieces live in
truapi-host-cli; no core changes.HostMetricRecord(category and op derived from the wire id, latency, outcome) to a JSONL sink. Recording is opt-in viaMETRICS_JSONL; unset, the recorder is a no-op and behaviour is unchanged. The outcome is decoded from the response frame, so a domain error counts as an error, not a clean dispatch.e2e/fleet.shstarts N virtual users on a ramp, each a pairing host on its own port running a flow script, paired against the signing-bot (POST /api/pair), which auto-provisions an attested user and signs per pairing. All VUs append to one shared JSONL, keyed byvuIndex.