phase1d: add telemetry module with tier-selection events#292
Closed
MGudgin wants to merge 0 commit into
Closed
Conversation
1a3f242 to
15b40af
Compare
b591eb9 to
fb3a708
Compare
15b40af to
69c3d62
Compare
fb3a708 to
ff81092
Compare
af72afa to
eabb1c2
Compare
eabb1c2 to
16269fd
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.
📖 Description
Introduces a platform-agnostic
telemetrymodule definingIsolationTierandTelemetryEventtypes, plus anemit()helper that writesMXC_TELEMETRY-prefixed lines through the existingLogger.No callers yet — emit sites land in phase1_integrate (AppContainer runner) and phase4 (dispatcher).
🔗 References
Stacked on top of #291 (phase1c → phase1b).
🔍 Validation
cargo testcleanWin25H2Safe-Tests.ps1in phase5 (held)