This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Trap Alert/Filter Variables question

This is a general how-to question regarding whether or not solarwinds has the ability to pull out a specific section of the $Message instead of the entire message when logging the trap to a log file for example.  When I use the default $Message, all of the OID info including the trap message (basically everything I see in the trap viewer) is written to the log file.  Just wondering if there was a defined variable or way to filter out all the junk and just get the Trap message that was sent by the device.


Thanks for anyones input on this.

Parents Reply Children
  • FormerMember
    0 FormerMember in reply to Craig651

    We shipped 9.0 a few weeks after the first post in this thread.  We didn't add this in 9.1, which shipped in October.  We haven't shipped a release since then.

    I don't have a firm date, but we have, however, acquired Kiwi's syslog and trap server, so that will almost certainly impact what we do.



  • We shipped 9.0 a few weeks after the first post in this thread.  We didn't add this in 9.1, which shipped in October.  We haven't shipped a release since then.

    I don't have a firm date, but we have, however, acquired Kiwi's syslog and trap server, so that will almost certainly impact what we do.



    We currently run Kiwi as our syslog and trap handling software and found this thread as we encountered the problems described in the first post.  Are you considering incorporating Kiwi into Orion NPM?

  • FormerMember
    0 FormerMember in reply to Lisser

    We intend to leverage Kiwi's technology and the Syslog-related expertise of that team to enhance Orion's syslog functionality, but that's not happening in v9.5, so we don't have details yet on exactly what we plan to do.

  • We figured out a painful workaround to get this to work.  Basically when a trap comes into the system that triggers a alert the alert runs a script that takes the $message and rips out only the info we care about and then the script send out the alert.  Every group I work with gets a little frustrated with the time it takes to get this all set up and working. I have been asked a couple of times when we would be switching to a Trap receiver that will do all this a little easier. It would be great to get this integrated sooner rather than later.