-
Notifications
You must be signed in to change notification settings - Fork 119
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
Add support for a minimum TTL for events #294
Conversation
46a3a33
to
5f7bad0
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.
Lgtm
The merge-base changed after approval.
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.
Lgtm
The merge-base changed after approval.
Meh! I will rebase the branches on top of main, I hope this will help! |
When running with riemann-wrappers, one may want to run different tools with distinct ttl, but the `--ttl` flag cannot be specified twice, so the following configuration will not work: ``` --- options: --ttl 300 tools: - name: "health" - name: "rdap" options: "--interval 21600 --ttl 86400 --domains example.com example.net" ``` A workaround is to add an explicit ttl for each tool, but it is not convenient. Introduce a `--minimum-ttl` flag that can be used as a global option to circumvent this issue.
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.
LGTM
When running with riemann-wrappers, one may want to run different tools with distinct ttl, but the
--ttl
flag cannot be specified twice, so the following configuration where we want to run thehealth
tool every 5 seconds (default value) but with a longer TTL than the default (twice the interval) will not work:A workaround is to add an explicit ttl for each tool, but it is not convenient.
Introduce a
--minimum-ttl
flag that can be used as a global option to circumvent this issue: