Skip to content
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

chore: add separate metrics for sign respond and sign generation #149

Merged
merged 3 commits into from
Jan 29, 2025

Conversation

ChaoticTempest
Copy link
Contributor

Add additional metrics for signing:

  • signature generation latency: time taken between request received and signature generation completed.
  • respond latency: time it takes to publish the signature.
  • logging now has the elapsed times as well for signatures.

We can see how long signature generation takes a bit more precisely with this

@ChaoticTempest ChaoticTempest changed the title chore: add sign separate metrics for respond and generation chore: add separate metrics for sign respond and sign generation Jan 29, 2025
chain-signatures/node/src/metrics.rs Outdated Show resolved Hide resolved
@@ -499,6 +518,7 @@ async fn try_publish_eth(
tracing::info!(
request_id = ?CryptoHash(*request_id),
tx_hash = ?tx_hash,
elapsed = ?timestamp.elapsed(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we want latency for Ethereum?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's in a TODO. I'm leaving it up to @ppca when she gets back

chain-signatures/node/src/rpc.rs Outdated Show resolved Hide resolved
@volovyks volovyks merged commit 749e008 into develop Jan 29, 2025
2 of 3 checks passed
@volovyks volovyks deleted the phuong/chore/sign-separate-metrics branch January 29, 2025 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants