Repository navigation
feat(telemetry): centralize event policy and process diagnostics - #7
Merged
Merged
Conversation
chore: promote Android native telemetry to main
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.
Producers and the collector previously maintained separate telemetry validation/redaction code, while client diagnostics lived inside the identity bridge. The shared SDK now owns the generated event contract, validation/redaction, bounded debug settings, typed client failure/lifecycle inputs and diagnostic status. It emits process lifecycle and redacted Rust panic records and closes a queue admission/shutdown race with explicit loss accounting. The collector consumes the same contract and recognizes client failure/recovery signals.
Validation: workspace tests and Clippy, canonical protocol regeneration, actual stdout/debug/panic/concurrent-shutdown acceptance, dependency advisory/license checks, and the real isolated PostgreSQL/Vector/OpenObserve pipeline passed on Linux. SDK/service candidate is 0.0.1-alpha.2; no release or live deployment is performed.