I have servers in the farm that are always in maintenance mode (standby), this means that the MaintenanceMode=True should not be a warning.
Other than ignoring this check type on these servers, is there a way to configure the check type to accept MaintenanceMode=True as an OK condition instead of WARN?
you can create a copy of the following file: ~/share/check_mk/checks/citrix_state and place it in the same paths but with a preceding directory “local”, so ~/local/share/check_mk/checks/citrix_state.
In that copy of the file edit the line 112 to say "True": 0, in the method check_citrix_state()
This will give you a workaround to achieve what you want.
Be aware that by creating a copy of this file, you won’t get any updates from upstream anymore, so you need to take a note that you have your own version of this file.
Alternatively you can edit the original file, but have to re-apply your changes after every update.
Last but not least, you could learn how to develop plugins and then edit the one shown in the screenshot above, so that you can decide upon the state of an enabled maintenance mode by defining a rule in the WATO UI.
I am aware that I can change the file, but if I make the check_citrix_state() it will affect all hosts, I only want this on a subset of hosts, hence it should be configurable via WATO.
This plugin is part of the core product offering, how do we go about proposing these feature enhancements to checkmk developers? It seems wrong that we’re not expsosing the state as a configurable item, and hardcoding it for a WARN.
Just to add to this, in case anyone else comes across, we can use “Service state translation” to re-map the WARN into OK for check_mk-citrix_state for specific hosts using WATO.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
