Configure per-host filesystem threshold

10 messages in this thread

list Christopher Seip · Thu, 20 Oct 2016 20:03:25 +0000 ·

I'm new to Xymon, have set up my first client monitoring config, and haven't gotten per-host filesystem thresholds to work for that host yet. In /etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert. I've played with a few different syntaxes, wildcards, and other config files. This looks to me like the right way to do it... Feels like I'm overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big Brother years ago.]

list Dennis Riley · Thu, 20 Oct 2016 16:37:18 -0400 ·

Hi Chris,
 You do have your entries above the DEFAULT entry so that you match your
entry first, right?
  Dennis

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher
(HPN SIS team)
Sent: Thursday, October 20, 2016 4:03 PM
To: xymon at xymon.com
Subject: [Xymon] Configure per-host filesystem threshold

▸ quoted from Christopher Seip


I'm new to Xymon, have set up my first client monitoring config, and haven't
gotten per-host filesystem thresholds to work for that host yet. In
/etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert.
I've played with a few different syntaxes, wildcards, and other config
files. This looks to me like the right way to do it... Feels like I'm
overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big
Brother years ago.]

list Christopher Seip · Thu, 20 Oct 2016 21:04:08 +0000 ·

I do indeed; just double-checked.

- Chris

▸ quoted from Dennis Riley

-----Original Message-----
From: Dennis Riley [mailto:user-152961d6c388@xymon.invalid] 
Sent: Thursday, October 20, 2016 1:37 PM
To: Seip, Christopher (HPN SIS team) <user-b14a01e805b4@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris,
 You do have your entries above the DEFAULT entry so that you match your
entry first, right?
  Dennis

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher
(HPN SIS team)
Sent: Thursday, October 20, 2016 4:03 PM
To: xymon at xymon.com
Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't
gotten per-host filesystem thresholds to work for that host yet. In
/etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert.
I've played with a few different syntaxes, wildcards, and other config
files. This looks to me like the right way to do it... Feels like I'm
overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big
Brother years ago.]

list Christopher Seip · Thu, 20 Oct 2016 23:15:01 +0000 ·

An update:

This was an apt-managed package named "xymon" (4.3.25) for Ubuntu.

I just compiled and installed Xymon 4.3.27; it exhibits the same behavior, so this strongly looks like I'm doing something wrong in the xymon configs.

Thanks,

- Chris


Root-# egrep -v '^#' /usr/local/xymon/server/etc/analysis.cfg

HOST=fqdn.of.my.monitored.host
	DISK /disk/data 96 98


DEFAULT
	# Ignore some usually uninteresting tmpfs mounts.
	DISK    /dev IGNORE
	DISK    /dev/shm IGNORE
	DISK    /lib/init/rw IGNORE
	DISK    /run IGNORE
	# These are the built-in defaults. You should only modify these
	# lines, not add new ones (no PROC, DISK, LOG ... lines).
	UP      1h
	LOAD    5.0 10.0
	INODE	* 70 90
	MEMPHYS 100 101
	MEMSWAP 50 80
	MEMACT  90 97

Root-#

▸ quoted from Christopher Seip

-----Original Message-----
From: Seip, Christopher (HPN SIS team) 
Sent: Thursday, October 20, 2016 2:04 PM
To: 'Dennis Riley' <user-152961d6c388@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

I do indeed; just double-checked.

- Chris

-----Original Message-----
From: Dennis Riley [mailto:user-152961d6c388@xymon.invalid] 
Sent: Thursday, October 20, 2016 1:37 PM
To: Seip, Christopher (HPN SIS team) <user-b14a01e805b4@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris,
 You do have your entries above the DEFAULT entry so that you match your
entry first, right?
  Dennis

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher
(HPN SIS team)
Sent: Thursday, October 20, 2016 4:03 PM
To: xymon at xymon.com
Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't
gotten per-host filesystem thresholds to work for that host yet. In
/etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert.
I've played with a few different syntaxes, wildcards, and other config
files. This looks to me like the right way to do it... Feels like I'm
overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big
Brother years ago.]

