Since Lansweeper version 7.2, the performance data of Linux computers can be scanned. This in addition to the already existing performance scanning feature for Windows computers, which was introduced in version 7.1. Performance scanning is the high interval scanning of specific assets to retrieve key resource usage information. Specifically, you can monitor the following resources and see them displayed in a Windows and Linux computer's Performance tabs: CPU, RAM, disks and network traffic. By default, performance data is only scanned for your Lansweeper server itself. For other client machines, performance counter scanning must be manually enabled, instructions for which can be found in this article.
For Windows computers, performance information is retrieved remotely through WMI (Windows Management Instrumentation), a management infrastructure built into Windows operating systems. For Linux computers, the
/proc/net/dev files are accessed and the
free commands are run. No Lansweeper software is needed on the Windows or Linux client machine whose data you want to scan.
Step 1: perform a successful agentless scan
Make sure your Windows and Linux computers have been successfully scanned without an agent at least once. Instructions for setting up scanning of Windows and Linux computers can be found below.
- Windows scanning requirements
- How to scan a Windows computer
- Linux scanning requirements
- How to scan a Linux computer
Step 2: configure cleanup options
Browse to the
Configuration\Server Options section of the web console. Lower the
Delete performance counter data after XX days setting as much as possible, in the
History Cleanup Options section of the page. Once you've configured performance scanning, this setting will determine how long the data is kept in the database. We recommend keeping the data only for as long as strictly required, to prevent unnecessary database growth.
Step 3: set up the scanning target for performance monitoring
Browse to the
Scanning\Performance Scanning section of the web console. Hit the
Add performance target button. By default, there will already be a target on the page to scan the performance information of your Lansweeper scanning server itself. Specify a name, target and interval. The minimum interval is hard coded at 5 minutes. If you choose an interval below 5 minutes, it will automatically default to 5 minutes.
Your target can be an
Selection. You can add any report, static group or dynamic group that contains any number of Windows and/or Linux assets. If you choose the selection option, the
Select Assets button will appear.
Afterwards simply wait. An initial performance scan of the specified machines is immediately run and any subsequent scans are automatically executed based on the schedule you configured. If you have multiple scanning servers, a Windows or Linux computer's performance scan is executed by the last scanning server that performed a general scan of the machine. When a performance scan is taking place, you can see the Windows or Linux computer in your scanning queue under
Step 4: view the performance monitoring results
View scanned data in the
Performance tab of your Windows and Linux computer webpages. Information on when the last performance scan was executed can also be found under this tab. Performance counter data includes processor, memory, hard drive and bandwidth usage. CPU and memory usage are scanned as percentages. Disk data includes (per disk and total) percentage of used disk space, disk reads per second, disk writes per second and disk transfers per second. Network interface data includes (per interface and in MB) network traffic received, network traffic sent and total network traffic.
The buttons at the top of each tab can be used to change the displayed time frame: 1 hour, 1 day, 1 week, 2 weeks or 1 month. Minimum, maximum and 95th percentile values are displayed for each resource as well. If you select a 1D or 1W view, an average value is calculated per hour and each hour is a data point. If you select a 2W or 1M view, an average value is calculated per day and each day is a data point. If a machine's performance data can temporarily not be scanned, because the machine is offline for instance, there will be a gap in the line graph for that time frame.