# Debian / Ubuntu
apt-get install bloonix-agent
# Red Hat / CentOS / Fedora
yum install bloonix-agent
# SuSE / SLES
zypper install bloonix-agent
The configuration file of the agent:
/etc/bloonix/agent/main.conf
To monitor the local system, you have to configure two sections.
Example configuration:
server {
host p1.bloonix.de, s1.bloonix.de
port 5460
mode failover
ssl_verify_mode peer
# Debian / SuSE / SLES
ssl_ca_path /etc/ssl/certs
# Red Hat / CentOS / Fedora
ssl_ca_file /etc/pki/tls/certs/ca-bundle.crt
}
Please replace the hostnames in the section _server__ with the hostname or ip address of the host where the Bloonix-Server were installed.
Notice: If the Bloonix-Server uses a self signed certificate then you have to set the SSL parameter ssl_verify_peer to none, otherwise the Bloonix-Agent throws an error because the agent is unable to validate the certificate.
Example configuration:
host {
host_id 12345
password secret
}
In the section host it is configured the Host which was furnished in the WebGUI. Put down the Host-ID and the password. Then you can restart the agent, so that this is begun with the new configuration.
/etc/init.d/bloonix-agent restart
# or
systemctl restart bloonix-agent.service
If this agent is a central agent to monitor multiple hosts, as for example Router and Switches by SNMP, you can also put down these hosts.
host {
host_id 12345
password secret
}
host {
host_id 12346
password secret
}
host {
host_id 12347
password secret
}