Difference between revisions of "Monitoring Servers"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
Line 24: Line 24:
:* Dropped packets  
:* Dropped packets  
:* Socket wear and tear
:* Socket wear and tear
<noinclude>
[[Category:Installation]]
</noinclude>

Latest revision as of 21:38, 2 October 2013

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

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