list Andy Smith · Fri, 21 Oct 2016 06:59:21 +0100 ·

▸ quoted from Christopher Seip

Seip, Christopher (HPN SIS team) wrote:

An update:

This was an apt-managed package named "xymon" (4.3.25) for Ubuntu.

I just compiled and installed Xymon 4.3.27; it exhibits the same behavior, so this strongly looks like I'm doing something wrong in the xymon configs.

Thanks,

- Chris


Root-# egrep -v '^#' /usr/local/xymon/server/etc/analysis.cfg

HOST=fqdn.of.my.monitored.host
	DISK /disk/data 96 98


DEFAULT
	# Ignore some usually uninteresting tmpfs mounts.
	DISK    /dev IGNORE
	DISK    /dev/shm IGNORE
	DISK    /lib/init/rw IGNORE
	DISK    /run IGNORE
	# These are the built-in defaults. You should only modify these
	# lines, not add new ones (no PROC, DISK, LOG ... lines).
	UP      1h
	LOAD    5.0 10.0
	INODE	* 70 90
	MEMPHYS 100 101
	MEMSWAP 50 80
	MEMACT  90 97

Root-#


-----Original Message-----
From: Seip, Christopher (HPN SIS team) 
Sent: Thursday, October 20, 2016 2:04 PM
To: 'Dennis Riley' <user-152961d6c388@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

I do indeed; just double-checked.

- Chris

-----Original Message-----
From: Dennis Riley [mailto:user-152961d6c388@xymon.invalid] 
Sent: Thursday, October 20, 2016 1:37 PM
To: Seip, Christopher (HPN SIS team) <user-b14a01e805b4@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris,
 You do have your entries above the DEFAULT entry so that you match your
entry first, right?
  Dennis

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher
(HPN SIS team)
Sent: Thursday, October 20, 2016 4:03 PM
To: xymon at xymon.com
Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't
gotten per-host filesystem thresholds to work for that host yet. In
/etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert.
I've played with a few different syntaxes, wildcards, and other config
files. This looks to me like the right way to do it... Feels like I'm
overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big
Brother years ago.]

What is in hosts.cfg?  Is it 'fqdn.of.my.monitored.host' or is it just 
'host'?  Try

HOST=%host
   DISK /disk/data 96 98

-- 
Andy

list Mike Burger · Fri, 21 Oct 2016 09:00:24 -0400 ·

▸ quoted from Andy Smith

On 2016-10-21 1:59 am, Andy Smith wrote:

Seip, Christopher (HPN SIS team) wrote:

An update:

This was an apt-managed package named "xymon" (4.3.25) for Ubuntu.

I just compiled and installed Xymon 4.3.27; it exhibits the same behavior, so this strongly looks like I'm doing something wrong in the xymon configs.

Thanks,

- Chris


Root-# egrep -v '^#' /usr/local/xymon/server/etc/analysis.cfg

HOST=fqdn.of.my.monitored.host
	DISK /disk/data 96 98


DEFAULT
	# Ignore some usually uninteresting tmpfs mounts.
	DISK    /dev IGNORE
	DISK    /dev/shm IGNORE
	DISK    /lib/init/rw IGNORE
	DISK    /run IGNORE
	# These are the built-in defaults. You should only modify these
	# lines, not add new ones (no PROC, DISK, LOG ... lines).
	UP      1h
	LOAD    5.0 10.0
	INODE	* 70 90
	MEMPHYS 100 101
	MEMSWAP 50 80
	MEMACT  90 97

Root-#


-----Original Message-----
From: Seip, Christopher (HPN SIS team) Sent: Thursday, October 20, 2016 2:04 PM
To: 'Dennis Riley' <user-152961d6c388@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

I do indeed; just double-checked.

- Chris

-----Original Message-----
From: Dennis Riley [mailto:user-152961d6c388@xymon.invalid] Sent: Thursday, October 20, 2016 1:37 PM
To: Seip, Christopher (HPN SIS team) <user-b14a01e805b4@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris,
 You do have your entries above the DEFAULT entry so that you match your
entry first, right?
  Dennis

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher
(HPN SIS team)
Sent: Thursday, October 20, 2016 4:03 PM
To: xymon at xymon.com
Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't
gotten per-host filesystem thresholds to work for that host yet. In
/etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert.
I've played with a few different syntaxes, wildcards, and other config
files. This looks to me like the right way to do it... Feels like I'm
overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big
Brother years ago.]

What is in hosts.cfg?  Is it 'fqdn.of.my.monitored.host' or is it just
'host'?  Try

HOST=%host
  DISK /disk/data 96 98

In addition to the question from Andy, did you remember to add a host specific wildcard DISK monitor?

I ran into a similar situation, back when I first started out and was told that once you've added any host specific DISK monitors, they override all DEFAULT disk monitor settings. As a result, you have to follow them up with a host specific wildcard entry, a la:

    DISK   /disk/data 96 98
    DISK   * 90 95

-- 
Mike Burger
http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

list Japheth Cleaver · Fri, 21 Oct 2016 16:18:30 -0700 ·

▸ quoted from Mike Burger


On Fri, October 21, 2016 6:00 am, Mike Burger wrote:

On 2016-10-21 1:59 am, Andy Smith wrote:

Seip, Christopher (HPN SIS team) wrote:

An update:

This was an apt-managed package named "xymon" (4.3.25) for Ubuntu.

I just compiled and installed Xymon 4.3.27; it exhibits the same
behavior, so this strongly looks like I'm doing something wrong in the
xymon configs.

Thanks,

- Chris


Root-# egrep -v '^#' /usr/local/xymon/server/etc/analysis.cfg

HOST=fqdn.of.my.monitored.host
	DISK /disk/data 96 98


DEFAULT
	# Ignore some usually uninteresting tmpfs mounts.
	DISK    /dev IGNORE
	DISK    /dev/shm IGNORE
	DISK    /lib/init/rw IGNORE
	DISK    /run IGNORE
	# These are the built-in defaults. You should only modify these
	# lines, not add new ones (no PROC, DISK, LOG ... lines).
	UP      1h
	LOAD    5.0 10.0
	INODE	* 70 90
	MEMPHYS 100 101
	MEMSWAP 50 80
	MEMACT  90 97

Root-#


-----Original Message-----
From: Seip, Christopher (HPN SIS team) Sent: Thursday, October 20,
2016 2:04 PM
To: 'Dennis Riley' <user-152961d6c388@xymon.invalid>; xymon at xymon.com
Subject: RE: [Xymon] Configure per-host filesystem threshold

I do indeed; just double-checked.

- Chris

-----Original Message-----
From: Dennis Riley [mailto:user-152961d6c388@xymon.invalid] Sent: Thursday, October
20, 2016 1:37 PM
To: Seip, Christopher (HPN SIS team) <user-b14a01e805b4@xymon.invalid>;
Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris,
 You do have your entries above the DEFAULT entry so that you match
your
entry first, right?
  Dennis

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip,
Christopher
(HPN SIS team)
Sent: Thursday, October 20, 2016 4:03 PM
To: xymon at xymon.com
Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and
haven't
gotten per-host filesystem thresholds to work for that host yet. In
/etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn
        DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red
alert.
I've played with a few different syntaxes, wildcards, and other config
files. This looks to me like the right way to do it... Feels like I'm
overlooking something really basic here. Thanks,

- Chris
[Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big
Brother years ago.]

What is in hosts.cfg?  Is it 'fqdn.of.my.monitored.host' or is it just
'host'?  Try

HOST=%host
  DISK /disk/data 96 98

In addition to the question from Andy, did you remember to add a host
specific wildcard DISK monitor?

I ran into a similar situation, back when I first started out and was
told that once you've added any host specific DISK monitors, they
override all DEFAULT disk monitor settings. As a result, you have to
follow them up with a host specific wildcard entry, a la:

    DISK   /disk/data 96 98
    DISK   * 90 95

Also: Can you confirm that your client is running in the default
server/centrally-configured mode -- that is, without the "--local" option.
That can sometimes be a trip-up for people coming directly from BB. In
that mode, the localclient.cfg file on the client is used for evaluation
and processing via analysis.cfg never happens.


It's also helpful when debugging thresholds to validate through
xymond_client that it's doing what you're thinking it's doing. You can
have it dump its (processed) config by running:

xymoncmd xymond_client --dump-config | grep DISK


HTH,
-jc

list Christopher Seip · Thu, 27 Oct 2016 00:18:07 +0000 ·

▸ quoted from Andy Smith

 Andy Smith [mailto:user-982f5f6d4d28@xymon.invalid] wrote:

 What is in hosts.cfg?  Is it 'fqdn.of.my.monitored.host' or is it just 
 'host'?  Try

 HOST=%host
    DISK /disk/data 96 98

# cd /etc/xymon
# egrep '/disk/data|swnfs07' analysis.cfg hosts.cfg
analysis.cfg:HOST=swnfs07.rose.rdlabs.hpecorp.net
analysis.cfg:	DISK /disk/data 96 98
hosts.cfg:    16.93.247.205	swnfs07.rose.rdlabs.hpecorp.net	# rpc=mount,nlockmgr,nfs,ypbind ssh

I tried the change you mentioned (Perl regex! Cool feature). Anyway:

# egrep '/disk/data|swnfs07' analysis.cfg hosts.cfg
analysis.cfg:# HOST=swnfs07.rose.rdlabs.hpecorp.net
analysis.cfg:HOST=%swnfs07
analysis.cfg:	DISK /disk/data 96 98
hosts.cfg:    16.93.247.205	swnfs07.rose.rdlabs.hpecorp.net	# rpc=mount,nlockmgr,nfs,ypbind ssh

Still haven't seen a change in the behavior. Its /disk/data partition is at 95% full and coming up red in Xymon.

Thanks,

--Chris--

list Christopher Seip · Thu, 27 Oct 2016 00:25:04 +0000 ·

▸ quoted from Mike Burger

 Mike Burger [mailto:user-cc5c6e80f4c5@xymon.invalid] wrote:

 In addition to the question from Andy, did you remember to add a host  specific wildcard DISK monitor?

 I ran into a similar situation, back when I first started out and was  told that once you've added any host specific DISK monitors, they  override all DEFAULT disk monitor settings. As a result, you have to  follow them up with a host specific wildcard entry, a la:

     DISK   /disk/data 96 98
     DISK   * 90 95

Thank you very much! That's new to me.

Duly added.

--Chris--

list Christopher Seip · Thu, 27 Oct 2016 00:58:49 +0000 ·

▸ quoted from Japheth Cleaver

 J.C. Cleaver [mailto:user-87556346d4af@xymon.invalid] wrote:

 Also: Can you confirm that your client is running in the default
 server/centrally-configured mode -- that is, without the "--local" option.
 That can sometimes be a trip-up for people coming directly from BB. In
 that mode, the localclient.cfg file on the client is used for evaluation
 and processing via analysis.cfg never happens.

I found that in /usr/local/xymon/etc/clientlaunch.cfg and took out the "--local"
option to xymonclient.sh. That fixed it. Thank you!

▸ quoted from Japheth Cleaver

 It's also helpful when debugging thresholds to validate through
 xymond_client that it's doing what you're thinking it's doing. You can
 have it dump its (processed) config by running:

 xymoncmd xymond_client --dump-config | grep DISK

Much appreciated!

--Chris--

Configure per-host filesystem threshold 🔗 link

Configure per-host filesystem threshold