Xymon Mailing List Archive search

Alerting table in the info screen

6 messages in this thread

list Greg Shea · Sat, 21 Jul 2007 17:56:51 +0000 ·
Hi all,

Is there supposed to be an "Exceptions" portion of the alerting table when viewed from the info button?
Kind of like the way BB has it?  This way here, at a glance, not only can I tell what services are being
alerted on, but I would also like to know what's configured NOT to alert on.

For instance (excerpt from hobbit-alerts.cfg)
HOST=myhost SERVICE=disk,memory,msgs,network,procs
        MAIL user-f41fdb8164cf@xymon.invalid FORMAT=TEXT REPEAT=30 RECOVERED
EXSERVICE=cpu,files,netstat,ports,vmstat

Thanks
-Grs-
Gregory R Shea
EMC Corporation
list Henrik Størner · Sun, 22 Jul 2007 00:00:35 +0200 ·
quoted from Greg Shea
On Sat, Jul 21, 2007 at 05:56:51PM +0000, user-f00ed6e065e8@xymon.invalid wrote:
Is there supposed to be an "Exceptions" portion of the alerting table when viewed from the info button?
Kind of like the way BB has it?  This way here, at a glance, not only can I tell what services are being
alerted on, but I would also like to know what's configured NOT to alert on.
It's very simple: The services that have alerts listed on the "info"
page are the ones that will send you alerts. All exceptions and host-
specific configuration is taken into account on the info-page display.
quoted from Greg Shea
For instance (excerpt from hobbit-alerts.cfg)
HOST=myhost SERVICE=disk,memory,msgs,network,procs
        MAIL user-f41fdb8164cf@xymon.invalid FORMAT=TEXT REPEAT=30 RECOVERED
EXSERVICE=cpu,files,netstat,ports,vmstat
You're making it needlessly complex. There's no reason to have a SERVICE
setting and an EXSERVICE setting when there's no overlap between the
two. By adding a SERVICE setting, you have automatically excluded all
of the services that aren't listed.

Oh ... and the netstat and vmstat columns usually do not exist, unless
you're using the old BB client. So they cannot trigger alerts.


Regards,
Henrik
list Greg Shea · Sun, 22 Jul 2007 16:46:05 -0400 ·
Hi Henrik,
 
Thanks for the reply.  A couple of more things if you don't mind, because I trust you gave me
the answer, but maybe I wasn't clear in my question.  I've added a little table below that represents
what I was asking.  I think what you told me was that in Hobbit, if the service does not appear in the
table, then it is implied that it will not alert.  That's Ok, I get that, but I'm being asked by the
pointy hair bosses, why they can't see the exceptions, like they do now with BB and BBGen.  If I'm
missing something in my configuration, great, please point me in the right direction.  If it's not intended
to look similar, would it be difficult to add?
 
Thanks again
-Grs-
Gregory R Shea
EMC Corporation
 
BB with BBGen3.6
| Services | Ex.Services | Weekdays | Time   | Recipients         |
|----------+-------------+----------+--------+--------------------|
| All      |             | All days | 0000-  | trap-10.10.10.10:0 |
|          |             |          | 2359   |                    |
|----------+-------------+----------+--------+--------------------|
| network  |             | All days | 0000-  | user-72358f08cb7a@xymon.invalid:120  |
| temp     |             |          | 2359   | user-1bf33e42478f@xymon.invalid:120  |
|----------+-------------+----------+--------+--------------------|
|                            Exceptions                           |
|----------+-------------+----------+--------+--------------------|
| cpu      |             | All days | 0000-  | trap-10.10.10.10:0 |
|          |             |          | 2359   |                    |
|----------+-------------+----------+--------+--------------------|
| All      |             | All days | 0000-  | user-1906180112d1@xymon.invalid |
|          |             |          | 2359   |                    |
|----------+-------------+----------+--------+--------------------|

Hobbit 4.2.0
| Service | Recipient     | 1st Delay | Stop After | Repeat | Time of Day | Colors         |
|---------+---------------+-----------+------------+--------+-------------+----------------|
| network | user-72358f08cb7a@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|         |---------------+-----------+------------+--------+-------------+----------------|
|         | user-1bf33e42478f@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|---------|---------------+-----------+------------+--------+-------------+----------------|
| temp    | user-72358f08cb7a@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|         |---------------+-----------+------------+--------+-------------+----------------|
|         | user-1bf33e42478f@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
quoted from Henrik Størner
|---------|---------------+-----------+------------+--------+-------------+----------------|


From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Sat 7/21/2007 6:00 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Alerting table in the info screen


On Sat, Jul 21, 2007 at 05:56:51PM +0000, user-f00ed6e065e8@xymon.invalid wrote:
Is there supposed to be an "Exceptions" portion of the alerting table when viewed from the info button?
Kind of like the way BB has it?  This way here, at a glance, not only can I tell what services are being
alerted on, but I would also like to know what's configured NOT to alert on.
It's very simple: The services that have alerts listed on the "info"
page are the ones that will send you alerts. All exceptions and host-
specific configuration is taken into account on the info-page display.
For instance (excerpt from hobbit-alerts.cfg)
HOST=myhost SERVICE=disk,memory,msgs,network,procs
        MAIL user-f41fdb8164cf@xymon.invalid FORMAT=TEXT REPEAT=30 RECOVERED
EXSERVICE=cpu,files,netstat,ports,vmstat
You're making it needlessly complex. There's no reason to have a SERVICE
setting and an EXSERVICE setting when there's no overlap between the
two. By adding a SERVICE setting, you have automatically excluded all
of the services that aren't listed.

Oh ... and the netstat and vmstat columns usually do not exist, unless
you're using the old BB client. So they cannot trigger alerts.


Regards,
Henrik
list S Aiello · Mon, 23 Jul 2007 07:28:45 -0400 ·
quoted from Greg Shea
On Sunday 22 July 2007 16:46, user-762ee872a5a4@xymon.invalid wrote:
Hi Henrik,

Thanks for the reply.  A couple of more things if you don't mind, because I
trust you gave me the answer, but maybe I wasn't clear in my question. I've added a little table below that represents what I was asking.  I think
what you told me was that in Hobbit, if the service does not appear in the
table, then it is implied that it will not alert.  That's Ok, I get that,
but I'm being asked by the pointy hair bosses, why they can't see the
exceptions, like they do now with BB and BBGen.  If I'm missing something
in my configuration, great, please point me in the right direction.  If
it's not intended to look similar, would it be difficult to add?
I actually prefer the new implementation in Hobbit. To me the info report was very cluttered with exceptions & rules that would never be applied to the device. The Hobbit info alert rule table is much simpler to read, If it isn't in the table - it won't send an alert. Something I am actually looking forward to with my migration to hobbit.  My bosses and monitoring customers can understand this simple explanation. I can not count how many times I was asked about alert rules w/ BBGEN and my answer was, "that really doesn't apply to your server, ignore it..."

Sometimes bosses and management ask for things that are overcomplicated and really make no sense at all. Just have to be patient and explain why this is better ;)  If you really need this, sure it would not be hard to script up a report to appease management.
list Henrik Størner · Mon, 23 Jul 2007 17:52:01 +0200 ·
Hi Greg,

the alert configuration in BB was horrible. You've provided an
excellent example yourself: I cannot tell from that display what will
happen when a critical "disk" event happens (at least, not without 
re-reading the BB docs, which I have no intention of doing).

The Hobbit alert config tries to be a lot more flexible, but at the 
same time much easier to understand (so there's a better chance you'll 
get it right). And the info-column display also tries to be crystal
clear: It's obvious that I will NOT get an alert when the "disk" status
goes red, because it only sends alerts for the "network" and "temp"
columns.

It won't change. Tell your users it's WYSIWYG 1).


Regards,
Henrik

1) http://en.wikipedia.org/wiki/WYSIWYG for those readers who aren't old
enough to recognize this acronym.
quoted from S Aiello


On Sun, Jul 22, 2007 at 04:46:05PM -0400, user-762ee872a5a4@xymon.invalid wrote:
Hi Henrik,
 
Thanks for the reply.  A couple of more things if you don't mind, because I trust you gave me
the answer, but maybe I wasn't clear in my question.  I've added a little table below that represents
what I was asking.  I think what you told me was that in Hobbit, if the service does not appear in the
table, then it is implied that it will not alert.  That's Ok, I get that, but I'm being asked by the
pointy hair bosses, why they can't see the exceptions, like they do now with BB and BBGen.  If I'm
missing something in my configuration, great, please point me in the right direction.  If it's not intended
to look similar, would it be difficult to add?
 
Thanks again
-Grs-
Gregory R Shea
EMC Corporation
 
BB with BBGen3.6
| Services | Ex.Services | Weekdays | Time   | Recipients         |
|----------+-------------+----------+--------+--------------------|
| All      |             | All days | 0000-  | trap-10.10.10.10:0 |
|          |             |          | 2359   |                    |
|----------+-------------+----------+--------+--------------------|
| network  |             | All days | 0000-  | user-72358f08cb7a@xymon.invalid:120  |
| temp     |             |          | 2359   | user-1bf33e42478f@xymon.invalid:120  |
|----------+-------------+----------+--------+--------------------|
|                            Exceptions                           |
|----------+-------------+----------+--------+--------------------|
| cpu      |             | All days | 0000-  | trap-10.10.10.10:0 |
|          |             |          | 2359   |                    |
|----------+-------------+----------+--------+--------------------|
| All      |             | All days | 0000-  | user-1906180112d1@xymon.invalid |
|          |             |          | 2359   |                    |
|----------+-------------+----------+--------+--------------------|

Hobbit 4.2.0
| Service | Recipient     | 1st Delay | Stop After | Repeat | Time of Day | Colors         |
|---------+---------------+-----------+------------+--------+-------------+----------------|
| network | user-72358f08cb7a@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|         |---------------+-----------+------------+--------+-------------+----------------|
|         | user-1bf33e42478f@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|---------|---------------+-----------+------------+--------+-------------+----------------|
| temp    | user-72358f08cb7a@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|         |---------------+-----------+------------+--------+-------------+----------------|
|         | user-1bf33e42478f@xymon.invalid |     -     |      -     |   2h   |      -      | yellow,red     |
|---------|---------------+-----------+------------+--------+-------------+----------------|
list Larry Sherman · Mon, 23 Jul 2007 13:43:22 -0400 ·
TINSTAAFL Henrik, TINSTAAFL.

Thanks for the great work Henrik!

Larry

bbgen for Hobbit version 4.3.0-20061124

Statistics:
 Hosts               :  1201
 Status messages     :  7686
 Purple messages     :     0
 Pages               :    61

It won't change. Tell your users it's WYSIWYG 1).

*******************************************************************
• This e-mail is intended only for the addressee named above.
As this e-mail may contain confidential or privileged information,
if you are not the named addressee, you are not authorized
to retain, read, copy or disseminate this message or any part of
it.

*******************************************************************
*