Capture and persist various pieces of registration information.
Capture attributes:
Registration:
Organizational name (optional) [Account id]
Owner / device name
Hostname (pre-populate)
Endpoint settings:
HTTP(S) endpoint URL
HTTP Event Collector Token
Security & Certs
Proxy settings (For reporting test results)
Network Interfaces
All / Wired / Wireless / Specific interface name(s) / First-Random (default); Eventually a drop-down will be very helpful here.
Proxy settings
Information to collect (long-term)
Error reporting
Network card info (NIC drivers and versions)
Basic OS info
Geo location (Captured live fro GPS device; different than statically derived from IP, which is automatic.)
Scheduling
Period/Frequency: Default to daily
Variation: default to 10 mins
Back-off mode
Wifi-blacklist: Don't run speedtests on metered-WiFi networks.
The first version, this can simply be editing a configuration file (as long as the user is provided with a template and some instructions; eventually there should be a CLI edit mode and UI options as well.)
It's very likely that not all of these options are needed initially. The above list is from a brainstorm, and needs more thought.
Eventually to include scheduling preferences. And the GUID should be generated at this same time, although it may be stored in a different config file.
Capture and persist various pieces of registration information.
Capture attributes:
The first version, this can simply be editing a configuration file (as long as the user is provided with a template and some instructions; eventually there should be a CLI edit mode and UI options as well.) It's very likely that not all of these options are needed initially. The above list is from a brainstorm, and needs more thought.
Eventually to include scheduling preferences. And the GUID should be generated at this same time, although it may be stored in a different config file.