starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #1770] Improvement to maintenance mode add/or check alert disable #3044

New issue

Open

opened 2026-03-14 06:20:56 +03:00 by kerem · 5 comments

kerem commented

2026-03-14 06:20:56 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Feb 23, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1770

Is your feature request related to a problem? Please describe.
it is currently impossible to disable individual checks without changing the whole policy affected to the agent.
it is also impossible to plan duration for maintenances or make them limited in time.

Describe the solution you'd like
Granular Alert Suppression:
We would like the ability to selectively suppress specific types of alerts during Maintenance Mode(only check/tasks/or overdue).
Also the ability to target specific check to disable during the maintenance.
This granular would allow us to tailor the feature according to our precise requirements, ensuring that only relevant alerts are muted while critical notifications remain active.

Flexible Maintenance Window:
It would be good to have the option to define customizable maintenance windows. To allow us to specify the start and end times for Maintenance Mode based on our schedule. This flexibility ensures that alerts are muted only during the designated maintenance period.

Notification History:
Access to a log of suppressed alerts during Maintenance Mode.

Rambling:
Maybe a simple right click with a button "downtime" that asks for the set time of the DT on each individual check/tasks/agent would be the best way to handle this without too much effort and could replace all together the maintenance mode feature ?

Describe alternatives you've considered
no alernative found

Additional context
https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/downtime.html

Originally created by @P6g9YHK6 on GitHub (Feb 23, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1770 **Is your feature request related to a problem? Please describe.** it is currently impossible to disable individual checks without changing the whole policy affected to the agent. it is also impossible to plan duration for maintenances or make them limited in time. **Describe the solution you'd like** _Granular Alert Suppression:_ We would like the ability to selectively suppress specific types of alerts during Maintenance Mode(only check/tasks/or overdue). Also the ability to target specific check to disable during the maintenance. This granular would allow us to tailor the feature according to our precise requirements, ensuring that only relevant alerts are muted while critical notifications remain active. _Flexible Maintenance Window:_ It would be good to have the option to define customizable maintenance windows. To allow us to specify the start and end times for Maintenance Mode based on our schedule. This flexibility ensures that alerts are muted only during the designated maintenance period. _Notification History:_ Access to a log of suppressed alerts during Maintenance Mode. _Rambling:_ Maybe a simple right click with a button "downtime" that asks for the set time of the DT on each individual check/tasks/agent would be the best way to handle this without too much effort and could replace all together the maintenance mode feature ? **Describe alternatives you've considered** no alernative found **Additional context** https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/downtime.html

kerem added the

enhancement

label

2026-03-14 06:20:56 +03:00

kerem commented

2026-03-14 06:21:07 +03:00

Author

Owner

@datawolk commented on GitHub (Feb 26, 2024):

Would be a valuable feature!

@datawolk commented on GitHub (Feb 26, 2024): Would be a valuable feature!

kerem commented

2026-03-14 06:21:12 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (May 2, 2024):

linking this :
https://github.com/amidaware/tacticalrmm/issues/1064
as it could be well implemented inside this framework

@P6g9YHK6 commented on GitHub (May 2, 2024): linking this : https://github.com/amidaware/tacticalrmm/issues/1064 as it could be well implemented inside this framework

kerem commented

2026-03-14 06:21:17 +03:00

Author

Owner

@LPJon commented on GitHub (Aug 4, 2024):

It would also be nice to allow an Admin of the TacticalRMM Server to disable any task or check even when it is part of an automation policy for any specific device. Otherwise you have to completely deactivate the policy in order to stop the task/check from being performed. This will affect many systems which wouldn't need the policy disabled for troubleshooting.

@LPJon commented on GitHub (Aug 4, 2024): It would also be nice to allow an Admin of the TacticalRMM Server to disable any task or check even when it is part of an automation policy for any specific device. Otherwise you have to completely deactivate the policy in order to stop the task/check from being performed. This will affect many systems which wouldn't need the policy disabled for troubleshooting.

kerem commented

2026-03-14 06:21:22 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Aug 13, 2024):

It would also be nice to allow an Admin of the TacticalRMM Server to disable any task or check even when it is part of an automation policy for any specific device. Otherwise you have to completely deactivate the policy in order to stop the task/check from being performed. This will affect many systems which wouldn't need the policy disabled for troubleshooting.

Yes same as you can "mass run" a task from the policy page you could "mass disable" or "mass downtime" a single check/task
while agent overdue would need a new button on that page to set a downtime or disable on the alert for that policy

@P6g9YHK6 commented on GitHub (Aug 13, 2024): > It would also be nice to allow an Admin of the TacticalRMM Server to disable any task or check even when it is part of an automation policy for any specific device. Otherwise you have to completely deactivate the policy in order to stop the task/check from being performed. This will affect many systems which wouldn't need the policy disabled for troubleshooting. Yes same as you can "mass run" a task from the policy page you could "mass disable" or "mass downtime" a single check/task while agent overdue would need a new button on that page to set a downtime or disable on the alert for that policy

kerem commented

2026-03-14 06:21:27 +03:00

Author

Owner

@silversword411 commented on GitHub (Oct 28, 2025):

You can do it right now with Agent installed on TRMM server, script, and API calls...for those with a desire for exploration.

@silversword411 commented on GitHub (Oct 28, 2025): You can do it right now with Agent installed on TRMM server, script, and API calls...for those with a desire for exploration.