You are here

SNMP Trap - preprocessing

1 post / 0 new
Laurent Block's picture
SNMP Trap - preprocessing

Hi all,

Our company recently purchased the Enterprise version of OpsView.
First of all I have to say that we are very happy with the product, it just makes life easier!

Now, here's my question to the pro's of OpsView:

We recently have setup the SNMP trap processing on our monitoring server. Thanks to the documentation, everything was up and running in a blink of an eye and the first servers are sending traps to OpsView.
One of the hosts is an Alcatel-Lucent appliance, which is sending traps in the following format:

UDP: [ALU]:49999->[OPSVIEW]
DISMAN-EVENT-MIB::sysUpTimeInstance 0:3:32:46.62
SNMPv2-MIB::snmpTrapOID.0 SMP-MIB::alarmTrap
SMP-MIB::pduAlarm.0 "ALARM=platform/platform:startup|ID=XXX|OCCURENCE NB=XXX|STATE=close|LEVEL=minor|OBJ=XXX|HOST=XXX|APPLI=XXX|SERVICE=XXX|SEP=|SOURCE=Defence.cxx|OPEN DATE=XX/XX/XX 18:08:48|ACK DATE=255/255/65535 255:255:255|ACKED BY=|COMMENT= |COMMENTED BY=|CLOSE DATE=22/07/2014 21:38:49|CLOSED BY=XXX"
SNMP-COMMUNITY-MIB::snmpTrapCommunity.0 "smp-in"
SNMPv2-MIB::snmpTrapEnterprise.0 SMP-MIB::smp

As you can see, the pduAlarm.0 contains the pipe character ("|"), which will be processed as performance data in OpsView.
After some research I didn't see any way in order to disable perf-data for that host and I'm not sure if in that case, the complete SNMP trap will be shown.

Is there any way to replace the "|" character before OpsView is going to process the traps? Or is there any other way?

Thanks in advance for your advice.