2 New host

Overview

In this section you will learn how to set up a new host.

A host in Zabbix is a networked entity (physical, virtual) that you wish to monitor. The definition of what can be a “host” in Zabbix is quite flexible. It can be a physical server, a network switch, a virtual machine or some application.

Adding host

Information about configured hosts in Zabbix is available in Configuration → Hosts. There is already one pre-defined host, called “Zabbix server”, but we want to learn adding another.

To add a new host, click on Create host. This will present us with a host configuration form.

2 New host - 图1

All mandatory input fields are marked with a red asterisk.

The bare minimum to enter here is:

Host name

  • Enter a host name. Alphanumerics, spaces, dots, dashes and underscores are allowed.

Groups

  • Select one or several existing groups by clicking Select button or enter a non-existing group name to create a new group.

All access permissions are assigned to host groups, not individual hosts. That is why a host must belong to at least one group.

IP address

  • Although not a required field technically, you may want to enter the IP address of the host. Note that if this is the Zabbix server IP address, it must be specified in the Zabbix agent configuration file ‘Server’ directive.

Other options will suit us with their defaults for now.

When done, click Add. Your new host should be visible in the host list.

2 New host - 图2

The Availability column contains indicators of host availability per each interface. We have defined a Zabbix agent interface, so we can use the agent availability icon (with ‘ZBX’ on it) to understand host availability:

  • 2 New host - 图3 - host status has not been established; no metric check has happened yet

  • 2 New host - 图4 - host is available, a metric check has been successful

  • 2 New host - 图5 - host is unavailable, a metric check has failed (move your mouse cursor over the icon to see the error message). There might be some error with communication, possibly caused by incorrect interface credentials. Check that Zabbix server is running, and try refreshing the page later as well.