After upgrading to Zabbix 7.0.6, my Windows VM's are triggering pretty frequently for system restarts when the VM's are not restarting. It's not the issue I've seen came up on some past posts where the same hostname being configured on multiple servers for active checks.
I'm using the default windows OS template where the trigger is as follows: change(/hostname/system.uptime)<0
Attached a graph for one of my VM's. It's not really happening on any kind of pattern and appears to be random for every host it's affecting. This is only happening on Windows 10 Pro/Server 2019 VM's, not on my bare metal hosts and older OS VM's using the same trigger.
No changes have been made to the agents or agent configs and this was not an issue before the upgrade when I was on zabbix 6.4. Nothing of note in the agent logs either.
Anyone have an idea of what's going on and what I should look into next?
I'm using the default windows OS template where the trigger is as follows: change(/hostname/system.uptime)<0
Attached a graph for one of my VM's. It's not really happening on any kind of pattern and appears to be random for every host it's affecting. This is only happening on Windows 10 Pro/Server 2019 VM's, not on my bare metal hosts and older OS VM's using the same trigger.
No changes have been made to the agents or agent configs and this was not an issue before the upgrade when I was on zabbix 6.4. Nothing of note in the agent logs either.
Anyone have an idea of what's going on and what I should look into next?