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
Collect information about peer ID here when recording rejected msg from header-sub (such as the peerID and error message) (and possibly also record the height of the rejected header).
In syncer, record height + reason for rejection here
The text was updated successfully, but these errors were encountered:
Metrics require listing and coding out all the possible rejection reasons, and they can't be arbitrary. These reasons are implementation-specific, and the Subscriber cannot know all of them internally. I think we need to have this as part of the Syncer metrics
renaynay
changed the title
p2p: Collect more information about peer and rejection reason in metric when rejecting message from header-sub
sync: Collect more information about invalid network head in metric when discarding an incoming network head
Jan 8, 2024
renaynay
changed the title
sync: Collect more information about invalid network head in metric when discarding an incoming network head
sync | p2p: Collect more information about invalid network head in metric when rejecting it
Jan 8, 2024
@Wondertan changed description now - I think it should be recorded in both places as what I want to see is peerID + height of bad header that is getting rejected. We can then correlate it to height + reason from sync metrics
Collect information about peer ID here when recording rejected msg from header-sub (such as the peerID and error message) (and possibly also record the height of the rejected header).
In syncer, record height + reason for rejection here
The text was updated successfully, but these errors were encountered: