-
Notifications
You must be signed in to change notification settings - Fork 100
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
Do not perform osquery healthchecks while system is sleeping #1284
Do not perform osquery healthchecks while system is sleeping #1284
Conversation
6dc940d
to
cb5f07e
Compare
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.
I'd take it as is, or called PowersaveMode
. I don't know that I know which feel more correct yet.
pkg/agent/flags/keys/keys.go
Outdated
@@ -47,6 +47,7 @@ const ( | |||
LogIngestServerURL FlagKey = "log_ingest_url" | |||
TraceIngestServerURL FlagKey = "trace_ingest_url" | |||
DisableTraceIngestTLS FlagKey = "disable_trace_ingest_tls" | |||
DisableOsqueryHealthchecks FlagKey = "disable_osquery_healthchecks" |
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.
Thoughts about whether should do this as DisableOsqueryHealthchecks
vs PowersaveMode
?
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.
I had gone back and forth on similar too, thinking about this versus something like InModernStandby
. I ended up on this one because the osquery extension doesn't need to know why it should skip healthchecks, just what to do -- but I do not feel that strongly about 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.
Updated per offline discussion!
5e98671
We occasionally see an issue where launcher shuts itself down on Windows while the device is sleeping, and fails to be restarted successfully. Our best guess is that while in modern standby, launcher is throttled and the osquery healthcheck therefore fails enough to shut down launcher, and the throttling prevents launcher from starting back up. This PR disables the osquery healthcheck while the system is sleeping.