SNMP Trap scripting options

A common misconception is that you lose performance because of the use of scripting languages like Ruby or VBScript for trap scripting. You should note that there are two parts to the solution.

1. A high performance native C++ server that receives, processes, and buffers traps.
2. Your script that post processes these traps and does what you want with them.

What happens when they arrive too fast 

Even bursts of over 2000 traps per second can be handles without dropping anything by the server on commodity hardware. The script could be much slower but that just means they will take some time to catch up. That is acceptable in almost all cases.

Do you want to handle storage ?

The Unbrowse SNMP server can store the traps for you in a format called VOTRP. You can open files save in this format from the Unbrowse User Interface and work with them. This is called the "NewDatabase" mode.

If you want to store the traps yourself in a SQL database or some other type of storage (eg, splunk) you can arrange for the Unbrowse server to merely act as a memory buffer for traps. You can then write scripts to process traps and then delete them. This is called the "BufferDatabase" mode.

The following pictures explain the outline of the script for the two storage modes.