KBI 312082 Issue Addressed: High CPU Usage When Monitoring SNMP Trap Messages


Argent Omega 2.2A-2307-A and earlier


Sunday, 17 September 2023


CPU usage can spike constantly when running Relators with SNMP Trap Rule. It is especially obvious with a busy network with more than a hundred SNMP Trap messages received every minute.

The issue has been addressed in Argent Omega 2.2A-2307-B.

Technical Background

Argent Omega Generator collects SNMP Trap messages and saves SNMP subfolder.

In Argent Omega 2.2A-2307-A or earlier, all messages go to a single file. As results, the file can grow significantly large during the cause.

By default, it rolls over every 5 Megabytes.
When Argent Omega runs SNMP Trap Rule, it scans the files to pick up matching messages.

When there are many of the files and file sizes are large, the scanning performance deteriorates.

Argent Omega earlier version also has a coding error that can throw exception when the network device has been up for a long time. As results, Argent Omega Generator has to re-scan the files from beginning each time.

All these are added up and cause high CPU usage.

Argent Omega 2.2A-2307-B has been enhanced to address the issue.

First, subfolders under SNMP are created, one for each network device. As results, significant smaller amount of files is needed to scan.

Second, Argent Omega Generator keeps track of what has been scanned. As results, only new trap messages are scanned each time.


Upgrade to Argent Omega 2.2A-2307-B (Build: 2.2.2309.14) or later