We use a bit of a hacky watch for our filesystem monitoring. What we did was set up a watch to monitor the dskErrorMsg table in UCD-SNMP-MIB. In snmpd.conf on the target server, you configure the filesystems you want to be published to the table (/, /var, /usr/local, etc). Normally the dskErrorMsg field is empty, but if a filesystem reaches the threshold specified in snmpd.conf, snmpd will put an error message in there that reads something like "/var: less than 40% free (= 88%)". We have Spectrum compare dskErrorMsg to the empty string "" and generate an alarm if it's not an empty string.
I'm not sure if our solution will help you, but it does move the responsibility for configuring monitored filesystems entirely outside of Spectrum. The watch is enabled by default on any Host_NetSNMP devices and configuring the desired filesystem monitors is left as the responsibility of the sysadmin of that server (we use a similar approach for process monitoring). On 4 Jun 2010, at 11:47, Craig Cook wrote: > I would suggest another method. Use something like nagios, xymon, etc to > monitor your servers. Make them send traps to spectrum. > > Spectrum does not have a reasonable method to monitor large amounts of file > systems. It can’t have “global defaults” eg. more that 90% utilized set > alarm on any Filesystem. > > It does not detect new file systems and automatically start monitoring them. > > Craig > > From: Mark Serencha [mailto:[email protected]] > Sent: Friday, June 04, 2010 11:29 AM > To: spectrum > Subject: RE:[spectrum] Using CLI or CORBA to update RFC2790 monitors? > > I have an update to my post below: > > I have been able to add models for RFC2790 file system monitoring using CLI. > It has to be done in 3 steps: > · Create the monitor model > · Create an association to its device model > · Create an association to its device’s Host Resources model. > > However, the CLI-generated monitors do not function; they do not appear in > the host’s System Resources view, > and under the OneClick Locater tab, the All Monitored File Systems view shows > the monitor with status “Threshold cannot be evaluated”. > > Also, I have discovered that if I use OneClick to add a file system monitor, > and then delete that monitor, > the model is not deleted from the SSDB, and it still appears with status > “Threshold cannot be evaluated” in the OneClick Locater tab. > If I create a new monitor for the same file system, even with the same > threshold settings, > a new model is created, but the old model still is in the SSDB, and both > models can be seen in Locater. > > I have compared attributes in CLI (functional vs. non-functional monitors), > however, I cannot determine how the deleted/non-functional models are > disabled / disassociated from the parent device. > I am still researching this issue, and would appreciate any feedback on any > related problems that others may have solved. > > In the meantime, I have opened a case with CA regarding the problem of not > removing the deleted monitors from SSDB. > That has potential to cause a lot of SSDB pollution. > > Platform: Windows 2003 Standard R2 SP2, Spectrum 9.1.2.12 > > Thanks, > --Mark S > > Mark Serencha – Inforonics LLC – (m) +1-781-439-0519 – (w) +1-978-698-7418 – > [email protected] > > From: Mark Serencha > Sent: Monday, May 17, 2010 11:50 AM > To: spectrum > Subject: Using CLI or CORBA to update RFC2790 monitors? > > Hi Spectrum list, > > I have about 300 hosts, with over 11,000 monitored file systems to monitor. > This large volume of monitors is too many to add by hand. > And there are thousands of unique file system names, which makes it > difficult, if not impossible, to use Spectrum’s built-in Global > Collection-based File System monitoring (other than for standard file systems > such as /, /usr, /var...). > Also, file systems may move from host to host during normal operation, so old > monitors may no longer be relevant, or new monitors may be required. > > We do have a central location for our threshold settings, so some creative > scripting or coding is possible. > I am interested to see if anyone is using CLI (or CORBA) to dynamically > add/update/remove RFC2790 file system monitors in the SSDB. > > I’ve done some CLI testing, and this approach seems viable. > My concern is that this represents a large number of updates to keep Spectrum > in sync with our data source, and a high risk of SSDB corruption. > > Is anyone doing anything at all similar to this, or perhaps has a better > option which I have not considered? > > Thank you, > --Mark S > > Mark Serencha – Inforonics LLC – (m) +1-781-439-0519 – (w) +1-978-698-7418 – > [email protected] > > > • --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > • --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
