If you want to know to know how your Unix boxes are spending their time, whilst you are not watching, for example when you are off sleeping, eating or sailing to far off places then Topitall could be for you !
Topitall also can be easily configured to generate alerts by syslog and email based on any of the collected parameters and so act as a simple Enterprise System Monitoring [ESM] tool. For example, Topitall could be used to detect system resource problems such as stopped or runaway processes, over or under used file system capacity, or when a process or application has exceeded a system resource threshold. What more do you really need ?
There are two main functions of Topitall, a topitall client and a topitall server. The client agent gathers system performance statistics and process information, generates alerts, nd stores the data in a database containing one years data. This agent also prepares html files and gif graphs of the data so it can be viewed on the client machine if you have a web server configured on the machine. The alerts generate emails and syslog entries and can be configured to run user defined perl scripts which can attempt totake corrective action to restore the normal running of the machine. The client machine can run in standalone mode or can send the alerts and a selected subset of the data to a central topitall server.
The topitall server collects data from topitall clients and generates a state database of data, and alerts which can currently be browsed with web cgi-scripts. This includes a monitor screen with one button per host coloured to represent the state of the host, according to how recent an alert has been received, and whether data is currently being received from the client. This button gives access to the host screen which has a list of the last ten alerts, again colour coded and a table of the data available for that host. Each of the data items can be browsed as a graph at tme scales of an hour, day, week, month or whole year.
Named has stopped, check slave server for dns !
Automatic Mail from Topitall
Gerthild | homer86 | jcb | jcbhp |
OK | No Connect | Alert | Alert <2T | Alert <5T |
homer86 | |||
2002 Feb 23 21:34 | homer86 5/5 Disk /dev/dsk/c0d0s0 >=65 | user@hostname | Boot disk getting full |
2002 Feb 23 21:34 | homer86 5/5 named N <1 | jbelshaw@localhost | Named has stopped, check slave server for dns ! |
2002 Feb 23 21:39 | homer86 5/5 System LoadAv <5 | user@hostname | System is getting busy |
2002 Feb 23 21:39 | homer86 5/5 Disk /dev/dsk/c0d0s0 >=65 | user@hostname | Boot disk getting full |
2002 Feb 23 21:39 | homer86 5/5 named N <1 | jbelshaw@localhost | Named has stopped, check slave server for dns ! |
2002 Feb 23 21:44 | homer86 5/5 System LoadAv <5 | user@hostname | System is getting busy |
2002 Feb 23 21:44 | homer86 5/5 Disk /dev/dsk/c0d0s0 >=65 | user@hostname | Boot disk getting full |
2002 Feb 23 21:44 | homer86 5/5 named N <1 | jbelshaw@localhost | Named has stopped, check slave server for dns ! |
2002 Feb 23 21:48 | homer86 5/5 System LoadAv <5 | user@hostname | System is getting busy |
2002 Feb 23 21:48 | homer86 5/5 Disk /dev/dsk/c0d0s0 >=65 | user@hostname | Boot disk getting full |
2002 Feb 23 21:48 | homer86 5/5 named N <1 | jbelshaw@localhost | Named has stopped, check slave server for dns ! |
homer86 | Monitor |
Hour | Day | Week | Month | Year | homer86 | Monitor |