This is a multi-part message in MIME format.
------_=_NextPart_001_01C3341E.2A6F9673
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C3341E.2A6F9673"
------_=_NextPart_002_01C3341E.2A6F9673
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi all,
=20
status sounds are very usefull when working near a Nagios browser
client.
In our configuration most mails, pager and sms messages are sent only
during non working hours. The rest of the time we use the sound of
Nagios as indicator for failures, because there is allways someone or
another near the console, where a Nagios browser session is running as
well.
=20
We experienced that Nagios will play sound at the first time it
recognises a warning or critical stage. This can be very annoying when
for example a ping reply reaches warning or critical level for a short
time and then fall back to normal again. If this happens to often,
operators lose interest in looking at Nagios.
=20
Increasing warning or critical level is not a real option, because i
want to recognise these levels but only when they occure for a defined
time, (max_check_attepts).
=20
We would wish to implement playing sounds only, when max_check_attepts
is reached, as for sending pager, sms or emails. =20
=20
I implemented this option in tac.c some weeks ago, and everybody is
happy since then.
Attached you will find my modifications to tac.c, (marked with SAN).
This was only a quick hack and could may be done differently. Of course
the same modifications must be done in status.c.
=20
Any other ideas ?
=20
Thanks and regards,
Markus Saner
=20
=20
------_=_NextPart_002_01C3341E.2A6F9673
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Nachricht
Hi=20
all,
status =
sounds are=20
very usefull when working near a Nagios browser=20
client.
In our =
configuration=20
most mails, pager and sms messages are sent only during non working =
hours.=20
The rest of the time we use the sound of Nagios as indicator for =
failures,=20
because there is allways someone or another near the console, where a =
Nagios=20
browser session is running as well.
We =
experienced that=20
Nagios will play sound at the first time it recognises a warning or =
critical=20
stage. This can be very annoying when for example a ping =
reply reaches=20
warning or critical level for a short time and then fall back to normal =
again.=20
If this=20
happens to often, operators lose interest in looking at=20
Nagios.
Increasing warning=20
or critical level is not a real option, because i want to recognise =
these levels=20
but only when they occure for a defined time,=20
(max_check_attepts).
We =
would wish to=20
implement playing sounds only, when max_check_attepts is re
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]