I think you gave me the right way to do this. Until now I was able to solve everything without Event Procedures but I knew the day will come that I have to deal with them. :)
I am really sure we will do the steps mentioned by Raphael. Thanks Raphael and Christian for your good and quick answers!!! Have a good weekend too. Yours sincerely Siegfried Behring Von: Franck, Raphael [mailto:raphael.fra...@computacenter.com] Gesendet: Freitag, 22. Juli 2016 13:37 An: spectrum <spectrum@listserv.unc.edu> Betreff: AW: [spectrum] Inode Monitoring with Spectrum Hi Siegfried, list, Christian is absolutely right, using extTable scripts is the way to go. You mentioned the Spectrum Policy Manager, so just a few sidenotes on how we do that: - the watch is looking for extResult != 0 on the UCDavisSNMPApp application model, always on all table rows - the watch is controlled by Policy Manager - the watch is triggering events, which trigger Event Procedures to o load the content of extOutput additionally, to have that displayed in the event message o get the parent model, which is the device o raise and clear alarms on the device model by creating events on the device model o discriminate on the row index, for independent alarm raise and clear per row - all evaluation and threshold logic is put into the scripts disadvantage: every row that is configured will be monitored, there is no partial ignore or maintenance advantage: the sysadmins may add and remove rows as needed, you don't have to touch Spectrum every time The same procedure also works for the other UCD tables like prTable, dskTable, laTable, fileTable and logMatchTable. Finally, using the fix statements, you could even automatic trigger remediation actions from Spectrum, by making SANM set the attribute through SSdb, which will cause an snmpset to the agent. That's a sample from a dev box, not really checking but more listing something: [cid:image001.png@01D1E426.9123FCC0] All: have a good weekend. Mit freundlichen Gruessen - Yours sincerely Raphael Franck Consultant Delivery - Applications - Automation & Reporting Global Infrastructure Operations Computacenter AG & Co oHG Enabling Users Europaring 34-40, 50170 Kerpen, Germany Tel.: +49 2273 597 7842 Mobile: +49 173 6806997 Short-Dial: 577842 E-Mail: raphael.fra...@computacenter.com<mailto:raphael.fra...@computacenter.com> WWW: www.computacenter.de<http://www.computacenter.de/> Von: Christian Schneider [mailto:christian.schnei...@4-tune.ch] Gesendet: Freitag, 22. Juli 2016 12:13 An: spectrum Cc: spectrum spectrum Betreff: Re: [spectrum] Inode Monitoring with Spectrum Hi Sigfried, Souldn't be a big issue. NetSnmp is capable to run scripts when getting polled. These scripts need to be written to get the information about the inodes and gives that value back to Spectrum via SNMP. Here you will find a easy intro https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html Kind regards, Christian Schneider Enterprise Service Specialist 4-tune GmbH Sägereistrasse 33 CH-8152 Glattbrugg Mob +41 79 418 45 42 Tel +41 71 930 07 00 Fax +41 71 930 07 01 Mail christian.schnei...@4-tune.ch<mailto:christian.schnei...@4-tune.ch> www.nexellent.ch<http://www.nexellent.ch> www.4-tune.ch<http://www.4-tune.ch> [cid:image002.png@01D1E426.9123FCC0] Am 22.07.2016 um 12:05 schrieb Behring, Siegfried <s.behr...@dvz-mv.de<mailto:s.behr...@dvz-mv.de>>: Hi all, we want to monitor the inode usage global with thresholds for all our servers like monitoring rules for file system monitoring. It seems that inodes are not included in the default configuration of net-snmp client. Because of that spectrum does not have an attribute for that. Even if it would the variations of partitions and the assigned ids are too dynamic to configure static watches in combination with policies for distribution. The main question: How can we monitor the inodes from our linux systems with spectrum? Is there a way to tell snmp to give inode informations? First tries with google answers were unsuccessful. And if I can map a snmp oid to an attribute how can I build a dynamic watch for partitions by partition name? The main goal would be to distribute this dynamic watch with policies. Even if you have a totally other way I would be very curious. Mit freundlichen Grüßen Siegfried Behring Servicecenter Netze SCN E-Mail: s.behr...@dvz-mv.de<mailto:s.behr...@dvz-mv.de> Telefon: +49 (3 85) 48 00 328 Telefax: +49 (3 85) 48 00 98 328 Internet: www.dvz-mv.de<x-msg://2/www.dvz-mv.de> _____________________________________ DVZ Datenverarbeitungszentrum Mecklenburg-Vorpommern GmbH Lübecker Str. 283 - 19059 Schwerin Sitz der Gesellschaft: Schwerin | Eintrag im Handelsregister: HRB 187 / Amtsgericht Schwerin Geschäftsführer: Hubert Ludwig | Aufsichtsratsvorsitzender: Staatssekretär Peter Bäumer _____________________________________ * --To unsubscribe from spectrum, send email to lists...@unc.edu<mailto:lists...@unc.edu> with the body: unsubscribe spectrum christian.schnei...@4-tune.ch<mailto:christian.schnei...@4-tune.ch> * --To unsubscribe from spectrum, send email to lists...@unc.edu<mailto:lists...@unc.edu> with the body: unsubscribe spectrum raphael.fra...@computacenter.com<mailto:raphael.fra...@computacenter.com> ----------------------------------- Computacenter AG & Co. oHG, mit Sitz in Kerpen (Amtsgericht Köln HRA 18096) Vertretungsberechtigte Gesellschafter: Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB 28384) Vorstand: Tony Conophy Aufsichtsrat: Michael Norris (Vorsitzender) Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284) Geschäftsführer: Dr. Karsten Freihube, Dr. Thomas Kottmann, Reiner Louis, Thomas Jescheck Visit us on the Internet: http://www.computacenter.de<http://www.computacenter.de/> Visit our Online-Shop: https://shop.computacenter.de<https://shop.computacenter.de/> This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. ----------------------------------- * --To unsubscribe from spectrum, send email to lists...@unc.edu<mailto:lists...@unc.edu> with the body: unsubscribe spectrum s.behr...@dvz-mv.de<mailto:s.behr...@dvz-mv.de> --- To unsubscribe from spectrum, send email to lists...@unc.edu with the body: unsubscribe spectrum arch...@mail-archive.com
