Monitoring CPU, Memory, Disk Using SNMP
The monitors for CPU, Memory, and Disk Utilization are automatically associated for the devices based on the device template definitions. For instance, for Linux servers, the default template has SNMP-based monitors associated. So, all Linux servers will have SNMP-based resource monitors associated. You will see the dial graphs for these three resources in the device snapshot page if SNMP is enabled.
All the Server templates have the monitors defined for various host resources. By default, the CPU, Memory, and Disk Monitors are associated to the servers. The device snapshot page shows the values of these monitored resources with dial-graphs.
If you do not see these monitors associated to the devices, it could be due to any or all of the following reasons:
- These monitors are not present in the device template.
- SNMP is not enabled on the device. In such case, enable SNMP and add the monitors to the device once again.
- Incorrect SNMP credentials are associated. Check the credential details like the SNMP version, community string etc.
Steps to add the monitors to the device again:
- From the device snapshot page, select the Monitors tab.
- From the monitor types, select Performance Monitors.
- You will see the monitors displayed on the right if associated. Click Add Monitors link on the right.
- From the list of monitors, select the SNMP monitors for CPU, Memory, and Disk Utilization.
- You can also add other required monitors like Partition monitors etc.
- The selected monitors are associated to the device and the resources are monitored.
To check if the SNMP agent in the device returns response, try the following:
- Click the Test Monitor icon against any of the associated monitor names. It does a dynamic query to the device for the value of the selected resource, and show the data.
- Incase the agent does not respond, you see a message to this effect. Refer to the troubleshooting tips to resolve the issue.
As an alternative, you can monitor the non-SNMP Linux servers using CLI (telnet or SSH), or the non-SNMP Windows devices using WMI.