-
Notifications
You must be signed in to change notification settings - Fork 679
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: record validation and end-to-end response time in signer metrics #5664
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.
LGTM. I just left one optional comment. Feel free to ignore it.
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
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.
See comments. Otherwise looks good. Thanks!
to reduce the amount of `cfg` macros needed
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!
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.
This is much cleaner and much easier to reason about. Thanks @hstove!
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This PR adds two metrics:
stacks_signer_block_response_latencies_histogram
: this measures the "end-to-end" time that the signer takes to respond to a block proposal. The block's timestamp is used as the "start time", so this isn't a totally fair end-to-end measurement, but it's directionally accurate.stacks_signer_block_validation_latencies_histogram
: thevalidation_time_ms
reported by the node when validating a block proposal