This page walks you through the steps required to start basic monitoring of Linux machines with Áú»¢¶Ä²©. The steps described in this tutorial can be applied to any Linux-based operating system.
Who this guide is for
This guide is designed for new Áú»¢¶Ä²© users and contains the minimum set of steps required to enable basic monitoring of your Windows machine. If you are looking for deep customization options or require more advanced configuration, see Configuration section of Áú»¢¶Ä²© manual.
Prerequisites
Before proceeding with this installation guide, you must download and install Áú»¢¶Ä²© server and Áú»¢¶Ä²© frontend according to instructions for your OS.
Áú»¢¶Ä²© agent is the process responsible for gathering data.
Check your Áú»¢¶Ä²© server version:
Install Áú»¢¶Ä²© agent of the same version (recommended) on the Linux machine that you want to monitor. Based on your monitoring needs, it may be the same machine, where Áú»¢¶Ä²© server is installed, or a completely different machine.
Choose the most suitable installation method:
Run as a Docker container - see the list of available images in .
Install from Áú»¢¶Ä²© packages (available for Alma Linux, CentOS, Debian, Oracle Linux, Raspberry Pi OS, RHEL, Rocky Linux, SUSE Linux Enterprise Server, Ubuntu).
Compile from sources.
Áú»¢¶Ä²© agent can collect metrics in active or passive mode (simultaneously).
A passive check is a simple data request. Áú»¢¶Ä²© server or proxy asks for some data (for example, CPU load) and Áú»¢¶Ä²© agent sends back the result to the server. Active checks require more complex processing. The agent must first retrieve from the server(s) a list of items for independent processing and then bulk send the data back. See Passive and active agent checks for more info.
Monitoring templates provided by Áú»¢¶Ä²© usually offer two alternatives - a template for Áú»¢¶Ä²© agent and a template for Áú»¢¶Ä²© agent (active). With the first option, the agent will collect metrics in passive mode. Such templates will deliver identical monitoring results, but using different communication protocols.
Further Áú»¢¶Ä²© configuration depends on whether you select a template for active or passive Áú»¢¶Ä²© agent checks.
1. Log in to Áú»¢¶Ä²© frontend.
2. Create a host in Áú»¢¶Ä²© web interface.
This host will represent your Linux machine.
3. In the Interfaces parameter, add Agent interface and specify the IP address or DNS name of the Linux machine where the agent is installed.
4. In the Templates parameter, type or select Linux by Áú»¢¶Ä²© agent.
Open Áú»¢¶Ä²© agent configuration file (by default, the path is /usr/local/etc/zabbix_agentd.conf):
Add the IP address or DNS name of your Áú»¢¶Ä²© server to the Server parameter.
For example:
1. Log in to Áú»¢¶Ä²© frontend.
2. Create a host in Áú»¢¶Ä²© web interface.
This host will represent your Linux machine.
3. In the Templates parameter, type or select Linux by Áú»¢¶Ä²© agent active.
Open Áú»¢¶Ä²© agent configuration file (by default, the path is /usr/local/etc/zabbix_agentd.conf):
Add:
For example:
Congratulations! At this point, Áú»¢¶Ä²© is already monitoring your Linux machine.
To view collected metrics, open the Monitoring->Hosts menu section and click on the Latest data next to the host.
This action will open a list of all the latest metrics collected from Linux server host.
Áú»¢¶Ä²© can notify you about a problem with your infrastructure using a variety of methods. This guide provides configuration steps for sending email alerts.
1. Go to the User settings -> Profile, switch to the tab Media and add your email.
2. Follow the guide for Receiving problem notification.
Next time, when Áú»¢¶Ä²© detects a problem you should receive an alert via email.
On Linux, you can simulate high CPU load and as a result receive a problem alert by running:
You may need to run several processes for CPU load to exceed the threshold.
When Áú»¢¶Ä²© detects the problem, it will appear in the Monitoring->Problems section.
If the alerts are configured, you will also receive the problem notification.
See also: