#709 introduced the concept of user-configured devices. Add some telemetry tracking to see how frequently users are leveraging this.
This is what we want to track:
- for the current network:
- how many devices are there total (via configured or discovered)
- how many devices are manually configured
- how many devices are manually configured specifically in user (global) settings
- how many devices are manually configured specifically in workspace settings
Key points:
- send an event whenever the user clicks the "refresh" button. (this helps us know if we have problems with the list not being fresh enough). This event should track the current state of the devices list (which will give us insights into why they clicked refresh). Ensure that a "devices settled" event gets fired (i.e. avoid debouncing) in this case to complete tracking on the user journey.
- send an event anytime the device list "settles" (need clarification around this, what does "settled" mean? 10s after no new devices?). Might also need some debouncing around this, we only need a small sample of
- we will NOT be collecting any specific information about devices (models, serials, etc). This is purely to help drive improvements to the experience of device management and understanding the number of Rokus on most developers' networks.
#709 introduced the concept of user-configured devices. Add some telemetry tracking to see how frequently users are leveraging this.
This is what we want to track:
Key points: