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 file can be found here: c:\ProgramData\SolarWinds\SeUM\Data\AgentStorage.s3db. Depending on the number and complexity of assigned transactions, this file can grow rather large. The size of the internal WPM Player database used for storing playback requests, results and screenshots. There may be issues with the central WPM server or connection. If the counter is not changing, the Player is not receiving any playback requests. The number of playback requests that were sent to the Player since it started. 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. The queue cannot contain duplicate requests. 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 number of requests that are currently in the queue. This counter has the Count statistic as difference option enabled and will show the statistical difference from the last polling cycle. You should remove some transactions from the Player. 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. 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. The number of requests that were dropped because they were already in the queue. This service is responsible for communication with active players. The CPU and memory usage of SolarWinds WPM Playback Player Proxy service. Service: SolarWinds WPM Playback Player Proxy If this service is not running, no transactions are played. This is the main part of WPM Player that receives and manages transactions that should be played. This service is responsible for the automatic playbacks of web transactions. The CPU and memory usage of the SolarWinds WPM Playback Player service.
Windows Administrator on the target server. WinRM must be installed and properly configured on the target server. To learn more about WPM, see the WPM documentation. This SAM application monitor template assesses the status and overall performance of SolarWinds Web Performance Monitor (WPM) Player installed on the SolarWinds Platform server by using Windows Performance Counters. SolarWinds Web Performance Monitor (WPM) Player
0 kommentar(er)
