SLSNMPAgent slow leak on 10.4 CU6 and reference value

242 views
0
1 Comment

Hello everyone,

could someone share a good threshold value for the SLSNMPAgent process to trigger the restart of the agent/s running 10.4 CU6 release?

Thank you,

Roberto.

Marieke Goethals [SLC] [DevOps Catalyst] Posted new comment 30th January 2025
Marieke Goethals [SLC] [DevOps Catalyst] commented

I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer (using the ✓ icon) to indicate that the question is resolved?

1 Answer

0
2.24K 0 Comments

Hi Roberto

This can be handled in the same way as described here: SLDataMiner leak on 10.4 CU6 and reference value - DataMiner Dojo (use SLSNMPAgent instead of SLDataMiner.)

SLSNMPAgent is also a 32bit process, however you'll want to check the nominal memory usage via the Microsoft Platform element > Task Manager > VM Size of SLSNMPAgent (over x months).
Knowing this nominal memory usage, you'll be able to configure the alarm template properly and create a correlation rule which uses those alarms.

Robin Devos [SLC] [DevOps Advocate] Answered question 5th November 2024