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.

Preprocessing out apostrophes from Message text in Log Analyser

I was going to start with my problem, instead ill ask another more OBVIOUS question:

Why can't we just pick varbinds to create/compose a message text from?

This has been done since the dawn of SNMP time, and for the life of me I can't figure out why solarwinds has removed / doesnt offer this for SNMP traps any longer. its just made the whole SNMP trap receiving painiful

Anyway - on to my issue:
As I am forced to use SQL substring to get the message i want as an alert message - I come across issues with apostrophes inserted into the event message. Oracle OEM is a classic case - even its test message has apostrophes in it. This has the effect of breaking the substring function as it stops when it sees an unexpected apostophe.

Has anyone managed to get around this?

I thought about calling a script to parse it out and then resubmit as a trap, but seems longwinded.



  • What exactly isn't possible? There are some ways how to get varbinds from a trap. For example for versions 2020.2.5+ using ${N=OLM.AlertingMacros;M=OLMAlertMessage.VbName1}  or ${N=OLM.AlertingMacros;M=OLMAlertMessage.VbData1}  (up to VbName10/VbNData10) which might help if the varbind you are interested in is a part of trap which always has the same structure.

  • I was just looking at the structure for OEM traps, the name of the device being monitored comes through as varbind 21. is it really only limited to the first 10 varbinds?

  • Wow, you have 21+ varbids in a trap? You can raise the number in Advanced Configuration (aka centralized settings), setting AlertMaximumTrapVarBindings.

Reply Children