Re: [PATCH] Total-#-of-starts counter

[Michel Marti]

Christian Hopp wrote:
> On Wed, 2 Feb 2005, Martin Pala wrote:
>
> > I think it is better to separate such functionality from monit. The 
> > new m/monit version which we work on has this functionality integrated 
> > already. It allows to collect all types of events from all monitored 
> > nodes, sort them by various criteria, etc. For illustration is in the 
> > attachment screenshot of related m/monit part (just basic screenshot - 
> > it has much more functionality). It can also make graphs of runtime 
> > service properties, such as space usage, load average, etc.

Remember: I am using monit on an autonomous embedded device that should run 
without any user intervention. I don't use monit alerts (No SMTP available) and 
I certainly cannot use m/monit.

> I can only agree.  IHMO it doesn't give you much of an advantage to do 
> diffent actions based upon a certain number of restarts especially 
> without the context of the timeframe. =>  -1

It would still give some hints on which services are "unstable" when comparing 
the restart counter between different services, e.g. if service A has 2 restarts 
within a given timeframe but service B has 10, this might indicate a problem 
with service B that should be investigated... IMO the patch is really not 
intrusive and might provide some benefit to some monit users... Others might 
just ignore the counter when looking at monit's status. It really doesn't hurt 
to have it.

By the way: the service monitor included in "Sun Cluster" (pmfctl) also provides 
such a counter ;-)

Michel