If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
Shouldn't you be matching "SVFPS_192something" instead of "Windows" in the rule?
Markku
Isn't the first condition supposed to be the matching requirement for it to work in discovery?
My understanding is that if its windows and the hostmetadata name is found it applies to that discovery rule being set. I have other ones with the wording "contains linux" and it works fine. Could the wording of the condition be the reason?
To be clear (just tested this): Your discovery rule gets the agent.hostmetadata value from the agent, and then you use it in the discovery action. Since your agent metadata is "SVFPS_something" and your discovery action just checks equality to "Windows", it won't match.
I changed the received value to contains not equals and that registered the server but its not detecting the agent installed. If I delete the current host from zabbix, make changes to the discovery rule and restart the service on windows, will this register the host again in zabbix?
I changed the received value to contains not equals and that registered the server but its not detecting the agent installed. If I delete the current host from zabbix, make changes to the discovery rule and restart the service on windows, will this register the host again in zabbix?
Yes, if you delete the host, the next discovery run will detect the host as new again.
I am going to play with the rules and see what I can get to work, seems like I am on the right track now with the modified condition i made. I will report back.
Comment