-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Trivial
-
None
-
Affects Version/s: None
-
Component/s: Documentation (D)
Feedback regarding Network Discovery documentation from the IRC.
- <whosgonna> sandisn: I don't recall at this point. It was not a case of it making no sense at all. It was more several small things that seemed to be a case of having to figure out how it actually worked that lead me to decide not to use the feature.
- <whosgonna> a few examples: for the protocols, what counts as discovered? Is it actually looking for the same type of response as the net services checks? - I.E. does the HTTP service type require an HTTP response, or simple handshake? Is "service port" just a successful handshake on said port?
- <whosgonna> How do these conditions staci? For exmaple, there's an option for "Discovery object" (which can be "service" or "host") in the conditions, but i don't see it documented on either of thes pages for discovery configuration: https://www.zabbix.com/documentation/2.4/manual/discovery/network_discovery or https://www.zabbix.com/documentation/2.4/manual/discovery/network_discovery/rule
- <whosgonna> and, can discovery rules apply on top of each other? For example, i want to add all hosts that have a ping resonse in a given subnet. On some of them, i want to add template X if it's responsive to http requests.
- <whosgonna> is that one rule that adds all hosts, then another that applies the template, or is it two rules, one that adds hosts if they don't have a webserver, and another that adds hosts and applies the template if they do?
- <whosgonna> one other one woudl be a definition for uptime/downtime.