Repository navigation
fix(client-runtime): omit machine labels from relay spans - #30940
Mr-Neutr0n wants to merge 1 commit into
Conversation
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — Removes machine labels from relay connection-attempt spans while retaining IDs, target kinds and connection diagnostics. The change reduces telemetry exposure without altering connection behavior. You can add or adjust custom eligibility rules. Learn more. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Thanks for the review! Nice to keep the connection diagnostics useful while sending a little less identifying data. |
|
Added the attribution to the PR description to match the repository convention. Model: GPT-6.1 Sol. Harness: Codex in T3 Code. |
Built-in relay connection spans include
environment.label, which can be the user's computer name. The existing environment ID already identifies the connection for diagnostics, so exporting its human-readable label adds unnecessary identifying data.Remove that attribute from the relay connection-attempt span. Retain environment ID, target kind, attempt/outcome metadata, UI labels, and local diagnostics. This is a focused data-minimization change to existing diagnostics, with no new setting or connection behavior.
Validation on macOS with Node 26.12.1:
environment.labelwas exported.vp run check:changedpasses the changed-file checks.Scope is the explicit span attribute. Arbitrary error-message redaction is separate work; this does not promise that user-derived text can never appear in diagnostic errors. No production telemetry endpoint was contacted.
Model: GPT-6.1 Sol. Harness: Codex in T3 Code.