comment on

I'm trying to put together a list of tests to perform on the servers that run my website to ensure that I spot any problems early. Some of those below will be fed into Nagios, and others will just send alarms if there is a problem.

Can you think of any others that I should be checking? Or are some of the below useless?

Update: I forgot to add - I was thinking about building the list of tests using the Test::More etc modules, which I've previously only used for testing modules at install. Anything in particular you'd recommend for structuring these tests?

General
- disk
  - % free disk space
  - free disk space
  - smartd alerts
- memory
  - % used
  - % free
  - % buffered / cached
  - swap
  - biggest processes & their size
- load
  - processes using most load
- network
  - ping
  - have outgoing access
  - traffic in
  - traffic out
- ssh
  - access
  - number of login attempts
Apache / mod_perl
- processes
  - number of processes / max
  - total memory of all processes
  - size of biggest process
  - rate of spawning new processes
- requests
  - requests / second
  - cached responses / second
  - dynamic responses / second
  - kB transferred / second
  - 404 errors / hour
  - 500 errors / hour
- connectivity
  - website responds to test page
  - response time
MySQL
- daily check tables
- can connect
- requests / second
- open_tables / table_cache
- tmp_disk_tables / tmp_tables
- max_used_connections
- threads_connected
- threads_running
- slow_launch_threads
- slow_queries
- query cache hits / query cache requests
- key_reads / key_read_requests
- key_writes / key_write_requests
- table_locks_waited
- aborted_connects
- slave status
- slave seconds behind master
DNS
- dns accessible
- check host entries
- check mx entries
- check SPF entries
Mail
- receiving test mail
- outgoing mail being delivered
- mails in queue
- mails sent per hour
memcached
- hosts accessible
- get hits / cmd_get
- malloc_total_free / malloc_total_alloc

thanks

Clint

In reply to [OT] Monitoring a website by clinton

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.