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
We have a tracker component which consumes events from other components in core workflow. Tracker needs to analyse and instrument the events to find out which peers are participating in the cluster. This will help our operators to determine cluster health and notify other peers if they are not participating.
Proposed solution
Tracker will analyse the events to calculate which peers participated by:
If we receive parSigDBInternal event then we participated.
If we receive an parSigEx event with a given shareIdx, then that peer participated.
Return all participated peers by shareIdx (including ourselves).
Tracker will report the result as:
Only log (INFO level) which peers didn't participated and do not repeat identical logs if same set of participants didn't participate in next duty report to avoid spamming.
Set a prometheus gauge vector per peer: participationGauge.WithLabelValues(duty.Type.String(), peerName).Set(participatedBool)
The text was updated successfully, but these errors were encountered:
Implements analyse cluster participation and participation reporter to calculate cluster participation based on partial signatures exchanged and instruments the results.
category: feature
ticket: #821
Problem to be solved
We have a tracker component which consumes events from other components in core workflow. Tracker needs to analyse and instrument the events to find out which peers are participating in the cluster. This will help our operators to determine cluster health and notify other peers if they are not participating.
Proposed solution
Tracker will analyse the events to calculate which peers participated by:
parSigDBInternal
event then we participated.parSigEx
event with a given shareIdx, then that peer participated.Tracker will report the result as:
The text was updated successfully, but these errors were encountered: