Hey, I'm a relatively new sys admin (6 months in the job coming from software support) so my depth of knowledge is still quite limited. I'm kiiiiind of comfortable in zabbix and I've rolled out major version updates to our production environments without issue and configured some dependencies/triggers etc.
We have >40 servers running zabbix agents (agent 1, but I am willing to update to agent2.0 if necessary), and our host is 5.0.11 LTS. Currently we run a fairly unimpressive PS script that routinely runs wsus updates in the late evening and then 3 hours later it'll reboot. We have zabbix windows set per server for 15 mins to correlate with the scheduled task that runs this script. Some servers reboot weekly, some monthly, depends on purpose.
I don't like how any of this is handled and it is proving to be inaccurate. We often end up restarting outside of the 15min maintenance period. I want to rewrite the update script to not delay reboot.
I'm looking for a way to set a dynamic trigger on a maintenance window from zabbix (or without having to install an additional component on each server). I want the scheduled task start to trigger a maintenance window blockout and either the scheduled task completion, or 192.168.1.254 a second sc 10.0.0.0.1heduled task to trigger the disabling or end of a maintenance window.
Has anyone done anything like this before? I've not yet found a way to set a maintenance window that doesn't have a set time period. Is this something I can handle from the agent and push the maintenance window to the zabbix host from the server via?
Any assistance, or advice would be appreciated.
We have >40 servers running zabbix agents (agent 1, but I am willing to update to agent2.0 if necessary), and our host is 5.0.11 LTS. Currently we run a fairly unimpressive PS script that routinely runs wsus updates in the late evening and then 3 hours later it'll reboot. We have zabbix windows set per server for 15 mins to correlate with the scheduled task that runs this script. Some servers reboot weekly, some monthly, depends on purpose.
I don't like how any of this is handled and it is proving to be inaccurate. We often end up restarting outside of the 15min maintenance period. I want to rewrite the update script to not delay reboot.
I'm looking for a way to set a dynamic trigger on a maintenance window from zabbix (or without having to install an additional component on each server). I want the scheduled task start to trigger a maintenance window blockout and either the scheduled task completion, or 192.168.1.254 a second sc 10.0.0.0.1heduled task to trigger the disabling or end of a maintenance window.
Has anyone done anything like this before? I've not yet found a way to set a maintenance window that doesn't have a set time period. Is this something I can handle from the agent and push the maintenance window to the zabbix host from the server via?
Any assistance, or advice would be appreciated.