We're developing our Zabbix instance and trying to grapple with how to configure discovery rules. As we've moved through this process, we've had a hard time getting the discovery actions correct, and have deleted discovered hosts and such.
What's happening right now is that when we restart discovery, actions that are configured don't seem to re-run, even if the hosts don't exist in the system any more.
We've been using the following to clear the discovery tables, but it seems there is some sort of action log that is also in play.
The fix right now is to rebuild the discovery rule, and reconfigure the discovery actions to point to the new checks created by that rule. This is going to be unwieldy, however, as we're going to end up with around 100 rules that will need to be corrected if anything changes.
How can discovery actions get properly reset so that they re-run on new discovery data?
What's happening right now is that when we restart discovery, actions that are configured don't seem to re-run, even if the hosts don't exist in the system any more.
We've been using the following to clear the discovery tables, but it seems there is some sort of action log that is also in play.
Code:
mysql -e 'USE zabbix; SET FOREIGN_KEY_CHECKS = 0 ; TRUNCATE table dhosts ; TRUNCATE table dservices ; SET FOREIGN_KEY_CHECKS = 1;' systemctl restart zabbix-server
How can discovery actions get properly reset so that they re-run on new discovery data?
Comment