|Subject:||Re: [Announce] monit 4.3 released|
|Date:||Mon, 06 Sep 2004 16:40:38 +0200|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040820 Debian/1.7.2-4|
Andrea Pagani wrote:
This is a feature and bugfix release. The most important change in this release is the refactoring of event engine, which allows to send alert and/or do optional action in the case that the monitored service recovered from the failed state.When you say "and/or do optional action", do you mean that mail alerting can be disabled/substituted by other types of actions, like SNMP traps??? In this case, is it possible to disable mail alerting???
Yes - just omit the alert recipient definition (i.e. don't add 'alert ...' or 'set alert ...' option to the monit control file).
For example, you can use this feature to send SNMP trap in the case that the service is up again (via snmptrap exec) in addition to failed state related action (for example SNMP trap as well) which was supported in previous releases. The action is optional - monit will send alert notification about any service state change by default.Is there some sort of native support for SNMP or the only way to do some SNMP action is to use the EXEC statement (triggering some SNMP tools CLI)???
There is no native support for SNMP yet, you can use monit exec action with utility like snmptrap to generate the SNMP event.
We are working on m/monit, which will provide support for central monitoring management of monit and SNMP agents, events, history, SLA, central configuration, etc. ;)
|[Prev in Thread]||Current Thread||[Next in Thread]|