[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [hobbit] Use hobbit in operation center with critcal systems view
- To: <hobbit (at) hswn.dk>
- Subject: AW: [hobbit] Use hobbit in operation center with critcal systems view
- From: Gräub Roland <roland.graeub (at) rtc.ch>
- Date: Mon, 12 Nov 2007 10:12:39 +0100
- References: <BA36A6D9A027AB4DA1831312C24EB388096A0AB3 (at) rtcnt66.prod.rtc.ch> <20071108232642.GB14260 (at) hswn.dk> <20071109083809250.00000001804 (at) nbeduard>
- Thread-index: AcgivJ41Vr/C7iKjTOizMmO7MXzKAACTfOYg
- Thread-topic: [hobbit] Use hobbit in operation center with critcal systems view
> >
> > > Special Case missed or belated Messages by Operation
> > Center; Now some
> > > application/scripts sends Alerts to the Console View and
> > the Operation Center make an alert call for each event.
> > > A problem in Hobbit/BB is when changes happen in red
> > messages, the Operation Center didnt realize that until the
> > acknowledge time runs out and they make the alert call again.
> > > This can happen for example in the disk status test (a
> > second filesystem goes red) or with nested Tests/Logfiles.
> > With the Event Console they get two messages (each for one
> > Filesystem).
> >
> > This is a problem with all of the tests that have multiple
> > ways of going
> > red: disk, procs, msgs and http are the common ones. I don't
> > have solution to that right now. The way Hobbit works right
> > now assumes that when you get an alert about the "disk"
> > status, you keep on fixing it until the status goes green -
> > and then the Operations Center won't need to raise a ticket
> > for the second event.
> >
> I use as a solution to this problem, the counting of alerts
> within each test, if the number of alerts has changed, then a
> new alert will be generated with the status of the test
Sounds promising; how it works exactly ?
If the alert is already red, how you can send a new alert ?