[ZBXNEXT-818] Discovery rule for only already registered hosts Created: 2011 Jun 17 Updated: 2015 Mar 03 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F), Server (S) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Pavel Stros | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 2 |
Labels: | autoregistration, networkdiscovery | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
Auto-discovery feature enables to assign template to host as a result of the "Zabbix agent" besed (tcp/10050) periodic network scan. Usage scenarios: Would be nice to have an option to limit the post-discovery to a specific host group, host, or hosts that are assigned a specific template. |
Comments |
Comment by richlv [ 2011 Jun 17 ] |
that sounds very similar to low level discovery (http://www.zabbix.com/documentation/2.0/manual/discovery/low_level_discovery) |
Comment by Pavel Stros [ 2011 Jun 17 ] |
Sounds similar but is not the same. Low level discovery is for discovering instances of a known object. Post-discovery could assign a predefined static set of monitored items (a template) to a particular host. For example: if "VMware tools service" service is detected on host, a template "Template-VMW_guest_performance_counters" could be assigned to host automatically. In fact, the suggested post-discovery is almost equal to auto-discovery, but does not require the IP scan of an IP range, because the hosts are already known to Zabbix server od proxy. |
Comment by Oleksii Zagorskyi [ 2012 Nov 22 ] |
ZBXNEXT-306 asks for almost opposite, so they both could be implemented by supporting a clause "IS" and "IS NOT" at discovery rule level or at operation condition level. I'd prefer discovery rule level for this feature. |
Comment by richlv [ 2013 Mar 23 ] |
see also ZBXNEXT-1347 |