linux:host_and_website_monitoring - Solin Expertise Center

Trace: • multimedia • activerecord • navigation
This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Host And Website Monitoring ======







===== Requirements =====

The following were my requirements when I was looking for host and website monitoring solutions.

  * Monitoring individual websites
  * Observing a host system (i.e. web server)
  * Warning by email
  * Nice to have: sms alerts (or a bridge to an sms-gateway)  



With regard to #2, observing a host system:

  * I want to be warned if system resources are nearing critical limits. E.g. the hard drive is at >90% capacity.
  * It would also be nice to have a tool which notices trends, e.g. the CPU load is has been increasing steadily over last month.












===== Solutions =====

Please note that the following tools do not fullfill the requirements mentioned above (far from it, in most cases), but they are important monitoring tools.

  * Webmin: go to ''Others > System and Server Status'' to add various monitors (remote systems, local services). Use the email option and an sms gateway (email2sms) to send out warnings.
  * [[collectd]]: an excellent, light weight data gathering tool with CPU and load monitoring, as well as plugins for servers such as Apache and MySQL.
  * [[drraw]]: a perl script which uses rrd files to generate graphs (collectd can maintain rrd files for you, e.g. to create a history of http requests)
  * WebminStats: installed under System as ''Historic System Statistics''.
  * [[Munin]]: easy to install and configure. Does not force you to use snmp (uses a monitor and node, but both can be on same machine). Has a number of Apache plugins (including two for Passenger).

Unexplored:

  * [[http://nagiosgraph.sourceforge.net/|nagiosgraph]]
  * [[http://www.zabbix.com/|zabbix]] (apparently more professional than Munin, and easier to set up and use than Nagios)









==== What NOT to Use ====

  * Cacti: bloatware. Requires you not only to install and configure snmp stuff, but all lot of fluff too (graph trees and whatnot).
  * Visage: Sinatra / Ruby based graph generator (using rrd files). Not advanced enough (yet): no obvious way to include min, max and average from an rrd file.
  * Nagios: overkill for my needs. Seems to be pretty complicated to configure (maybe even more so than Cacti).



==== Comparisons ====

  * [[http://www.felix-schwarz.name/Short_Comparison_of_some_Network_Monitoring_Tools_%28en%29|Comparison of Nagios, Zabbix, Argus]]
  * [[http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/|10 Free Server & Network Monitoring Tools that Kick Ass]]
  * [[http://en.wikipedia.org/wiki/Comparison_of_network_monitoring_systems|Comparison of network monitoring systems]] (wikipedia)


===== Simple Monitoring Tools =====


  * ''top''
  * ''htop''

How to interpret the load average, as reported by top/htop: 1, 5, 15 min. averages. See this article: [[http://blog.scoutapp.com/articles/2009/07/31/understanding-load-averages|Understanding Linux CPU Load - when should you be worried?]]. The gist of it is that for 1 logical cpu (can be a core):

  * 0.70: need to look into it
  * 1.00: fix this now
  * 5.00: serious trouble (e.g. box is hanging)

Multiply these values with the number of logical cpus as reported by ''cat /proc/cpuinfo'' or ''lscpu''. To get the relevant count, run it through grep and word count: ''grep 'model name' /proc/cpuinfo | wc -l''.


===== Find The Cause of High Load Average =====

The article [[http://www.linuxjournal.com/magazine/hack-and-linux-troubleshooting-part-i-high-load?page=0,0|Linux Troubleshooting, Part I: High Load]] provides an excellent intro. The gist of it is that there are three main categories of high load:

  * CPU-bound load
  * Out of memory issues
  * I/O bound load

You are advised to look at the causes in that order, because sometimes //Out of memory issues// may look like I/O troubles (if the systems starts swapping heavily due to memory issues, it increases the I/O load as well).

TIP: use htop to easily see if the high load falls into either the CPU-bound or the memory-issues category. Unfortunately, it's not so easy to spot I/O bound load issues, especially not on a VPS.

You cannot use the iostat command on a VPS to discover I/O bound load issues.

Another useful article: [[http://www.midwesternmac.com/blogs/jeff-geerling/diagnosing-disk-io-issues|Diagnosing Disk I/O issues: swapping, high IO wait, congestion]].


===== Performance Testing with JMeter =====

[[http://jmeter.apache.org/|JMeter]] is a Java program to load test your website. Basically, it measures two things:

  * **throughput** per minute (requests per minute handled)
  * **average** response time (in milliseconds)

Using a single instance of JMeter, you should be able to [[http://stackoverflow.com/questions/765101/what-is-the-highest-number-of-threads-that-is-reasonable-to-simultaneously-run-in|simulate a load of at least 100 concurrent users]] (where JMeter is running on a different machine than the webserver).

As a rule of thumb: "it is best to run it on your hardware so that the CPU of the PC does not peak at 100% - a stable 80%-90% is best otherwise the results are affected".

==== Terminology ====
  * Threads: users
  * Samples: HTTP requests
  * Listeners: graphs & tables (reports)

==== Test Plans ====

For simple sites, it's easy to create your own test plan inside JMeter. For more complex sites, such as the LMS Moodle, you can use test script generators. In Moodle there's one available under ''Administration > Site Administration > Development > Make JMeter test plan'' (included from version 2.5 onwards).

=== Problem with CSV users data ===

One thing to look out for when using Moodle's JMeter test plan generator: it outputs a csv file for the test users. In JMeter, this csv file is referenced twice, once under 'Warm-up site' and again under 'Moodle Test', as ''CSV users data''. I had to insert the complete path to this csv file before JMeter could properly access it.

=== Ignore Errors / Warnings about recorder.bsf ===
The Moodle test plan will also contain a reference to ''recorder.bsf''. My version of JMeter was not able to locate that file. Just ignore the errors & warnings. JMeter will run just fine without recorder.bsf.
You are here: start » linux » host_and_website_monitoring
Views

Navigation

Personal Tools

Search

Toolbox
