Monitoring Servers

Any server in the system can become a bottleneck, at some point, so it's a good idea to continually monitor the health of the critical processes that run on them. This section lists the components to monitor on each server.

Monitoring Application Servers

• tomcat availability and CPU utilization. Check threads, connection pool size, sticky sessions, KeepAliveRequests, etc.
• GC – Allocation and de-allocation of memory on the JVM. (Monitoring and Tuning Garbage Collection)
• OS (Linux) CPU utilization, IO activity, swap ratio, context switches, etc. (Monitoring OS Statistics)

Monitoring Web Servers

• apache-httpd availability
• OS (Linux) CPU utilization, IO activity, swap ratio, context switches, etc. (Monitoring OS Statistics)

Monitoring Database Servers

• mysql availability. Check caches, buffers, connections, timeouts. (Monitoring and Tuning MySQL)
• OS (Linux) CPU utilization, IO activity, swap ratio, context switches, etc. (Monitoring OS Statistics)

Note: If replication is employed, scripts can be written to check the health of the replication and report replication lag times.

Monitoring memcached Servers

• memcached availability
• OS (Linux) CPU utilization, IO activity, swap ratio, context switches, etc. (Monitoring OS Statistics)

Monitoring the Network

• Dropped packets
• Socket wear and tear