[ZBXNEXT-1548] Setting Host maintenance for a host from host properties Created: 2012 Dec 14  Updated: 2020 Mar 25

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 2.0.3
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Sandra Bluhm Assignee: Unassigned
Resolution: Unresolved Votes: 20
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

User's often search for a host and click on it, and want to set a downtime/maintenance mode on it.
But this is only possible in the seperate configuration menu.

It would be more intuitive if you can set a new maintenance or extend an existing maintenance in the host configuration tab, too.



 Comments   
Comment by richlv [ 2012 Dec 14 ]

probably some options that would allow to :

  • create a new maintenance with host pre-included
  • create a new maintenance with all groups that this host is member of pre-included
  • list all active or upcoming maintenances that this host is included in
  • create a new maintenance with selected hosts pre-included (from mass update)

several of these will have to handle cases when user has write access to host, but not to all hosts in the host's group (thus can not create maintenance).
in some cases host will be in maintenance that current user won't be able to change - probably those should be shown, but identified as non-modifiable

Comment by Volker Fröhlich [ 2015 Jan 16 ]

http://zabbix.org/wiki/Docs/simplify_ad_hoc_maintenance#POC_implementation

Comment by Daniel Andrei Minca [ 2018 Jul 03 ]

Hello,

Has this feature request been abandoned? It's a nice to have implementation. For now we're running Ansible tasks for putting hosts in maintenance

Comment by Matej Kotras [ 2020 Mar 25 ]

I would like to see this working, having a button and API call to Start the maintenance immediately, and then Stop the maintenance mode. With or without the possibility of specifying the window length (could be some configurable default max value set to 12 hours lets say, in case someone forgets to stop maintenance mode or automation fails in the process)

This could be used in other automation running on hosts to simply avoid manual interaction

Generated at Wed Apr 17 02:25:38 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.