-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat: metrics for node up and signing latency #490
Conversation
Terraform Feature Environment (dev-490)Terraform Initialization ⚙️
|
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.
LGTM
@@ -120,7 +121,11 @@ async fn handle_block( | |||
epsilon, | |||
delta, | |||
entropy, | |||
time_added: Instant::now(), |
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.
nit: how about we keep it consistent with timestamp
everywhere else since timestamp is usually associated to when something is created anyways
IntGauge, IntGaugeVec, Opts, Result, TextEncoder, | ||
}; | ||
|
||
pub(crate) static NODE_RUNNING: Lazy<IntGaugeVec> = Lazy::new(|| { |
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.
is it by convention to create Lazy
values for doing metrics in prometheus? If not, we should have it be initialized from one place when the node starts up. It's hard to configure these things down the line since they're globals, but it's not something we have to do right now since there are more important things. If that's the case, then let's also create a ticket to revisit later
Terraform Feature Environment Destroy (dev-490)Terraform Initialization ⚙️
|
whether node is up, sign request count, sign success, sign latency