-
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] Only add monitor.status to browser summary events #29460
Conversation
Pinging @elastic/uptime (Team:Uptime) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
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.
Code LGTM and I tested this against master and the documents I was seeing were in keeping with the design goals.
we now only add monitor status to summary events for browsers. Additionally, this renames the poorly renamed wrappers/monitor* to wrappers/wrappers* (cherry picked from commit e3b1183)
@Mergifyio backport 7.17 |
we now only add monitor status to summary events for browsers. Additionally, this renames the poorly renamed wrappers/monitor* to wrappers/wrappers* (cherry picked from commit e3b1183)
✅ Backports have been created
|
#29510) we now only add monitor status to summary events for browsers. Additionally, this renames the poorly renamed wrappers/monitor* to wrappers/wrappers* (cherry picked from commit e3b1183) Co-authored-by: Andrew Cholakian <[email protected]>
#29509) we now only add monitor status to summary events for browsers. Additionally, this renames the poorly renamed wrappers/monitor* to wrappers/wrappers* (cherry picked from commit e3b1183) Co-authored-by: Andrew Cholakian <[email protected]>
Fixes #26325
we now only add monitor status to summary events for browsers. Additionally, this renames the poorly renamed
wrappers/monitor*
towrappers/wrappers*
Why is it important?
monitor.status
should really only be set on unique components of events that constitute a full check. For lightweight checks that means checking an individual IP etc. A step represents progress toward a check, not the check itself. Hence this change.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
We'll want to check that this doesn't break any features in the synthetics UI as well. I'd index to kibana and check that nothing breaks.