Skip to content
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

[Feature request] add random times to checks #2040

Open
P6g9YHK6 opened this issue Oct 22, 2024 · 2 comments
Open

[Feature request] add random times to checks #2040

P6g9YHK6 opened this issue Oct 22, 2024 · 2 comments

Comments

@P6g9YHK6
Copy link

Is your feature request related to a problem? Please describe.
currently i have some checks that will when executed on multiple hosts at the same time will simply DDOS either a hypervisor or even a remote website/endpoint.
this also apply to a speed test that would require that each hosts test the speed at separate times.

Describe the solution you'd like
another field when creating a check that will ask for a range of time to be added before executing the check automatically
this should also apply on "run check now" when called from either the site or the client but not on the agent this is why another value is needed or would need to be calculated separately for when "run check now" is used not on the agent

Describe alternatives you've considered
all problematic scripts would have to have a snippet {{randomdelay}} and sleep them for the range set in a var
low priority stuff but i though it should still be opened

Additional context
image
image
image

@P6g9YHK6
Copy link
Author

found an exemple in eset of an imprementation of this for the same reasons
image

>   | Random delay interval setting is available for Scheduled type triggers. It defines the range of maximum delay for task execution. Randomizing can prevent overloading the server. > -- | -- > > >

@ccarney16
Copy link

ccarney16 commented Dec 9, 2024

I like this idea, though I'd much prefer something similar to ansible/ci systems where you can specify how many concurrent jobs can be run at the same time. So perhaps something like "Max Concurrent: " instead of a random delay would be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants