-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
OTA update pings #697
Comments
The https://api.github.com/repos/mozilla-iot/gateway/releases endpoint lists the number of downloads for each component of the OTA update which right now shows that 5 attempts were made to OTA update to 0.3.0 from 0.2.1 and one confused person downloaded the gateway component thinking it was the gateway image. |
mrstegeman
pushed a commit
to mrstegeman/gateway
that referenced
this issue
Mar 21, 2018
This is the first step required for WebThingsIO#697.
mrstegeman
pushed a commit
to mrstegeman/gateway
that referenced
this issue
Mar 21, 2018
This is the first step required for WebThingsIO#697.
mrstegeman
pushed a commit
to mrstegeman/gateway
that referenced
this issue
Mar 21, 2018
This is the first step required for WebThingsIO#697.
mrstegeman
pushed a commit
to mrstegeman/gateway
that referenced
this issue
Mar 21, 2018
This is the first step required for WebThingsIO#697.
mrstegeman
pushed a commit
that referenced
this issue
Mar 21, 2018
This is the first step required for #697.
mrstegeman
pushed a commit
to mrstegeman/gateway
that referenced
this issue
Mar 21, 2018
Merged
mrstegeman
pushed a commit
that referenced
this issue
Mar 21, 2018
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
As Mozilla I want to log when gateways contact the update server so that I can get a better idea of the number of active gateways which may need updating
Currently we can only count the number of active gateways using our TLS tunnelling service and a *.mozilla-iot.org domain. It appears that many users are opting out of this service and choosing to use their own DNS configuration.
If we anonymously logged when a gateway contacts the OTA update server for updates, this would give us a more complete picture of how many active gateway they are requiring the use of the OTA update server so we can plan resources accordingly.
As updates are currently statically hosted on GitHub this may require changing our update infrastructure to Mozilla infrastructure in order to log this information.
The text was updated successfully, but these errors were encountered: