[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xymon] Managing who gets alerts - shifts and rotations
- To: xymon (at) xymon.com
- Subject: Re: [xymon] Managing who gets alerts - shifts and rotations
- From: Elizabeth Schwartz <betsy.schwartz (at) gmail.com>
- Date: Sat, 9 Oct 2010 21:44:45 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:content-type; bh=sfgOQVFHiuJ/Yki0f7Mqi5iVi696c602Ysby7Gy1KJk=; b=LAY78qDpjldl3W9YobsGne5W1uSUpfSHL4f/iU4dcpMFFvtK1zCSqkJ6aOU51zd50O Z84On+2xXH9UGaSiA7tXk0tlAmlT8fI5lwAa0TWXSI6dg11UfuIXqQgAByMHmJ23d/YQ 7m2wbTiwjxbjb6Fa2/36NVSq2h5R5YUVHtc0A=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=ewzvCvFZvWJfWk7Nu6GEtXxfJrbrR3mY85ktBnrtVn3j7oqK/YS6w1fO7J28qQFXBD QincLvz7NfuNQEMRz5TCFuXzuuUH6zPWCJ2FKRCxinkn3pQFWb9AgUf64tBojTZV90gz oDcJVG1K4pzgrNRMCQQwigoLPVa7G+yUPF8Gk=
- References: <AANLkTik=Ez4-YGtG1ZM8VUmiqXqCFJXaM=_Ch+h=_H5g (at) mail.gmail.com> <AE6F386A-6C13-4B18-809B-D9768E3998A1 (at) gmail.com> <AANLkTine1B3Sx2CQLvZwLyKmKXsojP9a0mN1t8Q_Ru=Y (at) mail.gmail.com> <i8qoaj$o1a$1 (at) voodoo.hswn.dk>
We have people in five time zones reporting to three different
supervisors/team leads, with shifts staggered for maximal coverage.
Today we have 25 permutations of folks on duty, and the company is
growing fast, so the complexity is increasing. We need some sort of
way to allow the team leads to enter shift descriptions, that we can
keep separate from the paging rule sets. We've also got many hundreds
of servers, and people are screaming for more sophisticated rule set
management, but with BB we've got to duplicate 25 shift rules for each
new change - and then modify each set whenever anyone moves around.
Xymon makes the rules easier to *read* but doesn't lower the count.
If we have to write this tool, we will. If it lands on my plate, I'll
set up a spreadsheet that saves as a CSV and write a perl program to
parse the spreadsheet (if I fail to enlist someone who can do a GUI).
But I'm still really hoping that someone somewhere has already done
this! We can't possibly be the first to need this. And I'm a huge
believer in trying to find code before starting from scratch.
My ideal program would have a web interface with 24x7 blocks and the
ability to put who's on call into each block, allowing for multiple
entries. Then the back end would set up the mail aliases or .forward
files for tech on duty, oncall, backup (and be smart enough to know
that if there's no tech on duty, go straight to the oncall)
thanks again for any thoughts
Betsy