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