-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add automated speedtest followups and store results #92
Comments
One way to figure out if there are new nodes is to query Andrew's API a few hours apart 2 weeks ago, vs now, and diff it. That's very un-ideal, but shrug. |
@WillNilges You could also diff the existing API. Actually this is an "everything table" so it's pretty big. Might be easier to diff Andrew's data. |
would also be good to somehow automate or require this to be run at initial completion of the install. that first run would store the baseline data with which to compare. |
@margsuarez I agree we should store the results of the speed tests we already run. We can take the max to figure out the best case. |
We'd like a way to automatically follow up on completed installs. Two weeks after an install is completed, the support bot should run a speedtest on the node and ensure it's above some baseline, and store the result. If it's not above the baseline, it should alert someone. It could also do a speedtest on the upstream hubs to compare.
Additionally, when a speedtest is run, the results should be stored in a database, and every time a speedtest is run, the past results are called up to compare.
The text was updated successfully, but these errors were encountered: