disk usage monitoring

Hi Net-SNMP gurus, 

First happy New Year 2007! 

Though it is not necessary for the understanding of this post, I'd like first to give you some background about what we're doing. At Amadeus Data Processing center, we're running in a 24x7 environment. It is important to ensure the service availability to our customers, a too long outage of a service may lead Amadeus to pay penalties. Obviously, monitoring is here a key component for detecting possible problems before they turn to an outage. 

Traditionally, commercial monitoring solutions have been used in the past. However, the pressure of reducing software costs plus the growing interests in open source software invites to look at other alternatives. A very promising one is, as you guessed, Net-SNMP. 

In a pilot project, we used Net-SNMP for basic OS monitoring (cpu, memory, disk usage), using DISMAN event MIB capabilities. If for instance a server is running low in memory, then the Net-SNMP Agent on the server fires a trap to a receiver station. If required, this receiver station will then inform the appropriate responsible persons (email, sms, call...) about the current problem. 

This solution has been quite successful so far, the net result is that I have been asked to implement this solution for other projects as well. For this, I need to generalize the monitoring of the disk usage as follows: 

1- for some known file systems mounted at boot time, I want to issue two kind of traps:
    (*) if file system is > X% full, a trap corresponding to a warning situation is sent.
    (*) if file system is > y% full, a trap corresponding to an alarm situation is sent. 
Here X, and Y depends on the file systems. 

These file systems are known when the Agent configuration file is written. 


2- for the remaining file systems known at Agent boot, a default policy applies: 
    (*) if file system is > 90% full, a trap corresponding to a warning situation is sent.
    (*) if file system is > 95% full, a trap corresponding to an alarm situation is sent.

Here the file systems are not necessarily known when the Agent configuration file is written. The default policy should be applied to all file systems known by the Agent but the ones explicitly defined previously in 1).


As far as I can see:

1) can be easily implemented using the "disk" directive, and monitoring the corresponding variable for disk usage UCD-SNMP-MIB::dskPercent.x

2) A default policy could be implemented for *ALL* file systems, using the "includeAllDisks" directive. However, doing so would also define a default policy for the file systems defined in 1), which is not what I want.

Is it possible to achieve 1) and 2) at the same time? We are currently using Net-SNMP 5.3.1.

Thanks in advance,
Loic.

-- 
--
A project is by definition unique. That means: you won't be tortured the same way twice. 

Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users