1
0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
0 Design: Usage telemetry
Nick O'Leary edited this page 2016-10-15 20:25:16 +01:00

To help us understand how node-red is used, I want to explore the idea of having some sort of optional, fully anonymised usage reporting.

Items it could collect:

  • platform info (arch/memory etc)
  • start-up time (node scan time)
  • node-modules installed; not 'local' nodes. Need to think about how to handle private nodes. Perhaps hash the module name, so we can identify the ones known to us, but no details about private nodes are revealed

It would never collect:

  • a user's flow configuration
  • any settings
  • any identifying information (usernames etc)

Opt-in vs Opt-out

This has to be opt-in and it needs to be entirely transparent in what it collects and what it will do with the data. A user should be able to opt-out (and back in) at any time. That said, we don't want to rely on a user volunteering having read a blog post about it. We could non-intrusively prompt them in the editor to opt-in. For full transparency they user should be able to disable/remove the telemetry module entirely (optional-dependency).

Examples

  • Atom

https://github.com/atom/metrics