SolarWinds Web Performance Monitor (WPM) Player
This template assesses the status and overall performance of SolarWinds Web Performance Monitor (WPM) Player installed on the SAM server by using Windows Performance Counters.
WMI access to the target server. WinRM must be installed and properly configured on the target server.
Windows Administrator on the target server.
For details on monitors, see SAM Component Monitor Types.
Service: SolarWinds WPM Playback Player
This monitor returns the CPU and memory usage of the SolarWinds WPM Playback Player service. This service is responsible for the automatic playbacks of web transactions. This is the main part of WPM Player that receives and manages transactions that should be played. If this service is not running, no transactions are played.
Service: SolarWinds WPM Playback Player Proxy
This monitor returns the CPU and memory usage of SolarWinds WPM Playback Player Proxy service. This service is responsible for communication with active players.
SeUM Agent dropped queue items
This monitor returns how many requests were dropped because they were already in the queue. The agent has an internal queue that it uses for transaction playback requests that cannot be immediately executed because there are no free worker processes. If a transaction is in the queue and a new playback request for the same transaction arrives, it is dropped because the queue cannot contain duplicate requests.
If the number of dropped requests increases significantly, it usually means that the Player is not able to play transactions as fast as they are requested. You should remove some transactions from the Player.
This counter has the Count statistic as difference option enabled and will show the statistical difference from the last polling cycle.
SeUM Agent enqueued items
This monitor returns the number of requests that are currently in the queue. The agent has an internal queue that it uses for transaction playback requests that cannot be immediately executed because there are no free worker processes. The queue cannot contain duplicate requests. If the number of items in the queue is close to the number of transactions assigned to the Player, it usually means that the Player is close to its capacity and is not able to play transactions fast enough.
SeUM Agent requested playbacks
This monitor returns the number of playback requests that were sent to the Player since it started. If the counter is not changing, the Player is not receiving any playback requests. There may be issues with the central WPM server or connection.
Size of internal WPM Player database
This monitor returns the size of the internal WPM Player database used for storing playback requests, results and screenshots. Depending on the number and complexity of assigned transactions, this file can grow rather large. This file can be found here:
If the file size grows too large, (over 2GB for example), this may mean that the playback results are not correctly downloaded from the Player. This can happen if there is a slow network connection between the WPM server and the Player. If this is the case, this file will continue to grow because results are generated faster than they are downloaded from Player.
Errors in AgentService.log file
This monitor returns errors from the
AgentService.log. The returned values are as follows:
Total – This component monitor returns the total number of errors in the log file. The value returned should be as low as possible.
New – This component monitor returns the number of newly found error strings.
Last_Message – This component monitor returns the last error message and its position in the log file.
You must specify the correct arguments (path to
AgentService.logfile) for this monitored component in the Script Arguments field. By default it monitors:
Number of running WPM worker processes
This monitor returns the number of active WPM worker processes (
SolarWinds.SeUM.Agent.Worker.exe). This process usually runs in multiple instances and is responsible for the actual playback of transactions. SolarWinds WPM Playback Player service uses these processes to execute playbacks. The default number of these processes is 2 on main WPM server.