Implemented

Forward "traps" to Orion NPM

We want to use Kiwi to perform initial filtering of our trap and syslog messages, and then pass only the items we want to Orion NPM for association with nodes and (possibly) alerting.

This works fine for syslog since the "forward to another host" function was built for that.

But traps are a problem.

First - the trap message is "blobbed" into a single message string so that you can't parse out one trap variable (ie: a varbind) from another.

Second - traps can't be forwarded transparently (it can in other tools, and even free tools like net-snmp)

Third - traps can't be forwarded *at all*, so you have to pick a specific trap OID for your rule

What I'm asking for is either:

1) support for actually forwarding a trap transparently, as the "forward to another host" option does for syslog...

OR

2) allowing the "forward to another host" option to support variables so that we can build our outbound message using the trap's varbind elements and pass THAT to Orion NPM so that the ultimate alert is something readable.

Parents
  • NPM sucks as a trap server though.

    How about forwarding alerts or notable events to Orion as a possible action for a single trap, or XX number of traps so that alerts could be generated for single traps or XX traps in the last NN minutes/hours/days?

    Peter

  • The trap alert does have a threshold that you can set, as well as a delay after the trigger so you do not continuously get emails over and over. - but you need to do it for each node, otherwise the same type of traps from different nodes will build up to your threshold counts.

Comment
  • The trap alert does have a threshold that you can set, as well as a delay after the trigger so you do not continuously get emails over and over. - but you need to do it for each node, otherwise the same type of traps from different nodes will build up to your threshold counts.

Children
No Data