[hobbit] CPU % load on Windows XP

Everett, Vernon Vernon.Everett at woodside.com.au
Tue Jul 1 03:05:32 CEST 2008


 
Hi Bill

Apologies for mailing direct, but there is a lag on our outgoing mail to
mailing lists. I didn't think you wanted to wait 7 hours for a reply.
(I included the list so we can all see the solution)

Have a look at the hobbit man page, hobbit-client.cfg section.

If all your Windows server host names start with win then you can use 
HOST=%^win.*
	LOAD 80 95

But it is most likely they do not.

>From the man page 

PAGE=targetstring Rule matching an alert by the name of the page in BB.
"targetstring" is the path of the page as defined in the bb-hosts file.
EXPAGE=targetstring Rule excluding a host if the pagename matches.
CLASS=classname Rule match by the client class-name. You specify the
class-name for a host when starting the client through the
"--class=NAME" option to the runclient.sh script. If no class is
specified, the host by default goes into a class named by the operating
system.
EXCLASS=classname Exclude all hosts belonging to "classname" from this
rule. 

These are probably the ones that will interest you most.

What we have done, is under our default definitions we have 
#DEFAULT
HOST=* EXHOST=firewall,sec01 EXCLASS=win32 EXPAGE=%win/*
(This includes all hosts, except the firewall & security server, all
win32 servers, and all hosts listed in /win/*

All of our Windows servers are listed under sub-pages of the win page.
These pages and sub-pages, are as defined in bb-hosts.

Example from bb-hosts
---snip---
page win Windows Servers
subpage win_prod_dc Domain Controllers
3.4.5.4   DC05        #
subpage win_prod_fps File/Print
3.4.5.5   FPS01       #
subpage win_prod_mls Exchange
3.4.5.6   MAIL01		#
3.4.5.7   MAIL02	#
subpage win_prod Production
3.4.5.8   PROD01        #
3.4.5.9   PROD02        #
---snip---
Since all of these will be listed on web pages that match the regex
%win/*
They will be excluded from the default definition.

You can now create a section in 

hobbit-client.cfg
# Windows Defaults
PAGE=%win/*
        LOAD 50 80
        DISK 85 90

Hope that helps.

Regards
    Vernon







-----Original Message-----
From: Bill Arlofski [mailto:waa-hobbitml at revpol.com] 
Sent: Tuesday, 1 July 2008 5:33 AM
To: hobbit at hswn.dk
Subject: [hobbit] CPU % load on Windows XP


We have approximately 20 virtual XP workstations on a VMWare ESX 3.02
server where the bbwin clients on the XP workstations are reporting back
to hobbit CPU loads of between 1% and up to 15% or a little more. This
seems appropriate for the tiny amount of work they are performing.

However, when the CPU load for one of these virtual XP workstations
reaches 7% CPU load (as reported on the CPU page), Hobbit sets the color
to Yellow.

When the CPU load gets to just around 10%-11% CPU load Hobbit sets the
color to red.

The hobbit-clients.cfg man page explains the default load as follows:

Defaults: warnlevel=5.0, paniclevel=10.0

Which I understand to be *NIX load levels, not %loads as indicated by
Windows systems.

But in the Reports --> Config Reports page, under the CPU for each host
I see:

UNIX - Yellow: Load average > 1.5, Red: Load average > 3.0 Windows -
Yellow: CPU utilisation > 80%, Red: CPU utilisation > 95%

So based on that information, I am assuming that the defaults for CPU
load on Windows clients is 80% = yellow and 95% = red.


Have I done misunderstood?

Do I need to add an explicit HOST entry in hobbit-clients.cfg for
Windows 
machines like so:

HOST=%^win.*
	LOAD 80 95


Thanks for any help - especially help that points me to a document that
I 
missed in my searching. :)



--
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/

To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk



NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.




More information about the Xymon mailing list