Zabbix Discovery Knowledge Finishing

Discovery translated into Chinese is "found", accurate speaking should be auto Discovery, that is, "automatic discovery", but everyone's subconscious has been set to Discovery automatic discovery.

Autodiscover is available in Zabbix in three ways: 1. Network Discovery (Discovery); 2. (running in) Active mode proxy autoenrollment (active Zabbix agent auto-registration) ; 3. Low Level Auto Discovery (low-level discovery).

(i) Network discovery. Zabbix's network discovery can work according to the following information:

1.IP address Range

2. Operational status of the service (SSH, LDAP, SMTP, FTP, HTTP, HTTPS, POP, NNTP, IMAP, TCP, Telnet, Zabbix agent, SNMPV1 agent, SNMPv2 agent, SNMPV 3 Agent, ICMP Ping.)

3. Obtaining data from the Zabbix agent

4. Getting data from the SNMP agent

Due to the complexity of the Monitoring object (device type, device kind, protocol), Zabbix's network discovery is not yet able to obtain the network topology.

The principle of service-based operation Discovery is that except SNMP is by querying the SNMP OID, the rest of the Zabbix net.tcp.service[] function is implemented

(ii) automatic proxy registration for Active mode

This mode is relatively small in practice, but when the number of servers is relatively long, this mode is more useful. This mode is applied only if the monitoring object (usually the server host device) has properly installed the agent and configured the hostname (HOSTNAME) and the Active server address (activeserver). and configure Hostmetadata and Hostmetadataitem (one for both), usually hostmetadata is a type of operating system name such as Linux or Windows, or it can be a name for a class of machines, such as Cisco or Dell, Hostmetadataitem is typically a key-value name used to identify the host, such as System.uname. If more than one hostmetadata is needed for a more delicate identification of which type of operating system the manufacturer model is, you can separate multiple keywords with a space in a single line of hostmetadata, such as the Linux Cisco UCS Cseries.

This method can also bind a specific action, and then add the host through the action's operation, add it to the host group, bind the specific template, and so on.

(iii) Low-level auto-discovery

Low-level Autodiscover is used for some specific templates (template), which are usually inherent in the system, with some Autodiscover rules configured in the template ("configuration" → "Templates" → "Discovery"), Used to automatically add some items that are specific to certain types of hosts. These items include partitions in the file system, interface and number of network cards, number of CPUs and cores, and SNMP OIDs.

Users can also configure some auto-discovery rules to replace manually added problems, such as automatic discovery of port monitoring, disk IO, and so on.

Resources:

Zabbix official version 2.4 documentation Https://www.zabbix.com/documentation/2.4/manual/discovery/low_level_discovery

Zabbix Items Type: https://www.zabbix.com/documentation/2.4/manual/config/items/itemtypes/zabbix_agent

--end--

This article is from "Communication, My Favorites" blog, please make sure to keep this source http://dgd2010.blog.51cto.com/1539422/1705106

Zabbix Discovery Knowledge Finishing