[http://zabbix.com Zabbix] is a full-featured monitoring solution for larger networks. It can discover all kind of networking devices using different methods, check machine states and applications, sending pre-defined alarm messages and visualize complex data correlations.

[http://zabbix.com Zabbix] is a full-featured monitoring solution for larger networks. It can discover all kind of networking devices using different methods, check machine states and applications, sending pre-defined alarm messages and visualize complex data correlations.

−

==Server Installation==

+

==Server setup ==

=== Installation ===

=== Installation ===

−

If you want to use the Zabbix server with [[MariaDB]], install {{aur|zabbix-server-mysql}} from the [[AUR]]. For [[PostgreSQL]] as database backend, you should use {{aur|zabbix-server}}. You also have to choose a web server with PHP support, e.g.:

+

If you want to use the Zabbix server with [[MariaDB]], install {{AUR|zabbix-server-mysql}} from the [[AUR]]. For [[PostgreSQL]] as database backend, you should use {{AUR|zabbix-server}}. You also have to choose a web server with PHP support, e.g.:

*[[LAMP|Apache]]

*[[LAMP|Apache]]

*[[Lighttpd]]

*[[Lighttpd]]

Line 47:

Line 47:

DBName=zabbix

DBName=zabbix

DBUser=zabbix

DBUser=zabbix

+

DBPassword=test

</nowiki>}}

</nowiki>}}

Line 57:

Line 58:

See appendix for a link to the official documentation, which explains all further steps in using it.

See appendix for a link to the official documentation, which explains all further steps in using it.

−

==Agent (Client) Installation==

+

==Agent (Client) setup ==

−

Currently, the server package already includes {{aur|zabbix-agent}}, so you don't have to install this package on your monitoring server. However, for monitoring targets, the client part is more minimal, standalone and easy to deploy, just install {{aur|zabbix-agent}}.

+

=== Installation ===

+

Currently, the server package already includes {{AUR|zabbix-agent}}, so you don't have to install this package on your monitoring server. However, for monitoring targets, the client part is more minimal, standalone and easy to deploy, just install {{AUR|zabbix-agent}}.

===Configuration===

===Configuration===

Simply edit the zabbix_agentd.conf and replace the server variable with the IP of your monitoring server. Only servers from this/these IP will be allowed to access the agent.

Simply edit the zabbix_agentd.conf and replace the server variable with the IP of your monitoring server. Only servers from this/these IP will be allowed to access the agent.

Line 64:

Line 66:

<nowiki>Server=127.0.0.1

<nowiki>Server=127.0.0.1

ServerActive=</nowiki>}}

ServerActive=</nowiki>}}

+

Further make sure the port <code>10050</code> on your device being monitored isn't blocked and is properly forwarded.

In this example, we create on localhost a MariaDB database called zabbix for the user zabbix identified by the password test and then import the database templates. This connection will be later used by the Zabbix server and web application:

Starting

To enable the and start server process, run:

systemctl enable zabbix-server
systemctl start zabbix-server

Finally you can access Zabbix via your local web server, e.g.: http://127.0.0.1/zabbix , finish the installation wizard and access the frontend the first time. The default username is Admin and password zabbix.

See appendix for a link to the official documentation, which explains all further steps in using it.

Agent (Client) setup

Installation

Currently, the server package already includes zabbix-agentAUR, so you don't have to install this package on your monitoring server. However, for monitoring targets, the client part is more minimal, standalone and easy to deploy, just install zabbix-agentAUR.

Configuration

Simply edit the zabbix_agentd.conf and replace the server variable with the IP of your monitoring server. Only servers from this/these IP will be allowed to access the agent.

/etc/zabbix/zabbix_agentd.conf

Server=127.0.0.1
ServerActive=

Further make sure the port 10050 on your device being monitored isn't blocked and is properly forwarded.