[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: Sun, 10 Oct 2010 13:28:54 -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 :content-transfer-encoding; bh=qSFg+QCSYayDPSSHU43lbuHoyVupOtRbqWAatjgHQos=; b=gIsxBkUR4zMu3c4YqfFB7otKCuOX84l0lkJL8GReLryI7MReXeUENOvBx127ApuM5c 9C9osgAu/gfmJImFBdC2stlVQxlBYycxQsWBqo0WH5xfwIbHOFVrv9n1OBHHLn2q5k2g hz3g5LOPSqTpEmz5XJxtC0DHBtRGM8tWavAs0=
- 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:content-transfer-encoding; b=QW6dew1JZ+HOwuNOaRuYqitxdCG1hkKNZMsrmswrr6ylJ+bKoV4YOce0BZQtevfMEJ xP9nSIspIBWm9++agyzBqK+HK0dKX2/lXG9eCPdANXi1vOi2NbCQEOEVaW6Ax2oh0Cch 7cb3lAj8NnoN7+gyVfY0IjIDp3ZCIxfF9Iti4=
- 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> <AANLkTi=zv3qpCrfWeP8E=a1OHxaZnz=JfNK5EoBQ96Se (at) mail.gmail.com> <AANLkTinOph89V1ndGO-=O0yXkwq_Sz5n7BEhfQ_uv48B (at) mail.gmail.com> <5B7372AB-E232-44C8-AF17-9B35372DAF5A (at) gmail.com>
On Sat, Oct 9, 2010 at 3:30 PM, Jerald Sheets <questy (at) gmail.com> wrote:
> Always did it by hand. 3 shifts, 22 people, multiple escalations and calling circles. Never needed a tool.
> Just always considered it a part of standard admin work.
I disagree with this, vehemently. That which is complex, repetitive,
and error-prone should be *automated*. As senior professionals it is
our job to identify these sorts of operational vulnerabilities and
remedy them. After all, that's why we're using monitoring software in
the first place, instead of just sitting there reading log files all
day.
Reminds me of the T-shirt that says "Go Away or I Will Replace You
with a Very Small Shell Script". If I have a task that can be replaced
by a shell script, it's wasting my time and my employer's money for me
to keep doing it. And I have a long list of better things to do. And
if *all* of my tasks can be replaced by automation, well, I probably
should find a better job :-)
So, question is how best to automate this, not *whether* I should.
Thanks Betsy