monit-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: monit summary ... patch


From: Martin Pala
Subject: Re: monit summary ... patch
Date: Sun, 03 Apr 2005 23:18:46 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050324 Debian/1.7.6-1

OK, i have modified the patch to display text version of summary as one-liner. It will be probably realy better because if the service is not monitored, the state is 'not monitored' anyway ... and state data timestamp is not necessary in summary - it can be displayed using full 'status' if more details are needed.

--8<--
unicorn:~/cvs/monit-summary# ./monit -c /etc/monitrc summary
The monit daemon 4.6-cvs uptime: 0m

System 'unicorn'                    [0.16] [0.14] [0.09]
Process 'slapd'                     running
Process 'mysql'                     running
File 'slapd_rc'                     accessible
File 'slapd_bin'                    accessible
Device 'rootfs'                     accessible
Device 'vfatfs'                     Data access error
File 'testfile'                     not monitored
Directory 'bin'                     accessible
Remote Host 'iol'                   online with all services
--8<--

Thanks for feedback :)

Here is new patch version.

Martin


Claus Klein wrote:
Yes, I like single line summaries too:

address@hidden:/home/claus/src/buildroot/build_powerpc/monit-4.5# ./monit -c 
/etc/monit/monitrc summary
The monit daemon 4.5 uptime: 2m

System 'www.clausklein.homelinux.net'
  load average                      [0.00] [0.00] [0.03]
  cpu                               2.7%us 0.7%sy 0.4%wa
  memory usage                      199452 kB [38.6%]
  data collected                    Sun Apr  3 12:22:40 2005

Process  'apache      '   running         monitored       at Sun Apr  3 
12:22:46 2005
File     'apache_bin  '   accessible      monitored       at Sun Apr  3 
12:22:46 2005
Device   'homefs      '   Resource limit matched          monitored       at 
Sun Apr  3 12:22:46 2005
Device   'rootfs      '   accessible      monitored       at Sun Apr  3 
12:22:46 2005
Process  'snmpd       '   Execution failed        monitored       at Sun Apr  3 
12:22:46 2005
Process  'pure-ftpd   '   running         monitored       at Sun Apr  3 
12:22:45 2005
Process  'dictd       '   running         monitored       at Sun Apr  3 
12:22:40 2005
Process  'wwwoffled   '   running         monitored       at Sun Apr  3 
12:22:40 2005
File     'wwwoffled_rc'   accessible      monitored       at Sun Apr  3 
12:22:40 2005
Process  'privoxy     '   running         monitored       at Sun Apr  3 
12:22:40 2005
File     'privoxy_bin '   accessible      monitored       at Sun Apr  3 
12:22:40 2005
File     'privoxy_rc  '   accessible      monitored       at Sun Apr  3 
12:22:40 2005
Process  'cron        '   running         monitored       at Sun Apr  3 
12:22:40 2005
File     'cron_rc     '   accessible      monitored       at Sun Apr  3 
12:22:40 2005
Process  'syslogd     '   running         monitored       at Sun Apr  3 
12:22:40 2005
File     'syslogd_file'   accessible      monitored       at Sun Apr  3 
12:22:40 2005
Process  'ntpd        '   Execution failed        monitored       at Sun Apr  3 
12:22:40 2005
File     'TestLockFile'   initializing    initializing    at Sun Apr  3 
12:20:35 2005
address@hidden:/home/claus/src/buildroot/build_powerpc/monit-4.5#

Claus
On Saturday 02 April 2005 10:33, Michael Shigorin wrote:

On Sat, Apr 02, 2005 at 01:34:42AM +0200, Martin Pala wrote:

The implementation adds new atributte called 'level' to _status
cervlet - the optional values are 'full' and 'summary' (fulll
is default). XML formated status summary is available as well

Hm, maybe the "brief" level (as `monit status` of 4.2 days) would
be nice too?  It was easily greppable and grokkable :)




_______________________________________________
monit-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monit-dev

Attachment: summary-20050403.patch
Description: application/unknown


reply via email to

[Prev in Thread] Current Thread [Next in Thread]