mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1843] Feature Request: Planned Maintenance #3091
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#3091
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 @datawolk on GitHub (Apr 16, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1843
Is your feature request related to a problem? Please describe.
When we perform an update of third-party software via scripts / tasks at night, windows services are stopped that are being monitored.
These updates are often scheduled days in advance so we cannot activate the maintenance during scheduling.
Because then the alerts also remain off during this period.
Describe the solution you'd like
It would be easy if maintenance could be scheduled.
For example between period x & x the server goes into maintenance and no alerts should be created.
This way we don't get false positives
Describe alternatives you've considered
Activate maintenance the night before updating starts.
But this causes a lot of overhead work that is not necessary if we can schedule maintenance.
@P6g9YHK6 commented on GitHub (Apr 16, 2024):
https://github.com/amidaware/tacticalrmm/issues/1770
@datawolk commented on GitHub (Apr 16, 2024):
Dubplicate #1770