Table of Contents
1 Monitor Linux with Áú»¢¶Ä²© agent
Introduction
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 Linux machine. If you are looking for deep customization options or require more advanced configuration, see Configuration section of Áú»¢¶Ä²© manual.
Prerequisites
Before proceeding with this guide, you need to download and install Áú»¢¶Ä²© server and Áú»¢¶Ä²© frontend according to the instructions for your OS.
Install Áú»¢¶Ä²© agent
Áú»¢¶Ä²© 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.
Configure Áú»¢¶Ä²© for monitoring
Áú»¢¶Ä²© 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.
Passive checks
Áú»¢¶Ä²© agent
1. Open the Agent configuration file on the machine where the Agent is installed.
2. Add the IP address or DNS name of your Áú»¢¶Ä²© server to the Server parameter.
3. Restart Áú»¢¶Ä²© agent.
Áú»¢¶Ä²© frontend
1. Log in to Áú»¢¶Ä²© frontend.
2. Create a host in Áú»¢¶Ä²© web interface.
- In the Host name field, enter a host name (e.g., "Linux server").
- In the Templates field, type or select the template "Linux by Áú»¢¶Ä²© agent" that will be linked to the host.
- In the Host groups field, type or select a host group (e.g., "Linux servers").
- In the Interfaces parameter, add Agent interface and specify the IP address or DNS name of the Linux machine where the Agent is installed.
3. Click on Add to add the host. This host will represent the monitored Linux machine.
Active checks
Áú»¢¶Ä²© agent
1. Open the Agent configuration file on the machine where the Agent is installed.
2. Add the IP address or DNS name (and optional port) of your Áú»¢¶Ä²© server to the ServerActive parameter. For example:
Áú»¢¶Ä²© agent will use this address to connect to Áú»¢¶Ä²© server's trapper port (default: 10051) and request the configuration data for active checks.
3. Define the Hostname parameter, which must match the host name that will be defined in Áú»¢¶Ä²© frontend. In our example, it is:
The Hostname value must match because, for active checks, Áú»¢¶Ä²© agent uses it to retrieve the correct host configuration from the server. Specifically, the Agent initiates a connection to the Server and identifies itself using the Hostname value. The Server then provides the monitoring configuration for that host. If these values differ, the Agent will not receive the appropriate configuration, resulting in missing metrics or monitoring issues.
4. Restart Áú»¢¶Ä²© agent.
Áú»¢¶Ä²© frontend
1. Log in to Áú»¢¶Ä²© frontend.
2. Create a host in Áú»¢¶Ä²© web interface.
- In the Host name field, enter a host name (e.g., "Linux server") that matches the Hostname parameter value defined earlier in the Agent configuration file.
- In the Templates field, type or select the template "Linux by Áú»¢¶Ä²© agent active" that will be linked to the host.
- In the Host groups field, type or select a host group (e.g., "Linux servers").
- Leave Interfaces undefined; an interface is not necessary for active checks because the Agent initiates the connection to the server instead of listening for a connection from the server.
3. Click on Add to add the host. This host will represent the monitored Linux machine.
View collected metrics
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.
Set up problem alerts
Áú»¢¶Ä²© 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.
Test your configuration
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:
- Creating an item - how to start monitoring additional metrics (custom monitoring without templates).
- Áú»¢¶Ä²© agent items, Áú»¢¶Ä²© agent items for Windows - full list of metrics you can monitor using Áú»¢¶Ä²© agent on Windows.
- Problem escalations - how to create multi-step alert scenarios (e.g., first send message to the system administrator, then, if a problem is not resolved in 45 minutes, send message to the data center manager).
- Installation from packages - how to install Áú»¢¶Ä²© components using official RPM and DEB packages for various Linux distributions, ensuring access to the latest features and bug fixes.