monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Plans for the next release


From: Jan-Henrik Haukeland
Subject: Re: Plans for the next release
Date: 02 Jul 2002 15:13:26 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service)

Martin Pala <address@hidden> writes:

> I think that it is general enough to allow users get the alerts where
> needed.

Good, good, maybe it will need some synatx tweaking but the general
idea is good then?

> Maybe monit could have native support for SNMP (mentioned in the past)

Yes, I thought about this, but if we can get away with having the
NOTIFY program do this it's probably better? You know me, Mr. "Keep it
as simple as possible for it to work" 

> Maybe the target for PROGRAM, SNMP, DB, etc. can be set on global
> level with its specific options and in the rule then can be used only
> target name, such as:
> 
> 
> ...
> SET TARGET mysnmp
>    COMMUNITY abcd1234
>    HOST 127.0.0.1
> 
> SET TARGET myprogram
>    PROGRAM logger
>    ARGUMENTS {...}
> 
> SET NOTIFY myprogram on {RESTART, TIMEOUT, CHECKSUM}
> SET NOTIFY msnmp on {RESTART, TIMEOUT, CHECKSUM}
> 
> NOTIFY directive can be used on global level (for example with SET
> NOTIFY ...) or can be overriden on per-process level (NOTIFY ... )

Hey, this is a pretty good suggestion!  BTW what is COMMUNITY?  (I'm
not a sys. admin. you know, but a former pencil neck CTO and now a
management consultant, IRL :)

> Maybe SNMP will be useful and DB logging is to proprietary.

DB logging is probably to proprietary we would have to create
something like JDBC then :)

> What about it?

I'll put it up in our plan and feature list for the next release and
we'll see.

-- 
Jan-Henrik Haukeland



reply via email to

[Prev in Thread] Current Thread [Next in Thread]