You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or problem you'd like to solve
in case there is a broken piece OR a time lag of more than 4 minutes (?) between audit requests, the auditScore for the specific satellite will drop WITHOUT any warning to the SNO nor any log warning / error / fatal error documented in the logs.
This can result, as far as I understand especially for huge SNs and much audit traffic, that the node will be pretty fast discualified and has no chance to recover, because the suspension mechanism is skipped as well.
Personally I was recognising this by chance, having setup a monitoring script which frequently checks the logs AND the scores. Most of the SNOs don't have anything like that and it sounds like a wormhole, if the node gets disqualified very fast without any warning.
Propose a Solution
I've understood a 1:1 logging of broken pieces and time lags between audit requests can be potentially misused for actions harmful to the ecosystem. Anyway, there must be some kind of logging, which let's the SNO be aware of technical issues. A solution can be, that the suspension score first drops, and then the audit score. Currently, the suspension score keeps 100%, while the audit score drops without any noise.
The text was updated successfully, but these errors were encountered:
Describe the feature or problem you'd like to solve
in case there is a broken piece OR a time lag of more than 4 minutes (?) between audit requests, the auditScore for the specific satellite will drop WITHOUT any warning to the SNO nor any log warning / error / fatal error documented in the logs.
This can result, as far as I understand especially for huge SNs and much audit traffic, that the node will be pretty fast discualified and has no chance to recover, because the suspension mechanism is skipped as well.
Personally I was recognising this by chance, having setup a monitoring script which frequently checks the logs AND the scores. Most of the SNOs don't have anything like that and it sounds like a wormhole, if the node gets disqualified very fast without any warning.
Propose a Solution
I've understood a 1:1 logging of broken pieces and time lags between audit requests can be potentially misused for actions harmful to the ecosystem. Anyway, there must be some kind of logging, which let's the SNO be aware of technical issues. A solution can be, that the suspension score first drops, and then the audit score. Currently, the suspension score keeps 100%, while the audit score drops without any noise.
The text was updated successfully, but these errors were encountered: