starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 06:55:52 +03:00

[GH-ISSUE #1320] Request to assign separate alert templates per device type (Workstation vs Server) #822

New issue

Closed

opened 2026-03-02 02:19:16 +03:00 by kerem · 6 comments

kerem commented

2026-03-02 02:19:16 +03:00

Owner

Originally created by @kmhadmin on GitHub (Oct 13, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1320

**Is your feature request related to a problem? Please describe. **
Nope

Describe the solution you'd like
We would like the ability to create/assign a separate workstation and server alert templates. As it is now, we can only assign one alert template that covers both Servers and Workstations. This causes an issue for our use case as we have different requirements for alerts notifications for workstations vs servers. For example, we do not want or need alerts for workstations that are offline. Also, we need to assign specific alert conditions to Servers that don't apply to workstations and would cause a lot of false alerts from the workstations.

Describe alternatives you've considered
Possible option we found was to remove all sites under each client and then create only two sites, one for workstations and one for servers which would allow us to then apply separate alert templates to each device type, but in doing this. We lose the asset organization and location tracking for each client letting us know which office/location the system is located at which now creates another issue for us.

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @kmhadmin on GitHub (Oct 13, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1320 **Is your feature request related to a problem? Please describe. ** Nope **Describe the solution you'd like** We would like the ability to create/assign a separate workstation and server alert templates. As it is now, we can only assign one alert template that covers both Servers and Workstations. This causes an issue for our use case as we have different requirements for alerts notifications for workstations vs servers. For example, we do not want or need alerts for workstations that are offline. Also, we need to assign specific alert conditions to Servers that don't apply to workstations and would cause a lot of false alerts from the workstations. **Describe alternatives you've considered** Possible option we found was to remove all sites under each client and then create only two sites, one for workstations and one for servers which would allow us to then apply separate alert templates to each device type, but in doing this. We lose the asset organization and location tracking for each client letting us know which office/location the system is located at which now creates another issue for us. **Additional context** Add any other context or screenshots about the feature request here.

kerem closed this issue

2026-03-02 02:19:16 +03:00

kerem commented

2026-03-02 02:19:17 +03:00

Author

Owner

@dinger1986 commented on GitHub (Oct 13, 2022):

You can do that.

Right click on the client and choose automation policy then assign your server policy and workstation policy

@dinger1986 commented on GitHub (Oct 13, 2022): You can do that. Right click on the client and choose automation policy then assign your server policy and workstation policy

kerem commented

2026-03-02 02:19:17 +03:00

Author

Owner

@dinger1986 commented on GitHub (Oct 13, 2022):

@dinger1986 commented on GitHub (Oct 13, 2022): ![image](https://user-images.githubusercontent.com/7244447/195691231-44091a64-035b-4afd-8a4e-f893dae9cf38.jpeg)

kerem commented

2026-03-02 02:19:17 +03:00

Author

Owner

@kmhadmin commented on GitHub (Oct 13, 2022):

Okay, this is what you get trying to work though testing a new product with no sleep. I see you can assign alert templates under the automation policies. I would still like to see the ability to adhoc assign a separate workstation and server alert template under the Assign Alert Template site option as this is helpful function for quick testing multiple alert templates on the fly.

@kmhadmin commented on GitHub (Oct 13, 2022): Okay, this is what you get trying to work though testing a new product with no sleep. I see you can assign alert templates under the automation policies. I would still like to see the ability to adhoc assign a separate workstation and server alert template under the Assign Alert Template site option as this is helpful function for quick testing multiple alert templates on the fly.

kerem commented

2026-03-02 02:19:17 +03:00

Author

Owner

@wh1te909 commented on GitHub (Oct 13, 2022):

create the automation policy, create the alert template, then from Automation Manager find your policy and click "Assign Alert Template"

@wh1te909 commented on GitHub (Oct 13, 2022): create the automation policy, create the alert template, then from Automation Manager find your policy and click "Assign Alert Template"

kerem commented

2026-03-02 02:19:17 +03:00

Author

Owner

@wh1te909 commented on GitHub (Oct 13, 2022):

@kmhadmin yes I agree, we do have planned a rework of policies and alerts and one of the things was to have alert templates not related to policies so you could assign then to just severs or workstations without relying on a policy. Atm the above comment is the only way to do it now until the rework. Hope that helps.

@wh1te909 commented on GitHub (Oct 13, 2022): @kmhadmin yes I agree, we do have planned a rework of policies and alerts and one of the things was to have alert templates not related to policies so you could assign then to just severs or workstations without relying on a policy. Atm the above comment is the only way to do it now until the rework. Hope that helps.

kerem commented

2026-03-02 02:19:17 +03:00

Author

Owner

@kmhadmin commented on GitHub (Oct 14, 2022):

@wh1te909 Thanks for the reply. I had someone that wasn't sleep deprived look over everything and we have worked out a way using alert templates attached to Automation Policies that will allow us to achieve what we wanted so we should be good to go now.

@kmhadmin commented on GitHub (Oct 14, 2022): @wh1te909 Thanks for the reply. I had someone that wasn't sleep deprived look over everything and we have worked out a way using alert templates attached to Automation Policies that will allow us to achieve what we wanted so we should be good to go now.

kerem referenced this issue

2026-03-14 04:08:01 +03:00

[GH-ISSUE #822] Add syntax field to Script Manager for non-Community Script #2466