Troubleshooting steps if some widgets do not show data

Troubleshooting steps if some widgets do not show data

Troubleshooting steps if some widgets do not show data
In the Network > Device Performance tab or Server-Agentless > Summary tabs, if you're unable to view values for CPU Utilization, Memory Utilization, or Hardware Details and are instead receiving a message "You can configure to view custom monitoring metrics," then this documentation can help.

If you've configured Performance Counters for CPU Utilization and Memory Utilization, you'll view that here. You can also configure to view Custom Monitoring Metrics for CPU Utilization, Memory Utilization, and Hardware Details by editing Device Templates. To do this:
  1. Click Network > Device Templates.
  2. In the Device Templates page, click the Edit icon under Action next to the template that needs to be edited.
  3. Once the Edit Device Template window pops-up, click Configure Custom Monitor Metrics.
  4. In the Custom Monitor Metrics window that pops up, choose the custom metrics for the performance counters of CPU Utilization, Memory Utilization, Manufacturer, Serial Number, and Model Name from the drop-down menu. You can also Test them before adding them.
    Note: CPU Utilization and Memory Utilization can only be numeric values while the rest can be either numeric or string.

  5. Click Save.
Testing custom monitor metrics
When you click Test against a particular metric, the Test Performance Counter screen will pop up. In that screen:
  1. Monitor Name: Choose a monitor name for which the performance counter has to be tested.
  2. Credential Name: Choose a suitable credential from the drop-down menu.
  3. Verify the SNMP OID and Type.
  4. Click Test.

You can view these configured values under the Device Performance tab (For Network: Network > your device > Device Performance | For Servers: Server-Agentless > your server > Summary) from the next poll.

    • Related Articles

    • Troubleshooting steps if the data collection stops for a network device

      Data collection issues could be due to any of the following reasons: The On-Premise Poller is Down. The Network Module is Disabled. The Network Module is Down or Initializing. The device hasn't been recently polled. Unable to fetch proper ...

    • Troubleshooting steps for On-Premise Poller

      Prerequisites and basic details: Prerequisites for installing On-Premise Poller Necessary ports to allow access to the installed On-Premise Poller How secure is On-Premise Poller Amount of bandwidth consumed by the On-Premise Poller software Adding ...

    • Troubleshooting steps when the Network Module does not start properly

      Follow the steps below to fix Network Module-related issues. If the issue is not resolved by the first step, try the subsequent steps until the issue is resolved. Step 1: Stop the On-Premise Poller and restart it with administrator or root ...

    • How secure is On-Premise Poller

      On-Premise Poller: Introduction On-Premise Poller, a lightweight agent, helps to monitor your internal network and resources behind a firewall or virtual private network (VPN). You can install On-Premise Poller in various branch offices within a ...

    • How to upgrade the Network Module to the latest version

      What's new Log4j upgraded to 2.17.2 PostgreSQL upgraded to 10.20 JRE version upgraded to Zulu 8.60.0.21 Why you should upgrade your Network Module The latest Network Module version has code-level enhancements that improve security and restrict ...