software:zabbix:client_install
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| software:zabbix:client_install [2023/10/07 19:57] – created rodolico | software:zabbix:client_install [2023/12/13 01:41] (current) – rodolico | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Zabbix Client Install ====== | ====== Zabbix Client Install ====== | ||
| - | We generally use the LTS (Long Term Service) version of Zabbix, | + | Zabbix |
| - | For many common platforms, Zabbix has a configuration tool that allows you to use their repository | + | As such, I tend to download and install |
| + | https:// | ||
| - | Choose your configuration in step 1, then follow | + | Precompiled agents for Windows/ |
| - | Once the software | + | The installation process is fairly straight forward; install |
| - | Find and change them to the correct values | + | Actually, there is only one value that is required, |
| - | < | + | |
| - | Server=127.0.0.1 | + | < |
| - | Hostname=Zabbix | + | Server=ip.address.of.server |
| </ | </ | ||
| - | NOTE: simply undefining | + | A much better configuration would be to explicitly define |
| + | <code conf>Hostname=myserver.example.org</ | ||
| + | your Zabbix server will use // | ||
| + | |||
| + | ===== Linux ===== | ||
| + | |||
| + | On Debian based machines, I also include the pid and log file locations, and an Include directive. The following config is the minimum I use on these. | ||
| + | <code conf> | ||
| + | PidFile=/ | ||
| + | LogFile=/ | ||
| + | LogFileSize=0 | ||
| + | Server=ip.of.zabbix.server | ||
| + | Hostname=Name of Host | ||
| + | Include=/ | ||
| + | </ | ||
| + | |||
| + | Following is a quick script that will generate a config file. It first saves the current config | ||
| + | <code bash configZabbix> | ||
| + | #! / | ||
| + | |||
| + | # you must change this to the IP of your current Zabbix server | ||
| + | ZABBIXSERVER=ip.of.zabbix.server | ||
| + | |||
| + | # if we have not already saved the agent conf, then do so | ||
| + | if [ ! -f / | ||
| + | # write the new configuration | ||
| + | # These first two lines are Debian specific | ||
| + | echo ' | ||
| + | echo ' | ||
| + | echo ' | ||
| + | # allow traffic from ZABBIXSERVER | ||
| + | echo ' | ||
| + | # grab our hostname and specifically use it | ||
| + | echo Hostname=`hostname -f` >> / | ||
| + | # include anything in the includes directory | ||
| + | echo ' | ||
| + | # restart agent | ||
| + | service zabbix-agent restart | ||
| + | </ | ||
| + | |||
| + | Note: I have never used Active Checks (though they sound pretty cool), so I always set that IP to null (the default). | ||
| + | |||
| + | ===== Windows ===== | ||
| + | |||
| + | For Windows machines, grab the zip file from https:// | ||
| + | https:// | ||
| + | |||
| + | - Unzip the downloaded archive | ||
| + | - Create c:\zabbix | ||
| + | - Move the zabbix | ||
| + | - Edit zabbix_agentd.conf, | ||
| + | - Open an elevated command shell (cmd with Administrative privileges) and run the command < | ||
| + | - Open service manager and start the Zabbix Agent | ||
| + | - Open your firewall and allow port 10050 through | ||
| + | |||
| + | NOTE: There is a cool script at https:// | ||
| - | Restart the daemon. Assuming you have discovery turned on, just wait about an hour and it should show up on your server. | ||
software/zabbix/client_install.1696726659.txt.gz · Last modified: 2023/10/07 19:57 by rodolico
