charon icon indicating copy to clipboard operation
charon copied to clipboard

Calculate failed duties counter per pubkey

Open dB2510 opened this issue 2 years ago • 0 comments

🐞 Bug Report

Description

Currently, tracker considers failure per duty for all the active validators rather that per duty per pubkey/validator. This causes reporting of wrong metrics as if attestation from one validator fails the chain_inclusion step in a slot it reports failures for all the validators in that slot.

Has this worked before in a previous version?

Yes, this was working until v0.16.0. This came up in v0.17.0 where we added chain_inclusion step in tracker.

🔥 Error

This screenshot is from hashquark 3 node cluster, we can see from here is bcast reported broadcast of around 1 million attestations while tracker reporting failures in most of them: Screenshot 2023-09-19 at 4 41 03 PM

🌍 Your Environment

Anything else relevant (validator index / public key)? Test the fix in hashquark clusters.

dB2510 avatar Sep 19 '23 11:09 dB2510