-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telemetry #327
Comments
for Size of application see #320 |
A few more assumptions… Also track:
Explicit list of things to never collect:
Mechanism:
Do we care about forgery or spam? How would we prevent it?? |
Original Next.js RFC issue: vercel/next.js#8442 Taking a few notes from browsing Next.js's telemetry code: There's a DEBUG flag you can set to see exactly what's being sent (this also disables telemetry). https://github.com/vercel/next.js/blob/v14.0.4/packages/next/src/telemetry/storage.ts#L288 Users gets a stdout magenta notification that telemetry is being collected, then a date is saved to not annoy them again. Some how this date is cleared if the team decides telemetry re-notification is warranted? https://github.com/vercel/next.js/blob/v14.0.4/packages/next/src/telemetry/storage.ts#L99-L102 A random session id is generated to tie together multiple events? https://github.com/vercel/next.js/blob/v14.0.4/packages/next/src/telemetry/storage.ts#L88 They send themselves hashed versions of some values (which ones?), each instance getting its own random salt to discourage un-hashing the values using a dictionary or leveraging all their users' data https://github.com/vercel/next.js/blob/v14.0.4/packages/next/src/telemetry/storage.ts#L26-L29 They spawn a detached process to submit records, seemingly to allow the main process to exit https://github.com/vercel/next.js/blob/v14.0.4/packages/next/src/telemetry/storage.ts#L231-L233 😮 There's a queue and flush thing going on https://github.com/vercel/next.js/blob/v14.0.4/packages/next/src/telemetry/storage.ts#L224 |
on every message:
anonymousId seems to be persistent and identifies me/computer/device? next dev:
huh running next build
|
|
Just noticed https://docs.brew.sh/Analytics. A practice from them which is new to me is they try to make sure to banner you before any analytics are ever sent. |
When CLI launches, we'll want to track as much info as we can about who's using the CLI and what they're doing. It would be great even as we're testing internally to start reporting on some numbers.
Ideally we could track something like:
This would be an opt-out.
Heavily borrowed/inspired from Next.js
The text was updated successfully, but these errors were encountered: