"Online" indicators suddenly dropped

The implementation matches the design doc here: https://github.com/storj/storj/blob/c2a97aeb143791dd7edd8bea5bb43558a95b57de/docs/blueprints/storage-node-downtime-tracking-with-audits.md
So there is no difference in “theory” vs. “practice” in this case.

In production, we have 12 hour windows and a 30 day tracking period - that is 60 windows per tracking period, two windows a day. Every single audit you get will affect your online score to some extent. For example, if you got audited during your 30 seconds of downtime, that offline audit will have a negative affect on your online_score. But other audits inside the same 12 hour window will be equally weighted.

So in one 12-hour window, if you get 1 offline audit and 10 total audits, your online_score for that window will be 0.9. Then, your score for that window will be averaged with all the other windows in the 30 day tracking period to calculate your overall online_score. So if you had perfect uptime outside of that 12 hour window, your online score would be (59*(1)+1*(0.9))/60 = 0.99833…

I can explain in more detail, or even point you to specific parts of the code which do the calculation. Please let me know if this explanation helped.

6 Likes