Performance Monitoring Check

If a system resource, such as a processor core or network device, is too busy to keep up with all of its requests, it becomes a system bottleneck that could increase the delay for subsequent requests.

For preventative maintenance, use the Performance Monitoring Check to identify bottlenecks or critical resources on your monitored devices. You can use the collected Performance Monitoring data when diagnosing problems, and to help you to build a system performance profile to identify an abnormal load.

Performance Monitoring is available from Linux Agent 0.8.0 onwards.

Performance Monitoring consists of five checks:

The Dashboard displays the average and maximum values of the performance counter over the last Agent cycle and where the average exceeds the specified threshold, configurable in the Agent, an Alert is generated.

All Performance Monitoring Check failures are indicated in the N-sight RMM DashboardNorth-pane under the performance_monitoring_icon icon and information on the particular check that failed is displayed in the lower pane.

The Performance Monitoring Gauge displaying the current status of the check is accessed through the clickable information line for the specific check.

The Performance and Bandwidth Monitoring History Reports show the results of Performance Monitoring or Bandwidth Monitoring checks, on an individual server, over the last 24 hours and last 8 days.

You can suppress check alerts until the Check failures exceed a configured number of consecutive failures. For more information, see Configure alert thresholds to suppress alerts.

Check configuration

The check is configured from the Dashboard or on the device. From Agent 2.0.6 Performance Monitoring Checks added during the agent installation process use the updated default threshold values introduced in Dashboard 2020.01.20.

Type of performance check Alert Threshold Default Thresholds (Agent)
From 2.0.6 Pre 2.0.6
Processor Utilization Alert if average utilization > 85% 70%
Processor Queue Length Alert if average queue length per core > 4 /Core 2 /Core
Memory Usage Alert if average available MB <

Alert if average pages per second >

Alert if average page file usage >

Alert if non-paged pool >

 500 MB

1000 /sec

80%

500MB

 10MB

20 /sec

70%

100MB
Network Interface Utilization Alert if average utilization > 40% 40%
Physical Disk Alert if average read queue length >

Alert if average write queue length >

Alert if average % disk time >

 4

4

85%

 2

2

50%

Check configuration

Add

  1. On the N-sight RMM Dashboard North-pane, select the device
  2. Go to the Checks tab
  3. Click Add Check
  4. Choose Add 247 > Performance Check

  5. Select the Type of performance check as well as Instance (where applicable) and configure the thresholds.

  6. To run an Automated Task when the Check fails choose Assign a Task after creating the Check
  7. Click OK to save and apply
  8. If you selected Assign a Task after creating the Check:
    1. Select the Automated Task script and select Next to configure. The following example is for Windows Automated Tasks. Other task options display for Linux and macOS devices.

    2. Enter any required Command Line parameters or Script parameters and select Next
    3. Set maximum permitted execution time for the script (optional)
    4. Select Finish to save and apply

Edit

  1. On the N-sight RMM Dashboard North-pane, select the device
  2. Go to the South-pane Checks tab
  3. Right-click the target Performance Monitoring Check and select Edit Check

    There are different Performance Monitoring Checks based on the type of performance check. For example, Performance Monitoring Check - Memory or Performance Monitoring Check - Processor Time.

  4. Edit the settings
  5. Click OK to save and apply

Delete

  1. On the N-sight RMM Dashboard North-pane, select the device
  2. Go to the South-pane Checks tab
  3. Right-click the target Performance Monitoring Check and select Delete Check
  4. Enter the password you used to sign into N-sight RMM to confirm removal
  5. Click OK to delete