Add Telemetry #264
Merged
Add Telemetry #264
Conversation
This file contains 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
NativeVision is looking to understand how our users are using the library better. To do this, we've created a telemetry API to ingest events from the application.
cjmcassar
previously approved these changes
Feb 16, 2024
robertjcolley
commented
Feb 16, 2024
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.
We at NativeVision want to understand how you are using Viro so we can prioritize address issues better. We've followed the Vercel model (down to the code they have!) found here and taken lots of inspiration from them.
Our telemetry ingestion server will be proprietary since we have API keys, but we want to make the information collected open source. Everything related to telemetry is in the components/Telemetry folder. Currently, we are just collecting specs for devices to see what our devices are users are using.
To learn more about how we do Telemetry, see here.
To opt out, follow the instructions here.
To turn on debug mode, follow the instructions here.