-
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] Run Once mode #28437
Labels
enhancement
Heartbeat
Team:obs-ds-hosted-services
Label for the Observability Hosted Services team
v7.16.0
Comments
andrewvc
added
enhancement
Heartbeat
Team:obs-ds-hosted-services
Label for the Observability Hosted Services team
v7.16.0
labels
Oct 14, 2021
Pinging @elastic/uptime (Team:Uptime) |
andrewvc
added a commit
to andrewvc/beats
that referenced
this issue
Oct 19, 2021
Fixes elastic#28437. This is an improvement over elastic#25972 which had a more complicated config interface.
6 tasks
andrewvc
added a commit
that referenced
this issue
Oct 20, 2021
Icedroid
pushed a commit
to Icedroid/beats
that referenced
this issue
Nov 1, 2021
* [Heartbeat] Make run_once syntax a boolean Fixes elastic#28437. This is an improvement over elastic#25972 which had a more complicated config interface. * Fix python tests * Fix python
post FF testing Works flawlessly , step to test
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Heartbeat
Team:obs-ds-hosted-services
Label for the Observability Hosted Services team
v7.16.0
Heartbeat could use a mode in which it starts, runs each monitor exactly once, then exits.
This was mostly accomplished in #25972
But now I'm thinking it would be better to just put all the monitors in
heartbeat.monitors
and add a newheartbeat.run_once: true
boolean that just changes the wayheartbeat.monitors
is handled instead.This is experimental.
The text was updated successfully, but these errors were encountered: