Traps, Services, and Extensibility
"Brian E. Seppanen" <[email protected]>
| Newsgroups | gmane.network.netsaint.user |
|---|---|
| Organization | Charter Communications |
| Message-ID | <[email protected]> |
Hi Folks: I have a theoretical question to which there is no right or wrong answer, but I wanted to present a situation and see if there was a possible solution or a best practice. We use netsaint for a lot of our monitoring, and despite the fact that netsaint (nagios) isn't intended as a NMS -- as the documentation indicates, -- I find myself being told to script trap events into netsaint on a regular basis. One of the problems with trap events is that you can receive multiple traps at any one time for a single device. If you're like me and you define a single placeholder for traps to ease administration, this usually means the last trap wins, and others would be missed, or the traps need to be consolidated so that they all show up and are aggregated, which isn't always very easy to do. I've used both scenarios. Is there any way to include what I would term expandable containers that would increase to hold an increasing number events. Of course the problem becomes one of then making sure that a corresponding container for a specific event has it's corrolary event clear/reset/expand the original trap. Which introduces a number of different problems. What have others done? Thanks, Brian Seppanen [email protected] 906-228-4226 ext 23 ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en