Monitor platform servers

1 All servers
2 Abiquo server
3 Datanode services
4 Abiquo remote services
5 Abiquo watchtower
6 Abiquo reporting

This document is a guideline about which elements to monitor in your installation.

This is to assure service levels and proactively detect possible failures before your end customers do.

You can use your own preferred monitoring platform. It should have the capability to alert about service outages as well as retrieve and graph performance metrics.

In a distributed installation, you should monitor the following elements on every server.

If you have a distributed HA cluster environment, then you should monitor the services on the datanode in the same way.

We have given the process name, the port where the service would be listening, and also interesting parameters for which to get metrics values.

All servers

Monitor the following parameters on ALL platform servers:

CPU usage
RAM usage
Network availability
Filesystem space used and remaining

Abiquo server

In a distributed environment, the server would host Abiquo API, UI, websockify, and M services, it may also have the queue system RabbitMQ, Redis, and MariaDB database.

Service	Parameters

Service	Parameters
Abiquo API
	abiquo-tomcat service running
	apache tomcat / JVM performance parameters
	port 8009/HTTP listening
	port 8010/AJP listening
	Login service available (`curl -u admin -p xabiquo http://abiquo_server:8009/api/login`)
Abiquo UI
	httpd service running
	Apache web server performance parameters
	port 80/HTTP listening
	port 443/HTTPS listening
	UI service available (`curl http://abiquo_server:80/ui`)

Datanode services

These services may be with the Abiquo API or on a separate server

Service	Parameters

Service	Parameters
RabbitMQ
	rabbitmq service running
	port 5672/AMPQ listening
	queue status ( `rabbitmqctl list_queues name messages consumers` )
	queue status - Number of messages queued ( increase on this number indicates a global problem )
	queue status - Number of consumers ( Each queue must have at least one connected consumer )
	RabbitMQ performance parameters
Redis
	redis service running
	Port 6379/TCP listening
	Redis performance parameters
MariaDB
	service mysql running
	Port 3306/TCP listening
	MariaDB performance parameters

Abiquo remote services

This server need to be checked for Abiquo remote services components, Redis database and DHCP Service.

Service	Parameters

Service	Parameters
Abiquo RSS
	abiquo-tomcat service running
	apache tomcat / JVM performance parameters
	port 8009/HTTP listening
	port 8010/AJP listening
Redis
	redis service running
	Port 6379/TCP listening
	Redis performance parameters
DHCP
	dhcpd service running
	Port 7911/TCP OMAPI running
Guacamole
	Port 4822/TCP listening
NFS
	nfs repository availability
	NFS performance
	NFS free space

Abiquo watchtower

Host watchtower components in charge of monitoring and alerting services.

Service	Parameters

Service	Parameters
Abiquo watchtower
	service abiquo-emmett running
	Port 36638/TCP listening
	service abiquo-delorean running
Cassandra
	service cassandra running
	Port 9160/TCP listening
	Cassandra performance parameters
KairosDB
	service kairosdb running
	Port 8080/TCP listening

Abiquo reporting

This node includes jasperserver packages.

Service	Parameters

Service	Parameters
JasperServer
	service mysql status ( Kinton replica )
	MariaDB replication status
	MariaDB performance parameters
	service jasperserver running
	PostgresQL service running