mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #177] Enhancement request: Time window and random value for intervals #2049
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2049
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DjMagicFingers on GitHub (Nov 11, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/177
Originally assigned to: @wh1te909 on GitHub.
When setting up a lot of devices to perform checks or run scripts by policy, the only current timing mechanism is by static amount of minutes.
That can cause an issue if 1000 devices perform speed test at the same time and the same intervals, sometimes tens of devices from the same location (same ISP).
The requested enhancement is to have better time frame definition.
For example, being able to setup static amount of minutes (let's say 120) PLUS random amount of minutes with some kind of limitation (let's say - randomly within another 120 minutes.
@wh1te909 commented on GitHub (Feb 3, 2022):
@DjMagicFingers this should now be possible with the latest task rework. you can set a random delay. let me know if it works for you