You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
found an exemple in eset of an imprementation of this for the same reasons
> | 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.
> -- | --
>
>
>
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
The text was updated successfully, but these errors were encountered: