Xymon Mailing List Archive search

Help with nopropred (I think)

3 messages in this thread

list Terry Barnes · Thu, 05 May 2005 23:15:19 -0400 ·
I have Hobbit's bb.html page displaying just a list of other pages
organized by OS platform. On a few of these pages we have production and
non-production servers listed. In our environment - the non-production
servers are deemed basically as important as the production servers
since many highly visible and much highly politcally oriented
development work and production support work is done. 

Now, i have been requested to separate the non-production servers from
the production servers, placing them on a subpage of the productions
servers page. No problem there - just a page tag and it is done. The
other part of this, and what I am having trouble understanding how to
do, is to prevent propagation of non-green events to the parent page
where the production servers ar listed. We still generate alerts, pages,
etc. for problems on the non-production pages, but I can't seem to find
a way to prevent the non-green alerts for all tests on the non-prod
subpages from propagting upward. Even if every single non-prod server
went up in smoke, the production page should remain green (assuming
there are no production problems).

It seems I can alter the propagation status either globally or for a
single test at a time, but there are hundreds of tests being done on the
non-production systems and disabling all of them individually would
really clutter up the bb-hosts file. Mosts of the tests are being done
with bb client and are not even listed in Hobbit's bb-hosts file.

Thanks for any help!


Terry Barnes
Siemens Com @ HFHS
XXX-XXX-XXXX (Office)
XXX-XXX-XXXX (Cellular)
XXX-XXX-XXXX (Fax)
user-34ea5ff61ded@xymon.invalid (Text Pager)
user-0e29285d9a67@xymon.invalid

==============================================================================
HFHS CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed.  If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by replying in an email to the sender, delete the email from your computer system and shred any paper copies of the email you printed.

Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. These risks are described in our Privacy Policy at http://henryford.com.  Review that policy carefully before continuing to communicate with us by e-mail. For greater Internet security, our policy describes the Henry Ford MyHealth electronic communication process - you may register at http://henryford.com.  If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.


==============================================================================
list Henrik Størner · Fri, 6 May 2005 08:23:13 +0200 ·
quoted from Terry Barnes
On Thu, May 05, 2005 at 11:15:19PM -0400, Terry Barnes wrote:
It seems I can alter the propagation status either globally or for a
single test at a time, but there are hundreds of tests being done on the
non-production systems and disabling all of them individually would
really clutter up the bb-hosts file. Mosts of the tests are being done
with bb client and are not even listed in Hobbit's bb-hosts file.
The simplest way of disabling red AND yellow statuses from going upwards
is to put a "NOPROPRED:*" on the pertinent host entries. bbgen assumes that 
if you don't care to see a red status, you probably dont want the yellow 
one either. And the "*" is special, matching all tests.

So that makes things a bit simpler.

On top of that, you can try using the ".default." host - this is
something that was added in 4.0.2 to make it easier to apply one or more
tags on lots of hosts. This is like a normal host entry in the bb-hosts
file, but it just sets up a set of tags that are automatically added for
all hosts that appear after the ".default." entry. So in your case it
would be used like this:

  page prod1 Production servers 1
  0.0.0.0    .default.        #
  10.0.0.1   prod1.foo.com    #  
  10.0.0.1   prod2.foo.com    #

  subpage nonprod1 Non-production servers 1
  0.0.0.0    .default.        # NOPROPRED:*
  10.1.0.1   test1.foo.com    #
  10.1.0.2   test2.foo.com    #
  10.1.0.3   test2.foo.com    #

  page prod2 Production servers 2
  0.0.0.0    .default.        #
  10.2.0.1   prodA.foo.com    #

See ? When you start on a set of production servers, you put in an 
empty ".default." definition to clear the default set of tags, and 
when you start on a non-production set of servers, you put in a
".default." host with the "NOPROPRED:*" tag.

The ".default." host must be called exactly that - with the two dots.
It will not show up on the generated web pages, and you can only use it
to define these Hobbit-internal tags - not network tests.


Regards,
Henrik
list Terry Barnes · Fri, 06 May 2005 08:55:51 -0400 ·
OK - the default host setting will work nicely. Thank you!
quoted from Terry Barnes

Terry Barnes
Siemens Com @ HFHS
XXX-XXX-XXXX (Office)
XXX-XXX-XXXX (Cellular)
XXX-XXX-XXXX (Fax)
user-34ea5ff61ded@xymon.invalid (Text Pager)
user-0e29285d9a67@xymon.invalid
user-ce4a2c883f75@xymon.invalid 5/6/05 2:23:13 AM >>>
quoted from Terry Barnes
On Thu, May 05, 2005 at 11:15:19PM -0400, Terry Barnes wrote:
It seems I can alter the propagation status either globally or for a
single test at a time, but there are hundreds of tests being done on
the
non-production systems and disabling all of them individually would
really clutter up the bb-hosts file. Mosts of the tests are being
done
with bb client and are not even listed in Hobbit's bb-hosts file.
The simplest way of disabling red AND yellow statuses from going
upwards
is to put a "NOPROPRED:*" on the pertinent host entries. bbgen assumes
that 
if you don't care to see a red status, you probably dont want the
yellow 
one either. And the "*" is special, matching all tests.

So that makes things a bit simpler.

On top of that, you can try using the ".default." host - this is
something that was added in 4.0.2 to make it easier to apply one or
more
tags on lots of hosts. This is like a normal host entry in the
bb-hosts
file, but it just sets up a set of tags that are automatically added
for
all hosts that appear after the ".default." entry. So in your case it
would be used like this:

  page prod1 Production servers 1
  0.0.0.0    .default.        #
  10.0.0.1   prod1.foo.com    #  
  10.0.0.1   prod2.foo.com    #

  subpage nonprod1 Non-production servers 1
  0.0.0.0    .default.        # NOPROPRED:*
  10.1.0.1   test1.foo.com    #
  10.1.0.2   test2.foo.com    #
  10.1.0.3   test2.foo.com    #

  page prod2 Production servers 2
  0.0.0.0    .default.        #
  10.2.0.1   prodA.foo.com    #

See ? When you start on a set of production servers, you put in an 
empty ".default." definition to clear the default set of tags, and 
when you start on a non-production set of servers, you put in a
".default." host with the "NOPROPRED:*" tag.

The ".default." host must be called exactly that - with the two dots.
It will not show up on the generated web pages, and you can only use
it
to define these Hobbit-internal tags - not network tests.


Regards,
Henrik


==============================================================================
HFHS CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed.  If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by replying in an email to the sender, delete the email from your computer system and shred any paper copies of the email you printed.

Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. These risks are described in our Privacy Policy at http://henryford.com.  Review that policy carefully before continuing to communicate with us by e-mail. For greater Internet security, our policy describes the Henry Ford MyHealth electronic communication process - you may register at http://henryford.com.  If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.


==============================================================================