Xymon Mailing List Archive search

analysis.cfg config issues

3 messages in this thread

list Rolf Brusletto · Tue, 12 Jun 2012 12:56:12 -0600 ·
I *thought* I'd used this type of setup in the past, but it doesn't seem to be working in the current setup as follows:

HOST=somehost
         LOAD 4.0 6.0 TIME=W:0730:1630
         MEMACT 50 60 TIME=W:0730:1630
         LOAD 10.0 12.0
         MEMACT 80 90

DEFAULT
         # These are the built-in defaults.
         UP      20m
         LOAD    1.0 2.0
         MEMACT  90 97


Currently, I'm getting warning(yellow) alerts for what seems to be anything over a load of 5, which in the documentation seems like the default, when nothing is specified. Clearly the load is defined in the default(which IS at the end of the analysis.cfg). We expect the load to be lower than 4 during week work hours, and higher in the evening/night due to a large amount of load processing. Is there something simple I'm missing here, or is it simply the way the times are configured?


-- 
Thanks!

Rolf Brusletto
Senior Network And Systems Admin
Global Liquidity Partners, LLC
user-b4140c0db1a1@xymon.invalid
XXX-XXX-XXXX mobile
list Jeremy Laidman · Fri, 15 Jun 2012 15:46:36 +1000 ·
To me, the config looks like it should work.

Perhaps you could test what's going on with "xymond_client --test --debug".
 See "man xymond_client" for details.

Also note that the default levels for LOAD are 5 and 10, according to the
man page for analysis.cfg.  So the behaviour is also consistent with the
host matching nothing including the DEFAULT.  Is it possible that the
analysis.cfg file is not readable by the xymon user?

J


On Wed, Jun 13, 2012 at 4:56 AM, Rolf Brusletto
quoted from Rolf Brusletto
<user-1fe6f74a62eb@xymon.invalid>wrote:
I *thought* I'd used this type of setup in the past, but it doesn't seem
to be working in the current setup as follows:

HOST=somehost
       LOAD 4.0 6.0 TIME=W:0730:1630
       MEMACT 50 60 TIME=W:0730:1630
       LOAD 10.0 12.0
       MEMACT 80 90

DEFAULT
       # These are the built-in defaults.
       UP      20m
       LOAD    1.0 2.0
       MEMACT  90 97


Currently, I'm getting warning(yellow) alerts for what seems to be
anything over a load of 5, which in the documentation seems like the
default, when nothing is specified. Clearly the load is defined in the
default(which IS at the end of the analysis.cfg). We expect the load to be
lower than 4 during week work hours, and higher in the evening/night due to
a large amount of load processing. Is there something simple I'm missing
here, or is it simply the way the times are configured?


--
Thanks!

Rolf Brusletto
Senior Network And Systems Admin
Global Liquidity Partners, LLC
user-b4140c0db1a1@xymon.invalid
XXX-XXX-XXXX mobile

______________________________**

Xymon at xymon.com<
list Phil Crooker · Fri, 22 Jun 2012 08:34:08 +1000 ·
Is this a Windows client? If so, it may be using local settings. I had a
similar problem and had to delete the defaults in the bbwin.cfg file.

cheers, Phil
quoted from Jeremy Laidman


On Wed, Jun 13, 2012 at 4:56 AM, Rolf Brusletto
wrote:
I *thought* I'd used this type of setup in the past, but it doesn't
seem
to be working in the current setup as follows:

HOST=somehost
       LOAD 4.0 6.0 TIME=W:0730:1630
       MEMACT 50 60 TIME=W:0730:1630
       LOAD 10.0 12.0
       MEMACT 80 90

DEFAULT
       # These are the built-in defaults.
       UP      20m
       LOAD    1.0 2.0
       MEMACT  90 97


Currently, I'm getting warning(yellow) alerts for what seems to be
anything over a load of 5, which in the documentation seems like the
default, when nothing is specified. Clearly the load is defined in the
default(which IS at the end of the analysis.cfg). We expect the load
to be
lower than 4 during week work hours, and higher in the evening/night
due to
a large amount of load processing. Is there something simple I'm
missing
here, or is it simply the way the times are configured?


--
Thanks!

Rolf Brusletto
Senior Network And Systems Admin
Global Liquidity Partners, LLC
user-b4140c0db1a1@xymon.invalid
XXX-XXX-XXXX mobile

______________________________**