Set an accelerated distributed_interval in the osquery config for the osquery instance startup period #2063
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… osquery instance startup period
James-Pickett
approved these changes
Jan 24, 2025
zackattack01
approved these changes
Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2056.
Some checks are unavoidably slow to run. When these checks become stale -- for example, if a user has turned off a device for the weekend -- we want to run them again as soon as possible, to avoid slowing down the authentication process. This PR shortens osquery's
distributed_intervaloption for the first ten minutes after the instance starts up, so that osquery will request these distributed queries more quickly.