On Fri, 7 Feb 2003, Gregor Goestl wrote: > Hi All! > > startupalert: > As I tried the startupalert I saw, that the startupalert is processed, > if the monitor fails and if it returns that all is ok. Is it > possible to distinguish the two different states in the alert?
a startupalert is called only when the mon server starts running or if it has been reset by a client "reset" command. startupalerts do not rely on the return value of monitors, or that monitors were even run at all. > no_comp_alerts: > I don't understand the function of this setting. Can someone explain it > to me, with an example (I don't understand the meaning of > the explanation in the manual!) the default behavior is that upalerts are called only if a regular alert was previously called. this means each alert which says something is "down" will correspond with an upalert. setting the no_comp_alerts will make mon send upalerts even if there was no corresponding "down" alert. that is, if a service is failing, then it stops failing, an upalert will be sent, regardless of whether or not a previous "down" alert was sent. a "down" alert is just a regular alert, specified by the "alert" setting in period definitions. _______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
