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. Such a resource would be thought of as critical to the performance of the system.

Performance Monitoring available from Linux Agent 0.8.0 onwards, may be used as a form of preventive maintenance to identify any bottlenecks or critical resources on the monitored devices - so the system can be fine tuned or upgraded - before they cause increased delays and other problems.

Through Performance Monitoring, data is obtained that may prove useful when diagnosing any problems as well as allow you to build a performance profile of the system which can be used to identify abnormal load.

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 Performance Monitoring check results on a device over the last 24 hours and 8 day.

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 performancecheck 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. OK to save and apply
  8. Where Assign a Task after creating the Check is selected:
    1. Select the script
    2. Click Next to configure
  9. Enter the Command Line parameters (if required)
  10. Set a Script timeout in the range 1 - 3600 seconds (default 120 seconds)
  11. Click Finish to save and apply

Edit

  1. On the N-sight RMM Dashboard North-pane, select the device
  2. Go to the Checks tab
  3. Select the target Performance Check
  4. From the Check drop-down
  5. Click Edit Check (also available from the Check's right-click menu)
  6. Configure the settings
  7. Click OK to save and apply

Delete

  1. On the N-sight RMM Dashboard North-pane, select the device
  2. Go to the Checks tab
  3. Select the target Performance Check
  4. From the Check drop-down
  5. Click Delete Check (also available from the Check's right-click menu)
  6. Enter the password you have logged into the Dashboard under to confirm removal
  7. Click OK to delete