1 Main Features
The mesos probe has three different components:
- Mesos: It will check the health status of the mesos cluster by acessing the metrics that it exposes
- Chronos: It will check the correct behaviour of the cluster by checking that it can create a job, run it and then delete it.
- Marathon: It will check the correct behaviour of the cluster by checking that it can create a application, run it and then delete it.
- It is necessary to have a Mesos instance running with the API exposed. The same is applicable to Marathon and Chronos in case the monitoring of them is needed.
- It requires an instance of Zabbix which it can send the metrics collected.
Since the implementation of the probes is in Java, it requires, at least, a Java8 JVM to be already installed.
First of all, make sure the JRE is installed. If this is not the case, they can be installed following a few simple steps.
In order to install the JRE:
sudo add-apt-repository ppa:openjdk-r/ppa sudo apt-get update sudo apt-get install openjdk-8-jre-headless
sudo yum install java-1.8.0-openjdk-headless
Then, it is necessary to install the corresponding packages generated for the probes.
dpkg --install mesos-zabbix-probe-1.01.deb
sudo yum install https://github.com/indigo-dc/Monitoring/raw/master/zabbix-probes/mesos-zabbix-probe/MesosZabbixProbe-1.01.rpm
Running of the probes is accomplished by executing the
mesosprobe.sh command with the arguments
chronos to send the metrics corresponding to each product. So for example running
mesosprobe.sh mesos will check the metrics on the configured Mesos cluster and send them to the also configured Zabbix server.
Although the probes can be run just on demand, the best option is to configure them as Cron jobs. That can be configured by editing the configuration file with the following command:
Then, add the following lines:
00 * * * * mesosprobe.sh mesos 15 * * * * mesosprobe.sh chronos 30 * * * * mesosprobe.sh marathon
This means that the probe will run every hour at xx:00, xx:15 and xx:30 each one monitoring one aspect of the cluster and conveniently separated to avoid conflicts when sending data.
The configuration of the different parameters is accomplished by modifying the /etc/zabbix/mesosprobe.properties file:
- mesos.master.endpoint: The master endpoint and port to gather the Mesos metrics. It will check the leader node and retrieve the actual metrics from it.
mesos.metric: This property can be defined more than once. Each value of this property will be a metric retrieved from the metrics API that will be sent to the Zabbix server. Since those metrics come in the form
master/<metric>it will be sent to Zabbix as
master.<metric>key. Please make sure the key is correctly defined in the template associated to the host in the Zabbix configuration.
chronos.endpoint: URL and port of the Chronos instance
- chronos.username: Username of the chronos instance
chronos.password: Password associated to the above user
marathon.endpoint: URL and port of the Marathon instance
- marathon.username: Username of the Marathon instance
marathon.password: Password associated to the above user
zabbix.wrapper.location: Location of the Zabbix wrapper instance that will serve to register hosts dynamically
- zabbix.ip: IP of the Zabbix server to send the metrics
- zabbix.port: Optional. Port of the Zabbix server. If undefined it will use the default 10051
As for logging, the probe uses the default JDK 1.4 logging system through Apache Commons Logging. As such, a default configuration is provided in the file /etc/zabbix/mesosprobe-log.properties that will log events by default to the console and the /var/log/mesosprobe