-
Notifications
You must be signed in to change notification settings - Fork 0
feat: metrics for when blocks are submitted [ENG-702] #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Elapsed block build time is going to be fairly inaccurate because of how few blocks actually are trying to be built. It'll get better once we have some actual traffic on Test Net. For now this is a great start 🎀
@@ -54,6 +56,7 @@ impl TxPoller { | |||
self.seen_txns.entry(*tx.tx_hash()).or_insert_with(|| { | |||
// add to unique transactions | |||
unique.push(tx.clone()); | |||
counter!("builder.unique_txs").increment(1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we bucket these by block number maybe?
let mut retries = 0; | ||
loop { | ||
match self.handle_inbound(&in_progress).await { | ||
Ok(ControlFlow::Retry) => { | ||
retries += 1; | ||
if retries > 3 { | ||
counter!("builder.building_too_many_retries").increment(1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice to have for internal visibility 🔥
No description provided.