I know of the existence of discovery in the data collection section but I can't see how I could match everything I want (maybe my lack of knowledge).
What I want to do is scan a subnet of IP's and if pingable check certain additional ports and/or try open a http connection and parse the result to know what kind of device is living on the IP.
Now the manual is written to do discovery for host where a zabbix agent is running. That part is clear.
See if http is available is also clear but then the tricky part comes in with the default functionality. I don't see how I could then filter out these device base on lets say html title or even better specific html body content.
Is it correct that my 'wish' to detect specific host based on html content isn't possible?
And if so, what would be the best approach to create host from a running script> zabbix API or use zabbix trapper and LLD discovery on virtual host? And why
I'm not certain if the Zabbix API route would delete a host if it's not detected for X amount of time (where LLD is able to do that)
What I want to do is scan a subnet of IP's and if pingable check certain additional ports and/or try open a http connection and parse the result to know what kind of device is living on the IP.
Now the manual is written to do discovery for host where a zabbix agent is running. That part is clear.
See if http is available is also clear but then the tricky part comes in with the default functionality. I don't see how I could then filter out these device base on lets say html title or even better specific html body content.
Is it correct that my 'wish' to detect specific host based on html content isn't possible?
And if so, what would be the best approach to create host from a running script> zabbix API or use zabbix trapper and LLD discovery on virtual host? And why
I'm not certain if the Zabbix API route would delete a host if it's not detected for X amount of time (where LLD is able to do that)
Comment