NagMIN Update

[Martin, Stanley G [GMG]]

Don't know if this is a problem or something I'm seeing incorrectly, but
when I go to add a new Service Dependency, the choices for Execution
Criteria Failure and Notification Criteria Failure don't seem to be
correct based on the Nagios documentation.  The choices given are:

Up
Down
Unreachable
Critical
None

The choices are the same for both.

>From the Nagios documentation they should be:

OK
Warning
Unknown
Critical 
None

define servicedependency{ 
     dependent_host_name host_name 
     dependent_service_description service_description 
     host_name host_name 
     service_description service_description 
     execution_failure_criteria [o,w,u,c,n] 
     notification_failure_criteria [o,w,u,c,n] 
}

Stanley G. Martin
System Administrator
Sprint - EIS3 Customer Care 
Stanley.G.Martin at mail.sprint.com



-----Original Message-----
From: FReimers [mailto:FReimers at infosysinc.com] 
Sent: Wednesday, April 02, 2003 10:44 AM
To: nagios-users
Subject: [Nagios-users] NagMIN Update

All,

I want to thank those of you who have tried NagMIN so far.  I've gotten
a lot of good feedback and have added many of the features requested.
I'm going to release NagMIN 1.0.6 this evening that will be the most
stable beta so far.  It includes global field updating so that
host_name, contact_name and other key fields included in parents,
members, etc., gets changed or deleted everywhere and support for
hostgroup escalations.

NagMIN can learn your network now and do port scans of your hosts and
dynamically create your services, amongst other things.  Personally, I
really like being able to verify a configuration before activating it.
There isn't a lot (or any) real documentation yet.  I'm shooting for two
weeks to have the first stable release and then perform proper release
management from that point.  I am creating updatennn.sql files for
updating the schema for existing databases.  Make sure that you run all
of the from the point that you first installed it.

The biggest problem I've encountered for release control so far was that
I initially set some of the field lengths too short.  I've made a lot of
changes to the database schema and I think 1.0.6 is pretty stable.  The
port scanning was a bit slow but I sped my own server up dramatically by
installing NMAP 3.20 (and rebooting it!!).  

I have release notes on SourceForge.  If you don't know how to find it,
you click on the release name on the download page.  I'm going to be
monitoring SourceForge for bug tracker, feature requests, etc..  There's
nothing there now and I'm looking for your input.

Check http://nagmin.sourceforge.net for the latest information.


-------------------------------------------------
Fred Reimers (CCIE #1469, CCSA)
Senior Network Consultant
Info Systems, Inc.
freimers at infosysinc.com



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null