Monitor platform servers
- MS (Unlicensed)
This document is a guideline about which elements you must monitor on your installation to assure service level and proactively detect possible failures before your end customers do.
Monitoring technology
We let you choose your preferred monitoring platform, nowadays most major monitoring technologies have the capability to alert about service outages as well as retrieve and graph performance metrics, so it is up to you to decide which one you will use.
Services to monitor
Next you will find a list of elements to monitor on every server on a distributed installation. We will try to detail both process name, port where the service would be listening and also interesting parameters for which to get metrics values.
Common parameters
The parameters below must be monitored on all platform servers:
CPU usage
RAM usage
Network availability
Filesystem occupation
Abiquo server
This server would host Abiquo API, UI, websockify and M services, it would also have the queue system RabbitMQ, Redis and MariaDB database.
Service | Parameters |
|---|---|
Abiquo API | |
abiquo-tomcat service running | |
apache tomcat / JVM performance parameters | |
port 8009/HTTP listening | |
port 8010/AJP listening | |
Login service available ( | |
Abiquo UI | |
httpd service running | |
Apache web server performance parameters | |
port 80/HTTP listening | |
port 443/HTTPS listening | |
UI service available ( | |
RabbitMQ | |
rabbitmq service running | |
port 5672/AMPQ listening | |
queue status ( | |
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 |
|---|---|
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 |
|---|---|
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 |
|---|---|
JasperServer | |
service mysql status ( Kinton replica ) | |
MariaDB replication status | |
MariaDB performance parameters | |
service jasperserver running | |
PostgresQL service running |
Copyright © 2006-2024, Abiquo Holdings SL. All rights reserved