Ask the Community
Groups
Monitor memory consumption of Traverse components (SNMP) - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION</strong></p> <p>How to monitor memory consumption of Traverse via SNMP?</p> <p><strong>RESOLUTION</strong></p> <p>To track the memory consumption of a Traverse component using SNMP, create an Advanced SNMP test with these parameters:</p> <ul><li>Navigate to Adminstration->Devices->Tests</li> <li>Select 'Create New Advanced Tests' (<strong>must be logged into the department or represented into the department)</strong> </li> <li>Check the box to select 'Advanced SNMP Test'</li> <li>Enter the following, replacing '<strong>xxxx</strong>' below with the Process ID (PID) of the component and replacing '<strong>COMPONENT NAME</strong>' with the component being used to monitor:</li> </ul><p>Test Name: <strong>COMPONENT NAME</strong> Process Memory<br>Interval: 5 min <br>Test Units: MB <br>SNMP OID: .1.3.6.1.2.1.25.5.1.1.2.<strong>xxxx</strong><br>Result Multiplier: 0.001 </p> <ul><li>Select the 'Provision Tests' button at the bottom of the page</li> </ul><p>One way to determine the PID from a command prompt on the Traverse server is to check the PID associated with a unique TCP port used by the component:</p> <p>netstat -ano | grep 9999 (netstat -anp | grep 9999 for Linux)</p> <p>where '9999' is a unique port number associated with the Traverse component. Example JMX ports used by Traverse components include:</p> <p>Web application: 7691 <br>Data Gathering Engine: 7692 <br>Message Handler: 7693 <br>Correlation & Summary Engine: 7696</p> <p>If using Linux, you may also run 'cat' on the component's .pid file to display the PID</p> <p>Web application: <TRAVERSE_HOME>/etc/webapp.pid<br>Data Gathering Engine: <TRAVERSE_HOME>/etc/monitor.pid<br>Message Handler: <TRAVERSE_HOME>/etc/msgsvr.pid<br>Correlation & Summary Engine: <TRAVERSE_HOME>/etc/cse.pid</p> <p> </p> <p><em><strong>Please note also that the Process ID will change each time the component is started, as such the SNMP OID will need to be updated each time the component is restarted.</strong></em></p> <p> </p> <p><strong>APPLIES TO </strong></p> <p>All versions of Traverse.</p> <p><strong>REFERENCE </strong></p> <p>None.</p> </article> </main>