An issue has been addressed where the trap receiver process accumulated memory during execution of the Service Engine, when more than ~ 80 "agents" were configured.
An issue has been addressed where the trap receiver process accumulated memory during execution of the Service Engine, when more than ~ 80 "agents" were configured.
By killing the zenSnmpTrapSrv service right after start, the behaviour doesnt happen anymore. For our customer this workaround is sufficient for now, but a fix in form of a build update is desired.