Doubt in nagios

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Jlnarayanan00 at aol.com
> Sent: Monday, January 03, 2005 3:29 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Doubt in nagios
> 
> 
> Hi ,
> 
>     Our requirement is such that we would like to monitor a dial-up-
> connection trend in an ISP scenario.For example, we would like to
monitor
> the number of connections for the last 10 minutes(say) and if there
was a
> 20% drop in the number of clients connected then a alert should be
raised.
> Is this type of trend monitoring is possible using nagios?. For this
we
> need to collect data for some amount of time and store in data base
and
> again fetch these values to check for the alert condition. If so how
> should be our plugins?.
> Can anyone help me out in this?.


There's no standard plugin to do it but it should be pretty
straightforward to write. In pseudo-code --
 
   Check number of current connections
   Store value in database
   Compare to previous value
   Exit OK if within acceptable parameters
   Exit ERROR if outside acceptable parameters
   Exit ERROR or UNKNOWN if unreachable or unexpected output received.

There are of course special circumstances for the first check but that's
a pretty rough outline of what you need to do. This also presumes that
you can check the number of connections from a unix command line in some
way.

http://nagiosplug.sourceforge.net/developer-guidelines.html

--
Marc 



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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