Skip to content
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

Investigate problems with uptime analysis for ITN. #101

Open
Sventimir opened this issue Oct 20, 2023 · 1 comment
Open

Investigate problems with uptime analysis for ITN. #101

Sventimir opened this issue Oct 20, 2023 · 1 comment
Assignees
Labels
uptime service Tasks related to the uptime service

Comments

@Sventimir
Copy link

The uptime service backend is responsible for recording and analysing the uptime submissions from nodes. The analysis script tends to produce suspicious (or outright wrong) results lately. Besides it is also very tightly coupled to AWS and Google infrastructure, which makes iot hard to test. We need to improve the testability and resolve the bad results issue. Additionally at the moment the service distinguishes submissions from different IP addresses, even if they're signed by the same key. From now on we prefer to ignore IP addresses and count all submissions from a public key for the same identity.

@Sventimir Sventimir converted this from a draft issue Oct 20, 2023
@Sventimir Sventimir self-assigned this Oct 20, 2023
@Sventimir Sventimir added the uptime service Tasks related to the uptime service label Oct 20, 2023
@Sventimir
Copy link
Author

For the moment I managed to improve testability by decopupling from GCP spreadsheet and outputting results to stdout instead. Ongoing work is available here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
uptime service Tasks related to the uptime service
Projects
Development

No branches or pull requests

1 participant