Re: [Nagios-devel] FW: [Nagios-users] Timeperiods and oncall

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] FW: [Nagios-users] Timeperiods and oncall

Post by Guest »


--Apple-Mail-2--557735139
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii

This is one of my pet peeves of Nagios -- that notifications are not =
particularly flexible. That is why we have two sets of contacts for =
everyone, one that notifies via pager and e-mail, and one that only =
notifies via. e-mail; as there isn't a way to have Nagios do that for =
us.

We do something very similar to what you are trying to do. We have a =
contact "groupname-oncall" that gets assigned to hosts and services a =
particular group is responsible for. That alias exists both in our mail =
system and our paging system, and is updated automatically by a script =
to point to the correct individual. The hardest part of this is writing =
the script to do the updates, as it has to be able to parse a =
configuration file with the dates/times your individuals are on-call and =
update the mail and paging systems with the correct information. In our =
case, the aliases are stored in LDAP, so it is trivial for us to make =
the updates.

For years I have wanted to find the time to write a back-end =
notification script for Nagios that would make notifications more =
flexible, I just haven't had the time. I want to be able to do things =
like:
o Notify via. e-mail on warnings but send a text message for critical =
or for some services/hosts send text-messages for everything
o Only notify the on-call individuals after hours but notify everyone =
during business hours
o Remove duplicate messages
o Allow for two-way messages so an reply can be sent via. e-mail or =
SMS to ack an issue (I almost have this in place today)
o Have a configuration file that drives all of the above
=20
On Apr 22, 2010, at 02:42, Deborah Martin wrote:

> =20
> Is anybody able to help with this ?
> =20
> Thanks,
> Deborah
>=20
> From: Deborah Martin [mailto:[email protected]]=20
> Sent: 21 April 2010 12:25
> To: [email protected]
> Subject: [Nagios-users] Timeperiods and oncall rotation with UK Public =
holidays
> Importance: High
>=20
> Folks,
>=20
> I'm using SLES 10 and Nagios 3.2.0.
>=20
> We have 4 oncall engineers which rotate over a 4 week period, each =
being oncall one week at a time.=20
> The oncall period is 17:30 - 08:00 each working day and then the whole =
period for any weekend or UK public holiday.
>=20
> My definitions are :-
>=20
> define timeperiod{=20
> timeperiod_name 24x7=20
> alias 24 Hours A Day, 7 Days A Week=20
> sunday 00:00-24:00=20
> monday 00:00-24:00=20
> tuesday 00:00-24:00=20
> wednesday 00:00-24:00=20
> thursday 00:00-24:00=20
> friday 00:00-24:00=20
> saturday 00:00-24:00=20
> }
>=20
> This is for all normal monitoring of our systems.
>=20
> Each oncall engineer is defined :-
>=20
> define timeperiod{=20
> timeperiod_name person1-oncall=20
> alias person1-oncall=20
> 2010-03-29 / 28 17:30-24:00 ; Monday=20
> 2010-03-30 / 28 00:00-08:00,17:30-24:00 ; Tuesday=20
> 2010-03-31 / 28 00:00-08:00,17:30-24:00 ; Wednesday=20
> 2010-04-01 / 28 00:00-08:00,17:30-24:00 ; Thursday=20
> 2010-04-02 / 28 00:00-08:00,17:30-24:00 ; Friday=20
> 2010-04-03 / 28 00:00-24:00 ; Saturday=20
> 2010-04-04 / 28 00:00-24:00 ; Sunday=20
> 2010-04-05 / 28 00:00-08:00 ; Monday=20
> }
>=20
> define timeperiod{=20
> timeperiod_name person2-oncall=20
> alias person2-oncall=20
> 2010-04-05 / 28 17:30-24:00 ; Monday=20
> 2010-04-06 / 28 00:00-08:00,17:30-24:00 ; Tuesday=20
> 2010-04-07 / 28 00:00-08:00,17:30-24:00 ; Wednesday=20
> 2010-04-08 / 28 00:00-08:00,17:30-24:00 ; Thursday=20
> 2010-04-09 / 28 00:00-08:00,17:30-24:00 ; Friday=20
> 2010-04-10 / 28 00:00-24:00 ; Saturday=20
> 2010-04-11 / 28 00:00-24:00

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked