Set custom checks TTL to 1 minute to prevent clock skew issues #5257
Conversation
This file contains hidden or 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
…ing interval. This can cause issues with clock skew between instances.
ramonsmits
commented
Jan 15, 2026
mauroservienti
approved these changes
Jan 15, 2026
andreasohlund
approved these changes
Jan 15, 2026
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.
Set custom checks TTL to 1 minute, as the default TTL is 4*the reporting interval. This can cause issues with clock skew between instances.
For example, the report interval for AuditIngestionCustomCheck is 5 seconds, this means the TTL for that is 20 seconds. A clock skew of 20 seconds between hosts is not uncommon.