I'm using CentOS OS with the following SNMP config.###### CPU load monitoring ########load 12 10 5monitor -r 60s -o laNames -o laErrMessage laTable laErrorFlag !=0When I increase the load (using stress tool), I don't see the trap (Trap ID .1.3.6.1.2.1.88.2.0.1) fired, even though the thresholds were breached. I was expecting to see the trap when system uptime shows the following.Every 2.0s: uptime                     Wed Aug  2 13:44:26 201713:44:26 up  3:31,  2 users,  load average: 57.69, 17.79, 14.44I also have Disk monitoring settings for which DISMAN_EVENT traps (Trap ID .1.3.6.1.2.1.88.2.0.1) are getting generated when the threshold is crossed.###### Disk monitoring ######disk / 10%disk /var 10%monitor -r 10s DiskAlmostFull dskPercent > 80monitor -r 10s DiskFull dskPercent > 95Hence, I'm not sure what I'm missing here. Any thoughts?
CentOs DISMAN-EVENT-MIB_mteTrigger not fired when average load thresholds are breached
linux;centos;cpu;snmp