How about changing the way you view that issue - create a GC for unreponsive devices, then chaneg the device down alarm to do the following 1: check for GC membership - if in the "non responsive " group then create a minor alarm and also use an event rule so it waits for a period , say 5 minutes, for a device up, if no device up then create the real device down alarm 2: for all other devices just keep it as normal
So that way no need to change polling intervals I use that model and have the initial device down alarm create the first alert then if after 1 minute create the real device down for 1 minute alert Standard device up event clear the alarms and give valid info On 25 April 2013 20:31, Christian Fieres <[email protected]> wrote: > Hi all, > > this may once more be a dumb question, but I guess I have lost my focus a > bit after 16 years SPECTRUM administration. > > I was asked whether it is possible, and I quote, "to manage devices that > tend to be unresponsive for short periods of time, but nevertheless with a > reasonable way of getting to know what state the device is in". In other > words, we do not want to be BOMBED with ten alarms an hour because the > device is unresponsive for three minutes, but always be able to say, yes, > it's up again. > > Discussing the idea, I was unable to answer the following question: In > what intervals does SPECTRUM poll an unresponsive device? It is clearly > more often than in normal operation, for there are alarms that last less > than our 30 seconds standard polling interval. Some tests with varying > intervals lead me to the conclusion it is roughly half the configured > polling interval. Might this be true? > > And, more importantly: Can it be configured? In easy words, I need to poll > a device once an hour, but once SPECTRUM has detected an outage, I > definitely need to know when the device comes up again, and not eventually > after 30 minutes. > > Things like SPM and EventDisp customizing have been discussed already. Due > to the dynamic nature of the amount of models affected, it must be an > attribute based solution, i.e. something ouf of the box. > > Thanks a lot for your thoughts! > > Freundliche Grüße / Best regards > > Christian Fieres > > Mainova AG > Planung und Betrieb Infrastruktur (M3-ON2) > Service Operation Center > Solmsstraße 38 > 60623 Frankfurt > > Telefon / Phone (069) 2 13-2 36 17 > Mobil / Mobile (0170) 5 60 15 63 > Telefax / Facsimile (069) 2 13-9 62 36 17 > E-Mail [email protected] > > > > Mainova Aktiengesellschaft Solmsstraße 38 D-60623 Frankfurt am Main > Vorsitzende des Aufsichtsrates: Dr. h. c. Petra Roth, Oberbürgermeisterin > a. D. > Vorstand: Dr. Constantin H. Alsheimer (Vorsitzender), Dr. Peter Birkner, > Lothar Herbst > Sitz der Aktiengesellschaft: Frankfurt am Main Amtsgericht Frankfurt HRB > 7173 USt-ID-Nr. DE 114184034 > > > Mainova steht für besten Service, faire Verträge und top Preise für Ihre > Energie - mit Auszeichnung! > Mehr Infos unter: http://www.mainova.de/auszeichnung > > - --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > > --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
