-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Heartbeat] Fix monitor duration wrapper #36900
Conversation
Pinging @elastic/uptime (Team:Uptime) |
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.
The code looks good, and the behavior with manual testing seems correct. There are not, however, any tests, and I do think we should add some before merging.
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 with the one added comment mentioned prior
/test |
Fixes #36892. Monitor duration is not being calculated correctly, where start time is initialized after monitor execution and wrapping order is overriding retries event order. (cherry picked from commit 5d6c308) Co-authored-by: Emilio Alvarez Piñeiro <[email protected]>
Fixes elastic#36892. Monitor duration is not being calculated correctly, where start time is initialized after monitor execution and wrapping order is overriding retries event order.
Proposed commit message
Fixes #36892.
Monitor duration is not being calculated correctly, where start time is initialized after monitor execution and wrapping order is overriding retries event order.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
max_attempts: 2
monitor.duration.us
in the generated docs do not account for retry delays but includeresolve.rrt.us
time.