add basic crash analytics and very light telemetry to dioxus-cli #4224
Conversation
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
jkelleyrtp
changed the title
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.
Adds some very basic, light, anonymized, infrequent, opt-out telemetry to get a better sense of panics, crashes, and usage of the CLI.
Tools like subsecond bring in lots of complexity and it's worth knowing how the CLI is being used and where it falls apart.
This adds a handful of instrumentation points
Analytics are anonymized, all paths are stripped, uploads will be infrequent (weekly or less), users can opt-out, and uploads will be done through an obvious endpoint (ie telemetry.dioxus.dev)