mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #511] Possibility to add multiple automation policy to one site #2265
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#2265
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 @lclainsg2a on GitHub (May 14, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/511
Describe the solution you'd like
It would be nice if we can add multiple automation policy for one site.
Describe alternatives you've considered
Or add the possibility to exclude specifics agents for a specific task or check from an automation policy.
Thanks
@dinger1986 commented on GitHub (May 14, 2021):
Is that per machine? Or where would this be used?
@lclainsg2a commented on GitHub (May 14, 2021):
Actually, I want to exclude this specific agent for checking my Wireguard server.
Maybe we can add a button "Exclude" in the submenu :
@dinger1986 commented on GitHub (May 14, 2021):
But would you not be better just manually adding ping checks to the devices you want to?
EG I have one device on a network doing ping checks and speed tests for internet
@lclainsg2a commented on GitHub (May 14, 2021):
Yes, I will do that for my 250 agents.
Thanks
@dinger1986 commented on GitHub (May 14, 2021):
I was making a suggestion, I wouldnt have thought on a network you need every machine to be pinging a server, but its your network,
I suggest reopening this and letting the dev decid.
I was trying to fully understand what you were asking for as at the moment you can assign an automation policy to individual machines and block the inheritance so from there you could add other checks
@WouterLS commented on GitHub (May 14, 2021):
It would be nice to have the checks have some kind of assignment policy so you could define that a certain check only gets deployed on certain agents.
for instance: ping check Wirecheck - only deploy if IP = 192.168.x.x or location is xxx