ADMINISTRATOR GUIDE
Web Performance Monitor
Version 2.2
Last Updated: Monday, December 11, 2017
Retrieve the latest version from: https://support.solarwinds.com/Success_Center/Web_Performance_Monitor_(WPM)/WPM_Documentation Copyright © 2015 SolarWinds Worldwide, LLC. All rights reserved worldwide.
No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SOLARWINDS, the SOLARWINDS & Design, ipMonitor, LANsurveyor, Orion, and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies. Microsoft®, Windows®, and SQL Server® are registered trademarks of Microsoft Corporation in the United States and/or other countries.
Version: 2.2 February 24, 2015
page 2 Table of Contents
Introduction 11
WPM and Orion 11
WPM glossary 11
Installing WPM 13
Installing the WPM Server and Web Console 13
Server hardware requirements 13
Server software requirements 13
SQL database server requirements 15
Requirements for virtual machines and servers 16
Additional required components 17
Antivirus directory exclusions 17
Installation procedure 18
Completing the configuration wizard 19
Licensing 21
Maintaining licenses 21
Installing the Recorder 22
Recorder requirements 23
Configuring settings 23
Recorder login fields and options 24
Installing the Player 24
Recommended Player Requirements 24
Minimum player requirements 25
Configuring settings 26
Server initiated communication fields 27
Player communication type 27
page 3 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Deploying the Player remotely 27
Accounts and security requirements 27
Requirements for open ports 27
Supported OS and IE requirements 27
Upgrading Players 28
Additional poller and web site 28
Recording Sequences 29
Creating recordings 29
Running the Recorder for the first time 29
Common recording actions 29
Text matching 30
Creating a recording 31
XY Capture Mode 33
Downloading 34
Downloading checkbox options 35
Image verification 35
Stopping and saving a recording 36
Testing the recording 36
Exporting a recording 37
Managing recordings 37
Importing recordings 39
Exporting recordings 39
Deleting recordings 40
Disabling Windows authentication 40
Step duration calculations 41
Transactions 42
Creating Transactions 42
Good Playback Locations 42
page 4 Cloud Portals 42
Creating a Transaction 43
Adding a location 43
Managing playback locations 45
Failover and the WPM Player 46
What is a proxy? 46
Proxy per location 46
Proxy per transaction 47
Proxy authentication 47
Active Directory authentication against proxy 47
Thresholds 48
Adjusting thresholds for network latency 48
Importing recordings as transactions 48
Adding transactions in Discovery Central 49
Grouping related transactions, transaction steps or locations 49
Managing transactions 49
Managing transactions through the Web Console 50
Managing transactions with the Unmanage Scheduling Utility 50
Transactions and dependencies 52
Creating dependencies when adding a transaction 53
Editing transaction and transaction step dependencies 53
Creating dependencies on the Manage Dependencies page 54
Monitoring your transactions 55
The Transactions Summary views 55
Transaction Summary View 56
Transaction Details 56
Step Details 57
Location Details 58
page 5 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Active Transaction/Step/Location Alerts 58
Available customization 58
All Locations 59
Available Customization 59
All Transactions 59
Available customization 60
Current Screenshot 60
Available customization 61
Current Screenshot of Steps 61
Available Customization 61
Duration - Radial Gauge 61
Available customization 61
Last XX Events 62
Available customization 62
Location Details 62
Available customization 63
Min/Max Average Duration 63
Zooming 63
Available customization 63
Page Elements Overview 63
Available customization 64
Player Load Percentage 64
Zooming 64
Available customization 64
Requests with Issues 64
Available customization 65
Recording Custom Properties 65
Available customization 65
page 6 Screenshots of Last XX Failures 65
Available customization 66
Screenshots of Last XX Step Failures 66
Available customization 66
Step Application Dependencies 66
Available customization 66
Step Availability 67
Zooming 67
Available customization 67
Step Details 67
Available customization 68
Step Duration 68
Zooming 69
Available customization 69
Step Node Dependencies 69
Available customization 69
Steps by Status 69
Available customization 70
TCP Waterfall Chart 70
Available customization 71
Top XX Locations by Duration 71
Zooming 71
Available customization 71
Top XX Steps by Duration 72
Available customization 72
Top XX Transactions by Duration 72
Zooming 73
Available customization 73
page 7 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Transaction Availability 73
Zooming 73
Available customization 73
Transaction Application Dependencies 74
Available customization 74
Transaction Custom Properties 74
Available customization 74
Transaction Details 74
Available customization 75
Transaction Health Overview 75
Available customization 75
Transaction Node Dependencies 76
Available customization 76
Transactions by Status 76
Available customization 77
Solutions 78
The AppStack Environment 79
Introduction to the AppStack Environment View 79
The AppStack Environment View Analogy 79
The AppStack Environment View 82
AppStack categories and data 84
Understanding AppStack 86
Understanding status and colors 86
Understanding Quick Links 87
Understanding Categories 89
Understanding the Overview Bar 90
Understanding filtering options 90
Understanding filter properties 91
page 8 Understanding layouts 93
Hiding objects with "up" status 95
Understanding the AppStack resource 95
Navigating to AppStack 96
Using AppStack 97
Customizing the AppStack Environment View 99
Adding AppStack to a NOC View 101
Custom properties 104
Alerts and WPM 106
Creating alerts 106
Viewing alerts 107
Acknowledging alerts 107
Adding alert resources to a view 107
WPM Reports 109
Appendices 110
Troubleshooting and Diagnostics 110
Common debugging scenarios 110
Issues with JavaScript 110
Keyboard input does not work 110
Links do not work 110
Recorder hangs or becomes unresponsive 111
Element not found during playback error 111
Troubleshooting XY capture mode 111
Status icons 111
Status indicators 111
Status rollup mode 113
WPM alert variables 114
WPM transaction alert variables 115
page 9 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
WPM transaction step alert variables 117
WPM step request alert variables 121
WPM player location alert variables 127
page 10 Introduction
Web performance monitoring provides you with an accurate sampling of your web sites and services from the viewpoint of your users/customers. SolarWinds' web performance monitor (WPM) actively monitors web transactions from the end user's point-of-view without requiring the use of agents, and provides intuitive user experience testing with dashboards to display alerts and graphs for websites on both sides of the firewall. You can drill into load times, user experience for complete transactions, page load speed by location, heaviest page elements, waterfall charts, and images not displaying as intended. WPM and Orion
WPM shares the Orion core engine with other SolarWinds products such as Server and Application Monitor (SAM), Net Performance Monitor (NPM), etc. Some features and functions within WPM are also shared. Therefore, features and functions in WPM may appear to be available when they are not. These features and functions are not utilized by WPM as a standalone product.
WPM glossary
Here is a list of fundamental terms used within this product with which you should be familiar:
Action An action is considered a single event within a recording. An action can be, but is not limited to, text input into a field, a mouse click, a download, and so on.
Managed A managed transaction is a transaction currently assigned to a location and actively Transaction reporting statistics to the web console. Managed transactions count against your license.
page 11 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Player The Player is a Windows service simulating an end-user by playing back the steps of your transaction recordings. The results and timings are then reported back to the WPM Web Console, where the information can be viewed in various transaction resources. By installing the Player on remote computer systems, you form a cloud of Players that can sample the typical experiences of end-users in various locations around the world.
Recorder The Recorder is a Windows program that records web browser steps as your perform them to simulate the typical steps taken by end-users. Typical actions recorded include mouse clicks, text input, file downloads, and matching text strings and images.
Recording A recording is a series of navigational steps that are recorded. Once assigned to a location for playback, a recording becomes a transaction. A recording, in and of itself, does not count against your license.
Step A step is a collection of actions within a transaction. For example, the actions required to navigate to a specific URL make up one step.
Transaction A transaction is a recording of web browser steps assigned to a specific location. An assigned recording, or transaction, counts against your license.
Unmanaged An unmanaged transaction is a transaction that is currently assigned to a specific location, Transaction but is purposely inactive and does not report statistics to the web console. When a transaction is unmanaged, the historical data is retained. Unmanaged transactions count against your license.
WPM Server The Web Console lets you play back your transactions on a schedule with intervals as short and Web as one minute. The Web Console also lets you set thresholds on any step in a transaction Console when played back. These thresholds allow the WPM server to compare results and timings and warn you if a transaction indicates your end-users are experiencing service delays.
page 12 Installing WPM
WPM provides separate installers for Server, Recorder, and Player components. Installing the Server also installs local copies of the Recorder and Player. You can then install additional copies of the Recorder and Player on other computers as needed. Installing the WPM Server and Web Console
WPM uses a simple wizard-driven interface for the installation process.
Downgrades of SolarWinds products are not supported. If you are upgrading or installing multiple SolarWinds products, confirm that you are installing them in the order given in the upgrade instructions located in your SolarWinds Customer Portal.
SERVER HARDWARE REQUIREMENTS
The following table lists the minimum software requirements and recommendations:
HARDWARE REQUIREMENTS
Hard Drive 20 GB
Memory 3 GB
CPU 3 GHz dual-processor, dual-core is recommended.
SERVER SOFTWARE REQUIREMENTS
The following table lists the minimum software requirements and recommendations:
S REQUIREMENTS OFTWARE
Operating l Windows Server 2003 R2 SP2 (32-bit & 64-bit) Systems l Windows Server 2008, 2008 SP2, 2008 R2, and 2008 R2 SP1
l Windows Server 2012 and 2012 R2
Supported operating system languages:
l English (US and UK)
l German
l Japanese
page 13 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
S REQUIREMENTS OFTWARE
l Simplified Chinese
FIPS compliant/compatible and UAC features are supported.
IIS and MSMQ must be installed. SolarWinds recommends that SolarWinds administrators have local administrator privileges to ensure full functionality of local SolarWinds tools. Accounts limited to use of the SolarWinds Web Console do not require administrator privileges.
SolarWinds supports evaluation installations on Windows 7, Windows 7 SP1, Windows 8 (except Win 8 Standard edition), and Windows 8.1 (except Win 8.1 Standard edition). SolarWinds does not support production installations of SolarWinds products on Windows 7.
Both the WPM Player and Recorder support Windows 8 and Windows 2012.
TCP/IP l 80 (TCP) open for http traffic Ports l 443 (TCP) open for https traffic
l 17777 (TCP) open for SolarWinds traffic
l 17782 (TCP) open for player-initiated communications mode
Web Microsoft IIS, version 6.0 and higher, in 32-bit mode. Server DNS specifications require that hostnames be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed. For more information, see RFC 952.
Warning: The following Windows accounts, as configured by IIS 6.0 on Windows Server 2003 with their default security settings, are required:
l IUSR_
l IWAM_
Disabling these accounts or changing any default settings of these accounts may negatively affect the operation of your SolarWinds installation. SolarWinds strongly recommends against altering these accounts or their settings.
SolarWinds neither recommends nor supports the installation of any WPM product on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.
page 14 S REQUIREMENTS OFTWARE
.NET .NET Framework 3.5 SP1 through 4.0.3 Framework
Web l Microsoft Internet Explorer 8, 9, 10, and 11 Console l Mozilla Firefox, latest two versions at time of shipping Browser l Google Chrome, latest two versions at time of shipping
SQL DATABASE SERVER REQUIREMENTS
The following table lists the software and hardware requirements for the SolarWinds database server.
R REQUIREMENTS ESOURCE
Microsoft SQL server versions: SQL Server Version l SQL Server 2005 SP4 l SQL 2008 without SP, 2008 SP1, 2008 SP2, 2008 SP3
l SQL 2008 R2 without SP, 2008 R2 SP1, 2008 R2 SP2
l SQL 2012, SQL 2012 SP1 (also with AlwaysOn Availability Groups)
l SQL 2014 (also with AlwaysOn Availability Groups)
SQL server collations:
l English with collation setting SQL_Latin1_General_CP1_CI_AS
l English with collation setting SQL_Latin1_General_CP1_CS_AS
l German with collation setting German_PhoneBook_CI_AS
l Japanese with collation setting Japanese_CI_AS
l Simplified Chinese with collation setting Chinese_PRC_CI_AS
SQL version in FullWithSQL package:
l MS SQL server 2008 R2 SP1 - Express Edition
Notes:
l SQL Server Express Edition 3.5 SP2 is only supported for SolarWinds evaluations.
page 15 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
R REQUIREMENTS ESOURCE
l Due to latency effects, SolarWinds does not recommend installing your SQL Server and your SolarWinds server or additional polling engine in different locations across a WAN. For more information, see the SolarWinds Knowledge Base article, Can I install my Orion server or Additional Polling Engine and my Orion database (SQL Server) in different locations across a WAN?
l Either mixed-mode or SQL authentication must be supported.
l If you are managing your SolarWinds database, SolarWinds recommends you install the SQL Server Management Studio component.
l If your SolarWinds WPM product installs SQL Server System CLR Types, a manual restart of the SQL Server service for your SolarWinds database is required.
l Use the following database select statement to check your SQL Server version, service pack or release level, and edition: select SERVERPROPERTY ('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
CPU Speed 2.0 GHz
Hard Drive 2 GB Space The SolarWinds installer needs at least 1GB on the drive where temporary Windows system or user variables are stored. Per Windows standards, some common files may need to be installed on your server operating system drive.
Memory 2 GB
.NET Version 4.0 .NET Framework is required. Framework
TCP/IP 1443 (TCP) open for remote SQL client access traffic. Ports
REQUIREMENTS FOR VIRTUAL MACHINES AND SERVERS
SolarWinds installations on VMware Virtual Machines and Microsoft Virtual Servers are fully supported if the following minimum requirements are met for each VM.
SolarWinds strongly recommends that you maintain your SQL Server database on a separate physical server.
page 16 VIRTUAL R REQUIREMENTS ESOURCE
CPU 2.0 GHz Speed
Allocated 2GB
Hard Due to intense I/O requirements, SQL Server should be hosted on a separate physical Drive server configured as RAID 1+0. RAID 5 is not recommended for the SQL Server hard Space drive.
Memory 3 GB
Network Each virtual machine on which SolarWinds is installed should have its own, dedicated Interface network interface card.
SolarWinds uses SNMP to monitor your network so if you are unable to dedicate a network interface card to your SolarWinds server, you may experience gaps in monitoring data due to the low priority generally assigned to SNMP traffic.
ADDITIONAL REQUIRED COMPONENTS
The following required x86 components are installed by the SolarWinds Installation Wizard if they are not found on your SolarWinds database server:
l SQL Server System Common Language Runtime (CLR) Types. SolarWinds products use secure SQL CLR stored procedures for selected, non-business data operations to improve overall performance.
l Microsoft SQL Server Native Client
l Microsoft SQL Server Management Objects ANTIVIRUS DIRECTORY EXCLUSIONS
To ensure that all Orion products have access to all required files, the following directories, listed by operating system, should be excluded from anti-virus protection:
l Do not exclude executable files
l C:\ is the default install volume
Windows Server 2003 and Windows XP:
l c:\Documents and Settings\All Users\Application Data\SolarWinds\
Windows Server 2007, Windows Vista, and Windows 2008:
page 17 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
l c:\ProgramData\SolarWinds\ INSTALLATION PROCEDURE
To avoid permissions issues, do not install on a domain controller.
1. Log on to your future WPM server as Windows administrator. 2. Navigate to your download location, and then launch the executable file. 3. If you are prompted to install requirements, click Install, and then complete the installation, including a reboot, if required.
l Downloading and installing Microsoft .NET Framework 3.5 SP1 may take more than 20 minutes, depending on your existing system configuration.
l If a reboot is required, click Install to resume installation after rebooting, and then click Next on the Welcome window. 4. If you want to use the SolarWinds Improvement Program to send anonymous data about your usage to SolarWinds, click Send data. 5. Review the Welcome text, and then click Next. 6. If the Setup Wizard detects that Microsoft Internet Information Services (IIS) is not installed, select Suspend installation to manually install IIS, click Finish, quit setup, and then install IIS. The Web Console requires that Microsoft IIS is installed on the WPM Server. If you do not install IIS at this point, you must install IIS later, and then configure a website for the Web Console to use.
7. If an IIS installation was required, launch the installer again, and then click Next on the Welcome window. A server reboot may be required after installing IIS.
8. Accept the terms of the license agreement, and then click Next. 9. If you want to install WPM in a destination folder other than the default given, click Browse, select the required installation folder, and then click OK. 10. Click Next on the Choose Destination Location window. 11. Confirm the current installation settings, and then click Next on the Start Copying Files window. 12. Click Finish when the Setup Wizard completes. 13. If you are evaluating WPM, click Continue Evaluation. 14. If you are installing a production version of WPM, click Enter Licensing Information, and then complete the following procedure to license your WPM installation: a. If you have both an activation key and access to the Internet, select the first option, I have Internet access and an activation key..., enter your Activation Key, and then click Next. If you are using a proxy server to access the Internet, check I access the Internet through a proxy server, and then provide the Proxy address and Port.
page 18 b. If you do not have access to the Internet from your designated WPM server, select This server does not have Internet access..., click Next, and then complete the steps provided.
COMPLETING THE CONFIGURATION WIZARD
Using the Configuration Wizard, the following procedure completes and configures your WPM installation.
l Confirm that you have designated a SQL server database instance for WPM.
l Confirm that the Internet Information Services (IIS) Manager is not open while the Configuration Wizard is running.
l SolarWinds recommends that you close any and all browsing sessions that may be open to the web console before starting the Configuration Wizard.
l During configuration, the SolarWinds polling engine will shut down temporarily with the result that, if you are actively polling, you may lose some polling data. SolarWinds recommends that you perform upgrades during off-peak hours of network usage to minimize the impact of this temporary polling stoppage.
Configuring WPM:
1. If the Configuration Wizard has not loaded automatically, click Start > All Programs > SolarWinds Orion > Configuration and Auto-Discovery > Configuration Wizard. 2. Click Next on the Welcome dialog of the Configuration Wizard. 3. If you are prompted to stop services, click Yes. To ensure that all updates and changes are installed correctly, you must stop all services.
4. Specify the SQL Server instance to store network data.
l If you are using SQL Express, specify your instance as (local) and use a strong password. For more information about authentication with strong passwords, see http://msdn.microsoft.com/ms143705.aspx. SolarWinds recommends against the use of SQL Express in production environments due to inherent limitations.
l The selected instance must support mixed-mode or SQL authentication with strong passwords. A strong password must meet at least three of the following four criteria: o Contains at least one uppercase letter. o Contains at least one lowercase letter. o Contains at least one number. o Contains at least one non-alphanumeric character, e.g., #, %, or ^. 5. Provide credentials, if required, to log into the selected instance.
l In general, SolarWinds recommends using SQL Server Authentication to ensure that the WPM server can always access the SQL Server, even when it is hosted remotely on a separate server.
l If you are using an existing database, the user account needs only to be in the db_owner database role for the existing database
page 19 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
l If you are using an existing SQL account, the user account needs only to be in the db_owner database role for the SolarWinds database
l If you are creating a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the sa user account are always members of dbcreator
l If you are creating a new SQL account, the user account must be a member of the securityadmin server role
The sysadmin role and the sa user account are always members of securityadmin.
6. Click Next. 7. If you are creating a new database, select Create a new database, provide a name for the new database, and then click Next. SolarWinds recommends using only alphanumeric characters (abc, 123) in database names.
8. If you are using an existing database, select Use an existing database, type the database name or select it from the list, and then click Next. 9. If you want to create a new SQL account for the polling engine and Web Console to use for accessing the database, select Create a new account, provide an account name and password, confirm the account password, and then click Next. 10. If you want to use an existing SQL account to provide database access to the polling engine and Web Console, select the existing account, provide the appropriate password, and then click Next. 11. If you need to specify a particular IP address for the SolarWinds Web Console, provide the IP address of the host web server. SolarWinds recommends the default of All Unassigned, unless your environment requires a specific IP address for your SolarWinds Web Console.
12. Specify both the Port through which you want to access the Web Console and the Website Root Directory into which you want to install Web Console files. If you specify any port other than 80, you must include that port in the URL used to access the Web Console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the Web Console is http://192.168.0.3:8080.
13. If you want to enable automatic login using Windows Authentication, select Yes - Enable automatic login using Windows Authentication. Manual login using Windows Authentication is always available, regardless of whether or not automatic login is enabled.
14. Click Next. 15. If you are prompted to create a new directory, click Yes. 16. If you are prompted to create a new website, click Yes. Choosing to overwrite the existing website will not result in the deletion of any custom SolarWinds website settings you may have previously applied.
page 20 17. Confirm that all services you want to install are checked. Typically, all listed services should be selected for installation.
18. Click Next. 19. If you are prompted to disable the SNMP Trap Service and enable the SolarWinds Trap Service, click Yes to disable the Windows SNMP Trap Service and enable the SolarWinds Trap Service. 20. Review the final configuration items, and then click Next. 21. Click Next on the Completing the SolarWinds Configuration Wizard dialog. 22. Click Finish when the SolarWinds Configuration Wizard completes. 23. Log in to the SolarWinds Web Console as an administrator. Until you change your account, you can log in by using the User name, Admin without a password.
LICENSING
WPM is licensed by the total number of transactions that are implemented, regardless of whether or not these transactions are managed or unmanaged. The number of licenses used is calculated by multiplying the number of recordings by the number of locations assigned.
For example:
l 5 transactions at 1 location = 5 licenses
l 5 transactions at 3 locations = 15 licenses
LICENSE TIER IMPLEMENTED TRANSACTIONS LICENSE
WPM5 5 License with 1st-Year maintenance
WPM10 10 License with 1st-Year maintenance
WPM20 20 License with 1st-Year maintenance
WPM50 50 License with 1st-Year maintenance
WPM100 100 License with 1st-Year maintenance
WPM200 200 License with 1st-Year maintenance
WPMX Unlimited, standard playback rate License with 1st-Year maintenance
MAINTAINING LICENSES
SolarWinds License Manager is a free utility that allows you to easily migrate SolarWinds licenses from one computer to another without having to contact SolarWinds Customer Service. The following sections provide procedures for installing and using the License Manager:
page 21 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
INSTALLING THE LICENSE MANAGER
Install the License Manager on the computer where you currently have licensed SolarWinds products.
You must install the License Manager on a computer with the correct time. If the time on the computer is even slightly off from Greenwich Mean Time (GMT), you cannot reset licenses without contacting SolarWinds Customer Service. Time zone settings neither affect nor cause this issue.
Installing the License Manager:
1. Go to Start > All Programs > SolarWinds > SolarWinds License Manager Setup. 2. Click I Accept to accept the SolarWinds EULA. 3. If prompted to install the SolarWinds License Manager, click Install.
USING THE LICENSE MANAGER
You must run License Manager on the computer where the currently licensed SolarWinds product is installed before you can migrate licenses to a new installation. The following procedure deactivates currently installed licenses that can then be transferred to a new installation.
Deactivating Installed Licenses:
1. Go to Start > All Programs > SolarWinds > SolarWinds License Manager. 2. Check the products you want to deactivate on this computer, and then click Deactivate. 3. Specify your SolarWinds Customer ID and password when prompted, and then click Deactivate.
Once complete, deactivated licenses become available to activate on a new computer. When you have successfully deactivated your products, log on to the computer where you want to install your SolarWinds products and begin installation. When asked to specify your licenses, provide the appropriate information. The licenses you deactivated earlier are then assigned to the new installation. Installing the Recorder
The WPM Recorder is a Windows application that you can install on any computer that meets the following system requirements:
page 22 RECORDER REQUIREMENTS
RESOURCE REQUIREMENTS
CPU 1.0 GHz
Memory 2 GB
Operating System Microsoft Windows XP, Vista, 7, 8, 2012, Server 2003, Server 2008, Server 2012
TCP/IP Ports 80 (TCP) open for http traffic
443 (TCP) open for https traffic
17777 (TCP) open for SolarWinds traffic
Web Browser Internet Explorer 9 or higher
Due to a known issue in Internet Explorer 8, Recorder breaks when IE8 is used.
Installing the Recorder:
1. Run the TransactionRecorder.exe installer from your WPM package or download and run the TransactionRecorder.exe installer from the Web Console by navigating to: Settings > WPM Settings > Manage Recordings > Download recorder locally. 2. Follow the installer instructions. During installation, any required prerequisites such as .Net Framework 4 will also be installed.
CONFIGURING SETTINGS
When you run the Recorder, you are asked to specify the connection details of the WPM server. If you check the Remember Me checkbox, the connection details are saved for future Recorder sessions .
page 23 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
RECORDER LOGIN FIELDS AND OPTIONS
User name Enter your username to log into the WPM server. If you have not configured any additional WPM users, use the default user name of admin.
The SolarWinds WPM user selected must have WPM administrator rights to create and manage recordings. Users who are not WPM administrators should consider using the Work Offline mode.
You cannot use Active Directory authentication with the WPM recorder.
Password Enter the password associated with the username. If you have not configured any additional WPM users, leave the password of the admin user blank.
IP or Enter the IP address or the hostname of the WPM server. The administrator should be able hostname to provide this.
Remember Check this box to have the Recorder remember your credentials for future logins. me
Connect Click to connect to the WPM server and run the Recorder.
Work Click to run the Recorder offline. In offline mode, recordings cannot be saved or loaded to Offline the WPM server, but must instead be exported and imported to and from your local disk as (XML) .recording files.
To save an offline recording to the WPM server, you must use the WPM Web Console's Import function on the WPM Settings > Manage Recordings page.
If you have another Recorder available that can connect to the WPM server, import the file into that Recorder and then save it to the WPM server.
Once you have successfully logged in, or have chosen to work offline, the recorder is launched.
Installing the Player
The WPM Player is a Windows service that you can install on any computer that meets the system requirements. RECOMMENDED PLAYER REQUIREMENTS
The recommended requirements allow a single Player to monitor up to 50 transactions of 30-second duration at 5-minute intervals. The minimum is 1 minute.
page 24 RESOURCE REQUIREMENT
CPU 2.0 GHz Quadcore
Memory 3 GB
Operating System Microsoft Windows XP, Vista, 7, 8, Server 2003, Server 2008, or Server 2012
TCP/IP Ports 80 (TCP) open for http traffic
443 (TCP) open for https traffic
17777 (TCP) open for SolarWinds traffic
17781 (TCP) open for server-initiated communication mode
Web Browser Internet Explorer 8 or higher
MINIMUM PLAYER REQUIREMENTS
The minimum Player requirements allow up to two 30-second transactions to be monitored at 1-minute intervals.
The Player that is installed on the SolarWinds WPM server is configured to work as a minimum- resource player in the interest of conserving the system resources of your SolarWinds WPM server.
RESOURCE REQUIREMENT
CPU 2.0 GHz single core. Virtual Machine okay.
Memory 2 GB
Operating System Microsoft Windows XP, Vista, 7, Server 2003, Server 2008 or Server 2012.
TCP/IP Ports 80 (TCP) open for http traffic
443 (TCP) open for https traffic
17777 (TCP) open for SolarWinds traffic
17781 (TCP) open for server-initiated communication mode
Web Browser Internet Explorer 8 or higher
To avoid permissions issues, do not install on a domain controller.
Installing the Player: page 25 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
1. Run the PlaybackPlayer.exe installer from your WPM package or download and run the PlaybackPlayer.exe installer from the Web Console. The download link is located at Settings > WPM Settings > Manage Player Locations > Download player. 2. Follow the installer instructions. CONFIGURING SETTINGS
After installing the Player, you must configure its settings. Later on, you will copy these settings into your WPM server when you define your Playback locations so that the server knows how to connect and relay commands to this particular Player.
Configure the Player:
1. Click Start > All Programs > SolarWinds Orion > Web Performance Monitor > WPM > Playback Player Settings. The following screen appears:
page 26 SERVER INITIATED COMMUNICATION FIELDS
This default option waits for requests from the WPM server on a specified port. This requires firewall/NAT configurations on each player computer.
Player This is an optional password to protect against unauthorized connections to your Player. Password
Player This is the port the WPM server uses to connect to the Player. This port must be open on Port your Player firewall. This must be set to 17781.
PLAYER COMMUNICATION TYPE
WPM offers two choices of configuration setup for how the player communicates with the WPM player.
Server-initiated The server-initiated player is passive and waits for requests from the WPM server on a communication specified port. This requires firewall/NAT configurations on each Agent machine.
Player-initiated Selecting this option allows the player to actively initiate communication with the WPM communication server on port 17782. Firewall/NAT configuration is simplified because the active agent actively connects to the poller server using a HTTP(S) protocol. MSPs and larger distributed deployments may prefer this option.
DEPLOYING THE PLAYER REMOTELY
The following requirements must be met for remote deployment to be successful:
ACCOUNTS AND SECURITY REQUIREMENTS
l Accounts must have access to the remote administrator share
l Updated Root Certificates
l For Windows Vista Windows 7 computers in a workgroup, UAC must either be disabled or the built in Administrator account must be used for deployment REQUIREMENTS FOR OPEN PORTS
135 Microsoft EPMAP (DCE/RPC Locator service)
445 Microsoft-DS SMB file sharing
SUPPORTED OS AND IE REQUIREMENTS
l Windows Server 2003, Windows Server 2008, Windows Server 2012
l Internet Explorer 8, or higher
page 27 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
During the deployment process, all prerequisites will be installed automatically, (e.g. VC Redistributables, .NET Framework, and so on).
The remote machine may be restarted at the end of the deployment process.
Upgrading Players
Upgrading players simply requires you to install the new player over the previous version. The new player retains all information, self-registers and your current transactions begin to poll again.
If you uninstall players, transactions will go into a state of Unknown. Transactions are polled again when you install a new player on the same machine with the same settings. ADDITIONAL POLLER AND WEB SITE
If deploying WPM into an existing SolarWinds environment that uses additional pollers or web sites, you must update the existing additional pollers and web site using the files provided:
Additional Poller update:
l SolarWinds-WPM-v2.2-Poller.exe
Additional Web Console update:
l SolarWinds-WPM-v2.2-WebOnly.exe
page 28 Recording Sequences
This section discusses the following topics:
l How to record and save action sequences
l How to edit recorded action sequences Creating recordings
The Recorder window is split into two panes:
l The left-hand pane records your browser actions.
l The right-hand pane is the Time Line that shows you what actions have been recorded. It also allows you to edit your actions while still recording.
When a recording is being captured, a red box surrounds what is being recorded.
WPM does not record the contents of XML pages.
RUNNING THE RECORDER FOR THE FIRST TIME
l The Recorder uses the Internet Explorer settings including web proxy. The Recorder web browser uses the settings and security level of the Internet Explorer browser of the computer it is installed on.
l If your web site requires the browser to accept cookies, or if you need to connect to the Internet through a web proxy, these are settings you must make in Internet Explorer.
l If the security level of the browser is too high, the Recorder will ask for permission to lower the security settings to the recommended level.
l Disable browser integration for Adobe Acrobat Reader if it is installed. If it is installed, the recorder will prompt you to disable the browser integration type.
l If you use Internet Explorer 9.0, change the .zip Windows file association. Internet Explorer 9.0 handles .zip files in a manner that is incompatible with the Recorder. As a workaround, install a third-party .zip utility such as WinZip or 7zip to change the .zip file association. COMMON RECORDING ACTIONS
Depending on which action is enabled, you will see different options available in the recorder menu.
Menu during a recording:
page 29 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
1. Record 2. Stop 3. Add Wait Time 4. X, Y Capture Mode 5. Start Conditional Block 6. Text Verification 7. Image Verification 8. Image Verification with click sequence
Menu when recording is stopped:
1. Record 2. Play Recorded Sequence 3. Play Step-By-Step 4. Insert Wait Time 5. Insert Text Verification 6. Insert Image Verification TEXT MATCHING
Monitoring is not only about playing back sequences, but also about verifying that the results are what you expect. For example, after recording a login sequence, you may want to add a check on the next web page to find any text that says "Login successful," "Welcome," or some other keyword indicating that the login action was successful.
If the match is not successful, WPM will set the transaction status to Down. Typically, you want to make the text matching action the first action on the page that is loaded after logging in.
Setting a "Success means (a Page Contains Certain Text)" verification:
1. Click the text verification icon: . 2. Enter the text to search for in the Enter Text to Match box. 3. Click Page Contains Text. 4. Click OK.
You can also verify that a page does not contain certain text, for example, "Error" or "Not found".
Setting a "Success means (a Page Does not Contain Certain Text)" verification:
page 30 1. Click the text verification icon: . 2. Enter the text to search for in the Enter Text to Match box. 3. Click Page Does not Contain Text. 4. Click OK. CREATING A RECORDING
Creating a record is simple. Just start the recorder and perform the browser steps you would expect your user or customer to do. You can edit these at any point.
Starting the Recording:
1. Click Start > SolarWinds Orion > Web Performance Monitor > Recorder. Note: You be asked if you want to lower your security settings in order the run the recorder. 2. Enter the URL for the page from which you want to start recording, and press Enter or click OK. 3. Click Record and begin the sequence. All your browser actions are now recorded and listed in the Time Line pane on the right side of the Recorder, as shown below:
Making Corrections While Recording:
page 31 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
1. Click Undo as many times as necessary to step back through any incorrect actions in the Time Line. 2. Correct your mistakes by right-clicking the step in the Time Line, and selecting the appropriate menu option.
New steps can be added between two existing actions or at the end of the last step in the recording.
Adding Waits:
The default timeout threshold for pages is 30 seconds. If you need to specify a longer time to wait, you can insert a Wait command before or after a step. These Wait times are not included in the recorded time for the transactions.
1. Right-click on the step before or after which you want to insert a pause. 2. Select Insert Wait above or Insert Wait below. 3. Select the time to wait, and click OK.
Removing Unnecessary Actions in the Time Line:
1. Select the unnecessary action, and press the Delete key.
Correcting Errors in Text Field Actions:
page 32 1. Double-click the text field action in the Time Line pane.
2. Enter the corrected text in the Simple Text Input box, or enter the multi-variant text in the Multi- Variant Text Input box, and then click OK.
XY CAPTURE MODE
XY Capture Mode records the coordinates clicked within dynamic web pages. This applies to pages containing non-html elements, such as Flash and Silverlight based content. This feature works by starting a recording, then toggling on/off the XY mode as needed during a recording.
When you toggle on the XY Capture Mode, all mouse actions are converted from global coordinates to local browser coordinates and recorded. The Image Match action will then verify that the content is properly loaded before playback continues.
It is possible to add an Image Match into a recording after it has finished.
Configuring XY Capture Mode:
page 33 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
1. Start your recording. 2. Enable the XY Capture mode by clicking the coordinate's icon . 3. Mouse click on the page as needed.
4. Click Image Match and then drag your mouse over a region of the image. 5. On mouse-up, the Match Image button will appear asking you to confirm the image match. 6. Stop the recording by pressing Stop . 7. Verify that the recorded clicks and actions were successful by clicking Play . 8. If needed, edit from the timeline by right-clicking on a step.
l Actions are recorded at the user's speed. If you have an unnecessary delay in your recording, double-click on the recorded action and change the recorded delay to another value.
l Image Matching on animated objects is not recommended. During playback, animated objects may be in a different phase of animation, which will result in not being able to find the exact recorded image.
l Select small regions. Image Match actions are CPU intensive. Select only small regions or portions of the image to improve the performance of playback.
l Do not use the Recorder on screen resolutions greater than 1920 x 1200 pixels as operating system limitations do not allow the WPM Playback Player to function above this resolution.
l Image matching: as soon as the image is found on the page, the timer is stopped and the next step begins. Image matching time is measured and added to the overall step duration.
DOWNLOADING
If you download a file during your recording, the following dialog box appears:
page 34 DOWNLOADING CHECKBOX OPTIONS
Include download Check to include the time required to download the file in the overall time for time in statistic recording this step.
Stop download Check to stop the download when it reaches the specified file size. after specified size is downloaded Note: Due to a known issue, a navigation action is required between each "partial" download or else the transaction playback will stop playing correctly.
Verify name: Check to compare the names of the recorded filename against the actual filename being downloaded at the time of playback. If the names do not match, this transaction step will be considered Down.
Verify size Check to compare the size of the recorded downloaded file against the size of the file being downloaded at the time of playback. If the sizes do not match, this transaction step will be considered Down.
IMAGE VERIFICATION
WPM can perform image verifications during a recording. Image matches can also be used in conjunction with XY Capture mode to record non-html page elements. The page becomes grayed-out once Image Verification is enabled.
In XY Capture mode, select a small region on the page by holding down the left mouse button and dragging the mouse. Once you have the portion of the image captured, click the Match Image button which appears on mouse-up.
During playback, the image is matched. If the image is not found, the search is repeated until the defined time elapses.
Enabling Image Verification:
page 35 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
1. Click the Image Verification icon. 2. Click and hold the left mouse button while dragging the mouse to select the image to match. 3. Click the Match Button. 4. Verify the image in the picture and click OK. Allow for extra time if the image is dynamically generated. 5. Save the recording.
Enabling Image Verification with Click:
WPM allows you enable image verification (described above) with a click. This is useful if an image is attached with a hyperlink.
1. Click the Image Verification with click icon. 2. Click and hold the left mouse button while dragging the mouse to select the image to match. 3. Click the Match and Click Image button. 4. Verify the image in the picture and click OK. Allow for extra time if the image is dynamically generated. 5. Save the recording. STOPPING AND SAVING A RECORDING
When you have completed your action sequence, you need to stop, test and save it.
Stopping the Recording:
1. Click Stop .
TESTING THE RECORDING
You can play the entire recording or step through it. During the playback, the Player times how long it takes each steps to run. This information is used later to calculate typical timings for the recording.
The Recorder automatically tests the recording when you save it.
Playing the recording:
l Click Play . The recorder will play the entire sequence.
Playing the recording step-by-step:
page 36 l Click Step . The recorder will play the next action in the sequence and then pause. Repeat for each step.
Saving the Recording:
If you are connected to the WPM server, you can save your recordings directly to the server.
The Recorder automatically tests the recording by playing it back when you save it. The Recorder also presents you with the option to open the Web Console to create a transaction from your new recording.
Saving a Recording to the WPM server:
1. Click Save . 2. Enter the name of this recording in the Recording Name text box. 3. Click Save.
Saving Changes to a Recording:
l Click Save .
Saving Changes as a New WPM Recording:
1. Click File > Save As. 2. Enter the name of this recording in the Recording Name text box. 3. Click Save.
EXPORTING A RECORDING
If you are in offline mode, you can export your recordings to the local disk as a .recording file that you can later transfer and import into WPM.
1. Click File > Export. 2. To password-protect the recording: a. Click Yes. b. Enter the password in the Password and Confirm Password text fields. c. Click OK. 3. Enter the file name for the recording, and then click Save. (Saving creates an XML file.) MANAGING RECORDINGS
In the Web Console, the only change you can make to a recording is to change its name. However, the WPM Recorder enables you to make additional changes.
While you cannot add new browser actions, you can delete existing actions, change the text input of text field actions, and edit or insert new Match Content actions as required.
You must either save or export the recording to retain your changes.
page 37 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
If the recording you want to edit is on the WPM server, you must first load it into the Recorder.
Loading a Recording from the WPM Server:
1. Click Open . 2. Select the recording, and then click Open.
Deleting an Action:
1. Select the action. 2. Press the Delete key.
Changing the Text in Text Field Actions:
1. Double-click the text field action in the Time Line pane. 2. Enter the corrected text in the text box, and then click OK.
Changing the Text in Match Content Actions:
1. Double-click the Match Content action in the Time Line pane. 2. Enter the corrected text in the Enter text to match box, and then click OK.
Changing the Name of a Step or Insert a Step Below a Step:
l Right-click on a step in the timeline and make your selection from the popup menu.
Adding wait time to steps creates an artificial pause in the recording. To add wait time to a step:
page 38 1. Click Add Wait Time . 2. Edit the time as needed, and click OK.
IMPORTING RECORDINGS
In offline mode, you cannot retrieve recordings directly from the WPM server. You can, however, open any recordings that have been exported as .recording files.
1. To import a recording using the Web Transaction Recorder, click File > Import. 2. To import a recording using the Web Console, click Settings > WPM Settings > Manage Recordings. 3. Browse and select the .recording file, and then click Open 4. If the recording is password-protected, enter the password, and then click OK. EXPORTING RECORDINGS
It may not always be possible to establish a connection between the recorder and the WPM server. The way to transfer recordings between a remote recorder and the WPM server is to export the recordings to .recording files on the local disk, and to then transfer them to their destination using e-mail, FTP, or some other means.
Exporting a Recording:
1. Click File > Export. 2. Enter the file name for the recording, and then click Save.
Exporting a Recording from WPM Server.
1. Log on to the WPM Web Console. 2. Click the Web tab. 3. Click WPM Settings. 4. Click Manage Recordings.
page 39 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
5. Select the check box next to the recording and then click Export.
6. To password-protect the recording: a. Select Yes, password protect this recording. b. Enter the password in the Password and Confirm Password fields. 7. Click Export. 8. The web browser begins downloading your .recording file. It is saved under the name, NameOfRecording.recording. DELETING RECORDINGS
You can delete recordings from the Manage Recordings page of the Web Console. All transactions using the deleted recording will also be deleted.
1. Log on to the Web Console. 2. Click Settings > WPM Settings > . 3. Click Manage Recordings. 4. Select the check boxes next to the recording or recordings you want to delete. 5. Click Delete. DISABLING WINDOWS AUTHENTICATION
If you find that Players are having authentication problems when playing back recordings, check whether the recorded web site uses Windows authentication for its login process. Some computer systems are set up to pass-through Windows credentials without prompting for a username and password, and if you create a recording on such a computer, the username and password required for the web site will not be saved with the recording. This may result in an authentication problem when the recording is played back on a different computer.
To ensure that the Recorder always asks for a username and password for web sites protected by Windows authentication:
1. Run the recorder under a local user account instead of a domain account. 2. Uncheck Enable Integrated Windows Authentication on the Advanced tab of IE Internet Options settings. This option requires a restart of Internet Explorer.
page 40 STEP DURATION CALCULATIONS
The times taken for navigation to new page, file download, and image match / text match are all used in the calculation of step duration.
Ajax calls are not used in step duration calculations. For example, page content loaded dynamically by Ajax. To partially measure such dynamic behavior, you can use text match / image match, but the return of this method is not as precise as the return of direct request measurement.
page 41 Transactions
A transaction is a recording of web browser steps assigned to a specific location. However, transactions are more than just recordings and locations. A transaction can also be assigned customizable timing thresholds so that the WPM server alerts you if any transactions are taking longer to run than they should.
This chapter discusses the following topics:
l How to create transactions from your recordings
l How to register Players as playback locations
l How to find good locations for Player agents
l How to interpret transaction and step status
l How to link transactions statuses together Creating Transactions
Transactions are created in the Web Console. Every transaction requires:
l a recording, created using the Transaction Recorder and saved on the WPM server
l a Transaction Player that is installed on a computer GOOD PLAYBACK LOCATIONS
Web Performance Monitoring is used to get an accurate sampling of your web sites and services from the viewpoint of your users/customers. You should place WPM players in the same geographical locations as the majority of your users in order to get data that is truly representative.
Possible locations include:
l A server in a co-location hosting service
l A workstation in a satellite office
l A virtual machine hosted by a cloud computing service CLOUD PORTALS
WPM enables you to monitor transactions from locations around the world using a VM cloud instance. If you do not have your own infrastructure, consider renting servers from co-location hosts and or virtual machines from cloud computing services.
For help on using Amazon Cloud Services to host a player, see the SolarWinds Knowledgebase article: Using Amazon Cloud Services as a Playback Location.
page 42 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
CREATING A TRANSACTION
Selecting a recording and assigning it to a location:
1. Log into the Web Console. 2. Click the Web tab. 3. Click WPM Settings. 4. Click Add a Transaction Monitor. 5. Select the Recording Name for the recording you want to monitor, and then click Next.
l If you need to import the recording you want to monitor, click Import, browse to the file, and click Import. Then select and click Next. 6. Select the Location Name for the location where you want this recording to be played, and then click Next.
l If you need to add a location, see Adding a location.
When you have selected a recording and assigned it to a location, you can define the properties for the transaction.
Defining properties:
1. Enter a Description for the transaction. 2. Select the Playback interval to specify how frequently you want this transaction to be played. 3. Select the Thresholds for each step in the transaction. For more information, see Thresholds 4. To use a Proxy URL, click Advanced, and enter the proxy server address in the Proxy URL field. A proxy server acts as an intermediary for requests from clients. A proxy server passes requests and responses to the client application. For more information, see What is a proxy? 5. To enable screenshot capturing, click Advanced, and check Enabled. 6. Click Next.
Transaction status troubleshooting:
1. Advanced users can select the Improve transaction troubleshooting by associating nodes or applications to this web transaction, and add nodes and applications for transactions and steps. For further information, see Transactions and dependencies. 2. Click Save Monitor. 3. The transaction is now added to the Transaction Monitor list. 4. You can play the monitor immediately by selecting its checkbox and clicking Play now. ADDING A LOCATION
Locations are simply places on the web where you can install the WPM player. They need to be registered with the WPM server. Location information is displayed in the resources on the WPM Location view, particularly the Location Details resource.
page 43 1. From the Add Transaction - Location page, click Add Location. 2. Select the method of adding the location. You can add the location on your network, on the cloud, or use an existing location.
Adding a location on your network:
1. Select Install location on my network and click Next. 2. Either:
l Enter the IP Address or Hostname of the location, click Add to List.
Or:
l Select a location from the list of existing nodes.
You can select multiple locations if required.
3. Click Next. 4. Either:
l Select Use default settings, and enter a Player Name if you do not want it to be the same as the Location Name.
Or:
l Select Use advanced settings, and enter a Player Name, Player Port number, and Player Password, as required. 5. Click Next. 6. The location is shown with default credential. Here you have the option to:
l Click Assign Credentials, to open the Assign Credential window where you can choose an alternative credential, or click
l Click Test Credentials, to test the selected credential is valid. 7. Click Deploy Player, to use the selected credential. 8. The location is added to the list of locations. Select the location and click Next. The Defining properties: tab of the Add Transaction page is displayed.
Adding a location on the cloud:
1. Select Add a location in the cloud, and click Next. 2. Select the appropriate vendor from the list displayed, and then click Next. 3. Enter the Access key and Secret key for the cloud account. 4. Supply the information requested on the screen until the location is added. Since this depends upon the Cloud provider, you should refer to the help provided by the vendor.
For help on using Amazon Cloud Services to host a player, see the SolarWinds Knowledgebase
page 44 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
article: Using Amazon Cloud Services as a Playback Location.
5. Once the location has been added to the list of locations, you can select it and click Next. The Defining properties: tab of the Add Transaction page is displayed.
Using an existing location:
1. Select Add an existing location, and click Next. 2. Enter a name for the player in the Name for player at this location field. 3. To use server initiated communication, where the server-initiated player is passive and waits for requests from the WPM server on a specified port: a. Select Server initiated communication, and enter the IP Address or hostname where the player is located. b. Click Advanced if you need to add a Player Password, want to change the Player port from the default of 17781, and/or Use proxy. 4. To use player initiated communication, which allows the player to actively initiate communication with the WPM server on port 17782: a. Select Player initiated communication, and select the Player from the dropdown. b. Click Advanced, if you want to assign this player to a poller. Firewall/NAT configuration is simplified because the player actively connects to the poller server using a HTTP(S) protocol. MSPs and larger distributed deployments may prefer this option.
5. Click Submit. 6. Once the location has been added to the list of locations, you can select it and click Next. The Defining properties: tab of the Add Transaction page is displayed.
MANAGING PLAYBACK LOCATIONS
The Manage Transaction Locations page lets you add, edit, and delete playback locations.
Opening the Managing Playback Locations Page:
1. Log in to the Web Console. 2. Click the Web tab. 3. Click Web Settings. 4. Click Manage Player Locations.
page 45 5. Hover over a Location Name to see the Location tool tip, or click the location to see the Location Details view.
FAILOVER AND THE WPM PLAYER
On failover, the WPM Player continues to point to the primary Orion server, and communication fails. When this occurs, you must switch back to the primary computer to regain player function. WHAT IS A PROXY?
A proxy server acts as an intermediary for requests from clients. A proxy server passes requests and responses to the client application.
PROXY PER LOCATION
You can set your WPM server to communicate with a player location through a proxy server from the Edit Transaction Location page, as shown below:
Enter a URL for the Proxy Server used to connect the WPM server to the WPM remote player's location.
You can update remote player passwords and ports by editing the location details page:
Select a location to edit and then select Update player settings.
page 46 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
PROXY PER TRANSACTION
You can set your transactions to be played using a connection through a proxy server. A player location uses the proxy setting to connect to the remote website that has to be monitored.
The group policy Proxy Settings per User must be allowed for transaction proxies to work. This is allowed by default on the computer where the WPM player is running. Use the following steps to check whether or not the settings are correct:
1. Run Gpedit.msc 2. In the left pane, expand Computer Configuration > Administrative Templates > Windows Components. 3. Select Internet Explorer. 4. In the right pane, double-click Make proxy settings per-machine (rather than per-user). 5. Select Disabled and then click OK. 6. Run Gpupdate /force. 7. Restart the WPM player service.
PROXY AUTHENTICATION
Proxy credentials cannot be provided on the Transaction Settings page. Credentials must be captured in the recording. Only the proxy URL can be set on the Transaction Settings page.
To ensure that the recorder always prompts for a username and password for sites behind a proxy that requires authentication, take the following steps:
1. Run the recorder under a local user account instead of a domain account. 2. Disable integrated Windows Authentication Internet Explorer's settings. Note: This requires a restart of Internet Explorer.
More detailed information can be found in the following KB article: Windows Authentication problems when playing back a recording.
Credentials do not need to be captured in the recording if the player is using Active Directory accounts for worker processes, but these accounts must have permission to access the proxy.
ACTIVE DIRECTORY AUTHENTICATION AGAINST PROXY
Using this method, credentials are not required to be included in recordings.
In order for this to be possible, the player location worker processes must use domain accounts. Also, Integrated Windows Authentication must be enabled on the remote website.
To enable domain accounts for player worker processes, you must manually configure the SolarWinds.SEUM.Agent.Service.exe configuration file in the WPM player installation folder.
page 47 A transaction with proxy settings employed can be played on any of the available workers. All of the accounts used for worker processes must be allowed access to the proxy.
THRESHOLDS
The default threshold timing values for a transaction are based on the step timings measured when a recording was saved:
l Typical Value: the initial step timing
l Warning: Twice the initial step timing
l Critical: Four times the initial step timing
The Warning and Critical thresholds are used to trigger alerts. The Typical Value is plotted as a benchmark on resource charts that you can use to compare with actual timings.
You can change the default values if required.
1. From the Home tab, navigate to Home. 2. Click a transaction in the All Transactions group. 3. Click Edit on the Management line.
The Edit Transaction Monitor page is displayed, where you can edit the thresholds.
ADJUSTING THRESHOLDS FOR NETWORK LATENCY
There may be a need to set different timing thresholds for transactions that are played back from drastically different geographical locations.
For example: If you use a recording to create a transaction that will play back on a Player that is 100 miles away from the original recording location, the default threshold timings are probably sensible. However, if the Player is 2,000 miles away, you will need to raise the timing thresholds to account for the added network latency.
Thresholds are not required to create a transaction.
IMPORTING RECORDINGS AS TRANSACTIONS
To add a recording that cannot connect to the WPM server, you must export the recording from the Recorder as a .recording file and then transfer it to a computer that can access the WPM Web Console. Transfer the file by e-mail, FTP, Flash Drive, or some other method.
page 48 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
After transferring the .recording file, you can use the Import command on the Add Transaction page to add the recording to the WPM server. ADDING TRANSACTIONS IN DISCOVERY CENTRAL
Discovery Central provides an alternative method of setting up transactions. Navigate to Settings > Discovery Central and follow the instructions shown under Adding Transactions in Discovery Central. GROUPING RELATED TRANSACTIONS, TRANSACTION STEPS OR LOCATIONS
Groups give you the ability to logically organize monitored objects, regardless of device type or location for alerting or reporting purposes. Groups can contain any SolarWinds objects that report a status, including transactions and even other groups. You create, delete, and modify groups from the Manage Groups page.
Nesting a group within another does not create a strict parent/child relationship. You can include any group as a member in any number of other groups.
1. Log on to the web console. 2. Click Settings in the top right of the web console. 3. Click Manage Groups in the Node & Group Management grouping of the Website Administration page. 4. Click Add New Group. 5. Enter a Name and Description for the transaction group. 6. Select Transactions from the Show Only dropdown, and select [No Grouping] from the Group by dropdown. 7. Check the transactions to be added to the group.
you can use the same procedure for creating groups of Transaction Steps or Player Locations by changing the selection made in step 6.
For further information on using the Manage Groups settings, please see the Managing Groups and Dependencies chapter of the Orion Common Components Administrator Guide. Managing transactions
You may want your transactions to be played only at certain times for any number of reasons, including avoiding scheduled maintenance, retrieving data only for normal business hours, and so on. When transactions are stopped, you are not be alerted when transactions fail and you will not have down time associated with scheduled maintenance.
You can manage your transactions via the Web Console as needed, or on a regular schedule using the SolarWinds Unmanage Scheduling Utility. By unmanaging a transaction, you stop its playback. Remanaging a transaction reenables transaction playback.
page 49 MANAGING TRANSACTIONS THROUGH THE WEB CONSOLE
Managing transactions from the web console is recommended if you need to stop a playback immediately or for a single occurrence. For transactions to be stopped and started on a schedule, use the Unmanage Scheduling Utility.
From the web console, navigate to Settings > WPM Settings > Manage Transaction Monitors to be taken to the following page:
Stopping a transaction from being played:
1. Select the transaction by checking the box next to the transaction name. 2. Click Unmanage. 3. From the dialog box, choose the time period for the transaction to be stopped. 4. Click OK.
Starting playback of a stopped transaction:
1. Select the unmanaged transaction by clicking the check box next to the transaction name. 2. Click Remanage. MANAGING TRANSACTIONS WITH THE UNMANAGE SCHEDULING UTILITY
Starting and stopping transactions on a schedule is done using the Unmanage Scheduling Utility.
page 50 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
You must be an Administrator to schedule transactions to be stopped. To do so, in your user account, scroll to the bottom under WPM Settings and change from User to Administrator in the drop-down menu.
Scheduling transactions to be stopped:
1. To access the Unmanage Scheduling Utility, navigate to Start > All Programs > SolarWinds Orion > Advanced Features > Unmanage Scheduling Utility. 2. Select either Create New Task, or open an existing task by clicking Edit Existing Task. 3. Click Add Items. 4. If required, group your transactions by selecting a filter from the Group by drop-down menu. 5. Click on the Transactions tab. 6. Select the transactions you want to schedule to be unmanaged by checking the check boxes next to the transaction names. 7. Click Add. 8. Select the length of time you would like the selected transactions to be stopped. 9. Click OK. 10. Optionally, you can click Save Task to save these selections for future use.
page 51 Once you have selected transactions to be stopped on a schedule, those transactions will appear in the left pane of the following screen.
To view the details of a selected transaction's schedule, check its box and its details will appear in the Task Item Properties pane on the right.
From this view, you can change the settings of transaction's schedule by selecting a transaction and clicking Set Duration. Additionally, you can delete transactions from the unmanage schedule by selecting them and clicking Delete Checked Items.
It is possible to create a conflict of schedules if you choose the same transaction to be stopped using both the web console and the Unmanage Scheduling Utility with different durations.
Transactions and dependencies
The SolarWinds Orion Manage Dependencies feature enables you to associate objects in a parent-child relations that shows one object has a dependency on another. WPM lets you set dependencies on transaction steps as well as transactions, providing you with an increased level of granularity to isolate dependencies at the level of single browser actions.
For the purposes of Web Performance Monitoring, dependencies are useful in conjunction with NPM and SAM for tying nodes and applications to transactions and transaction steps to facilitate troubleshooting. This means that you can view the status of nodes and applications associated with a transaction or transaction step using the Transaction Application Dependencies, Transaction Node Dependencies, Step Application Dependencies and Step Node Dependencies resources in the Transaction Details and Step Details views to see how their performances are affecting the transaction or an individual step.
page 52 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Setting up dependencies can also be for avoiding unnecessary alerts from child objects when only the parent object is actually experiencing problems. For example, if you had 50 devices at a remote site connected to one server, you would not want to be swamped with 50 alert messages from these if the server went down. By specifying that each device is dependent on the server, these devices would be shown as Unreachable if the parent server went down, and any alerts triggered by Down status would therefore be suppressed for these devices.
There are two ways to set up dependencies:
l Creating dependencies when adding a transaction
l Creating dependencies on the Manage Dependencies page CREATING DEPENDENCIES WHEN ADDING A TRANSACTION
You can create dependencies between transactions and nodes or applications when setting up transactions.
1. Create a transaction, as described in Creating Transactions. 2. When you reach the Transaction status troubleshooting option, select Improve troubleshooting by associating nodes or applications to this web transaction. 3. Click Add nodes. 4. Select the node or nodes you want to associate with this transaction, and click Save. 5. Click Add applications. 6. Select the application or applications you want to associate with this transaction, and click Save. 7. If you want to add nodes and applications to individual steps in this transaction, click Set individual dependencies for steps. 8. Click Save Monitor. 9. The Manage Transaction Monitors page is displayed, showing the related nodes and related applications.
EDITING TRANSACTION AND TRANSACTION STEP DEPENDENCIES
Transaction and Transaction Step Dependencies created this way are shown on the Manage Dependencies page. By default they are created with "Transaction dependency" and "Transaction Step dependency" as the Dependency Name, and with the node or application as the Parent and the transaction or transaction step as Child.
These dependencies can then be managed or edited in the same way as other dependencies as described in Managing Dependencies in the Orion Common Components Administrator Guide.
page 53 CREATING DEPENDENCIES ON THE MANAGE DEPENDENCIES PAGE
The Manage Dependencies page enables you to create a parent-child dependency between any two Orion objects, including Player locations, transactions and transaction steps.
To create a dependency:
1. Click Settings in the top right of the web console. 2. Click Manage Dependencies in the Node & Group Management grouping. 3. Click Add new dependency. 4. On the Select Parent page, complete the following steps: a. Use the Show only: and Group by: selection fields to customize the list of displayed objects and groups. The properties listed in the Group by: selection field are dynamic.
b. Select the parent object or group in the main pane, and then click Next. If you want to define a dependency so that the reported states of child objects are dependent on the status of multiple parent objects, create a group including all parent objects, and then select it on this view.
5. On the Choose Child page: a. Edit the Dependency name, as appropriate. b. Use the Show only: and Group by: selection fields to customize the list of displayed objects and groups. Properties listed in the Group by: selection field are dynamically dependent on the selection in the Show only: field.
c. Select the child object or group in the main pane, and then click Next.
If you want to define a dependency so that the reported states of multiple child objects are dependent on the status of one or more parent objects, create a group including all child objects, and then select it on this view.
6. On the Review Dependency page, review the current settings for the configured dependency.
l If any advanced alerts are configured on parent or child objects, they will be listed on this view. Click + to expand alert details.
l In the event that a parent object is down, alerts configured on any child objects in a dependency will not trigger because the child object status is Unreachable. 7. Click Submit to accept the dependency definition.
For complete documentation, see Managing Dependencies in the Orion Common Components Administrator Guide.
page 54 Monitoring your transactions
This section provides a complete list of WPM-specific resources available in the Transaction Summary view, the Transaction Details view, the Transaction Step Details view and the Location Details view. It also provides information about several of the resources. For information about a specific resource, click Help in the upper right corner of the resource.
To add a resource to a view:
1. Select the view to which you want to add the resource, and then click Customize Page. 2. Click the green plus icon, +, next to the column in which you want to display the resource. 3. To add a WPM-related resource, select Feature from the Group by dropdown, and then click Web from the list displayed. 4. Select the resource or resources you want to add, and then click Add Selected Resources. 5. Click Preview. 6. To edit the title and subtitle for this resource, click Edit in the resource title bar. Some resources have additional options on the Edit Resource page.
7. Amend the default information displayed. 8. Click Submit.
In addition to the WPM-specific resources, you also have access to the standard resources and those supplied with other SolarWinds products. For further information on adding and managing the resources shown in a view, see Editing Views in the Orion Common Components Administrator Guide. THE TRANSACTIONS SUMMARY VIEWS
The WPM Web Console provides both overviews and detailed views to present a wide array of information about the transactions you have created.
Each view is made up of graphs, charts or tables pertaining to that view. These resources can be added, removed, edited or deleted to present the view in a way that shows the information you want in the way most useful to you. You can add tabs to a view if you need to organize it in to smaller pages.
For information on customizing views, see Customizing Views in the Orion Common Components Administrator Guide.
The overview view is known as the Transactions Summary view. If you require more detail about any location, transaction or step listed on this view, click the location, step or transaction name in any resource to open the appropriate details view.
To view the Web Transactions Summary view in the Web Console, go to Web > Transaction Summary.
page 55 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
TRANSACTION SUMMARY VIEW
This overview displays information about all your WPM transactions, and can be used to drill down into details about individual transactions, transaction steps and locations. If you require more detail about any transaction, step or location listed , click the step, transaction or location name within any resource to open the appropriate details view.
You can customize this view by adding or removing resources, adding or removing columns in which these resources are displayed, changing the title of the view or any of the resources on it, adding navigation tabs, and adding view limitations.
For information on customizing views, see Customizing Views in the Orion Common Components Administrator Guide.
The following WPM resources are available in this view:
l Active Transaction/Step/Location Alerts
l All Locations
l All Transactions
l Last XX Events
l Steps by Status
l Top XX Steps by Duration
l Top XX Transactions by Duration
l Transactions by Status
l Transaction Health Overview TRANSACTION DETAILS
This view is used to display information about a selected transaction, and can be used to drill down into details about individual transaction steps and the player location. Click the step or location name within any resource to see the appropriate details view.
You can customize this view by adding or removing resources, adding or removing columns in which resources are displayed, changing the title of the view or any of the resources on it, adding navigation tabs, and adding view limitations.
For information on customizing views, see Editing Views in the Orion Common Components Administrator Guide.
The following WPM resources are available in this view:
l Active Transaction/Step/Location Alerts
l All Locations
l All Transactions
l Current Screenshot of Steps
l Duration - Radial Gauge
page 56 l Last XX Events
l Min/Max Average Duration
l Recording Custom Properties
l Screenshots of Last XX Failures
l Step Duration
l Steps by Status
l Top XX Locations by Duration
l Top XX Transactions by Duration
l Transaction Application Dependencies
l Transaction Availability
l Transactions by Status
l Transaction Custom Properties
l Transaction Details
l Transaction Health Overview
l Transaction Node Dependencies STEP DETAILS
This view is used to display information about a selected transaction step.
You can customize this view by adding or removing resources, adding or removing columns in which resources are displayed, changing the title of the view or any of the resources on it, adding navigation tabs, and adding view limitations.
For information on customizing views, see Editing views in the Orion Common Components Administrator Guide.
The following WPM resources are available in this view:
l All Locations
l Active Transaction/Step/Location Alerts
l All Transactions
l Current Screenshot of Steps
l Duration - Radial Gauge
l Min/Max Average Duration
l Page Elements Overview
l Screenshots of Last XX Failures
l Step Availability
l Step Details
l Step Duration
l Steps by Status
page 57 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
l TCP Waterfall Chart
l Top XX Locations by Duration
l Top XX Steps by Duration
l Top XX Transactions by Duration
l Transaction Health Overview
l Transactions by Status LOCATION DETAILS
The Location Details view is used to display information about a specific player location.
You can customize this view by adding or removing resources, adding or removing columns in which resources are displayed, changing the title of the view or any of the resources on it, adding navigation tabs, and adding view limitations.
For information on customizing views, see Editing Views in the Orion Common Components Administrator Guide.
The following WPM resources are available in this view:
l Active Transaction/Step/Location Alerts
l All Locations
l All Transactions
l Last XX Events
l Location Details
l Player Load Percentage
l Steps by Status
l Top XX Steps by Duration
l Top XX Transactions by Duration
l Transaction Availability
l Transaction Health Overview
l Transactions by Status ACTIVE TRANSACTION/STEP/LOCATION ALERTS
This resource lists all currently active transaction, step or location alerts. The table lists the time, object name, and message for each active alert.
l Highlight an Object Name to show popup details of the corresponding location, step or transaction
l Click an Object Name in the list to navigate to the specific location, step or transaction details view relating to this alert. AVAILABLE CUSTOMIZATION
Click Edit to: page 58 l Change the Title and Subtitle of this resource
l Show or hide acknowledged alerts ALL LOCATIONS
The All Locations resource shows all the locations where transaction players exist, with the following columns:
l Location Name (with status icon):
l Highlight the location to show pop-up location information
l Click on the location name to show the Location Details view
l Number of Managed Transactions, highlighting how many have problems
l The Version of the player
l The percentage Current Player Load AVAILABLE CUSTOMIZATION
You can change the Title and Subtitle of this resource by clicking Edit and editing the appropriate fields.
DEFINING TRANSACTION PROBLEMS
Click Edit to display the "Transactions with Problems" checkboxes. Here you can select the states (Warning, Critical, Down, Unreachable and Unknown) that you want to be included in the number of problems shown in the Managed Transactions column.
ADVANCED FILTERING
Advanced users can create their own filters to show or hide the locations displayed using SWQL. Click Properties available for filtering to display the properties you can use.
MANAGING LOCATIONS
Click Manage Locations to open the Manage Transaction Locations screen. For further information, see Managing playback locations ALL TRANSACTIONS
The All Transactions resource provides a tree view of your transaction monitors, allowing you to see the status of the transactions and whether any are unresponsive.
l Expand transactions to show steps in the tree view.
l Click a transaction, step or location to navigate to the corresponding transaction, step or location details view.
Click Manage Transactions to add, edit, enable, disable, or delete transaction monitors. For further information, see Managing transactions.
page 59 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
AVAILABLE CUSTOMIZATION
Title/Subtitle The title and the subtitle of the resource.
Group by Groups the items in the tree by None, Location, Playback Interval, Recording, or Status
Group Determines the status of the group or transaction (parent) if the group members or the status rollup individual steps (child items) do not all share the same status. type l Mixed: sets the parent status to Warning if the child items do not all have the same status.
l Worst: sets the parent status to the child item with the worst status.
l Best: sets the parent status to the child item with the best status.
Order by Sorts the items in the tree by Name or Status.
Remember Check to remembers which tree items you expanded in the resources and restores their Expanded expanded viewing state any time the view is reloaded. State
Always Check to show tree expanded to show transactions. Expand Root Level
Show Check to display how long it took to playback each transaction monitor or step. Durations
Hide Check to hide all transactions marked as unmanaged. Unmanaged Transactions
Filter (SWQL) Here you can enter a (SWQL) query using transaction properties to limit the scope of transaction monitors shown in this resource. For example, to only display transactions that have a location name starting with 'Japan', use: Transactions.Location LIKE 'Japan%'
Properties Click + to expand the list of transaction properties you can use in the Filter (SWQL) field. available for filtering
CURRENT SCREENSHOT
This resource displays the latest screenshot resulting from this step.
l To see a full-size image of the screenshot, click View screenshot full screen
l To view the HTML of the page as it appeared at the time of the screenshot, click View HTML
page 60 AVAILABLE CUSTOMIZATION
l Click Edit to change the Title and Subtitle of this resource CURRENT SCREENSHOT OF STEPS
This resource displays screenshots taken of the steps within this transaction at the indicated date and time.
l To see a full-size image of a screenshot, click View screenshot full screen beneath it
l To view the HTML of a page at the time of the screenshot, click View HTML beneath it AVAILABLE CUSTOMIZATION
l Click Edit to:
l Change the Title and Subtitle of this resource
l Change the Maximum Number of Items to Display
l Filter the screenshots shown using an SWQL statement. DURATION - RADIAL GAUGE
This resource shows the current duration of the transaction or step as a radial gauge.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Gauge Select a method for determining the largest value the gauge can indicate: Range l Dynamic: You provide a series of indicator ranges, and the limit that is chosen is the one that best fits the highest value seen in the data. Enter your comma- delimited series of custom limits in the Limits for Dynamic Range in Seconds field.
l Static: Define the largest indicated value in the Maximal Value in Seconds field.
l Thresholds dependent: Defines the largest indicated value by multiplying the highest threshold duration by a multiplier. Enter the multiplier in the Upper Threshold Multiplier field.
If there are no thresholds defined, the dynamic method is used.
Select Style Select a style for the gauge. Alternately, you can click on Available Styles and click on the for Gauges image of the required gauge type.
Gauge Size This field contains the scaling percentage of the gauge display. You can enter a scaling 30% to 250% factor from 30 to 250. 100 is the default scaling value.
page 61 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Available Click the [+] to see the available styles for gauges. Styles
LAST XX EVENTS
This resource lists the most recent events that have occurred for Locations, Transactions and Transaction Steps. For each event, the date and time of the event, the event Status icons, and event description is displayed.
AVAILABLE CUSTOMIZATION
Click Edit to open the Edit Resource page. Here you can:
l Edit the Title of this resource
l Specify the Maximum Number of Events to be displayed
l Select the Time Period for the list to cover LOCATION DETAILS
The Location Details resource presents a table of general operational and administrative information for the selected location.
Management Click Edit to go to the Transaction Location page where you can set up and manage location players.
For further information, see Managing playback locations
Status Displays a green check icon if the location is running within the operating thresholds, or critical, warning, or down icons if not.
Location Name The location name.
Communication Shows whether this is "Server initiated communication (passive)" or "Player initiated type communication".
DNS name The DNS name of this location.
Hostname The hostname of this location.
IP address The IP address of this location.
Assigned to The name of the poller assigned to this player location. poller
Version The version of the player at this location.
Current player The current percentage load for this player. load
page 62 Transactions The transactions assigned to this player. For each, the status icon, transaction name, most recent step duration and status is displayed.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle: The title and the subtitle of the resource. MIN/MAX AVERAGE DURATION
The Min/Max Average Duration Chart is located on both the Transaction Details page and the Step Details page. This chart lets you compare the average amount of time an individual transaction or step takes with the longest and shortest times that the transaction or step takes to complete.
This chart is interactive. Hovering over any part of the chart will provide detailed information for a selected period. You can check or uncheck either box in the legend to add or remove that element from the chart.
ZOOMING
Use the Zoom buttons to display data for 1 hour, 12 week, or 24 hours, or use the slider handles below the chart to create your own period. You can move the selected period to any point in the available data range using the slider bar.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title and Rename the title and subtitle of this resource as required. Subtitle
Time Here you can select the default period of data displayed, the amount of historical data Period available and the sample interval. If the sample interval is greater than the playback interval, the data within the sample will be summarized.
Advanced Here you can change the chart title and subtitle from the defaults of $(Caption) and $(ZoomRange).
PAGE ELEMENTS OVERVIEW
The Page Elements Overview displays a breakdown of elements contained in the navigated URL as a pie chart. Each category shows the number of requests and overall size of downloaded data in both the legend and the tool-tips.
Click an item in the legend of the Page Elements Overview to toggle the corresponding pie section's visibility.
page 63 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
AVAILABLE CUSTOMIZATION
Click Edit to:
l Change the Title and Subtitle of the resource
l Use the count of elements as the chart value instead of their size
The Page Elements Overview chart shows only data from the last playback for this transaction.
PLAYER LOAD PERCENTAGE
The Player Load Percentage Chart shows the load percentage of an individual player at any given time.
If you notice the load percentage is high, you should consider increasing the time intervals between polls and/or adding more players to a given location. Adding more players will help reduce the load by distributing the load more evenly.
This chart is interactive. Hovering over any part of the chart will provide detailed information about the load percentage.
ZOOMING
You can display data for 1 hour, 12 week, or 24 hours, or use the sliders below the chart to select your own period. You can also move the selected period to any point in the available data range.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title and Rename the title and subtitle of this resource as required. Subtitle
Calculated Check the checkbox to show a trend line on the chart showing the overall trend of the load Series percentage.
Time Here you can select the default period of data displayed, the amount of historical data Period available and the sample interval. If the sample interval is greater than the playback interval, the data within the sample will be summarized.
Advanced Here you can change the chart title and subtitle from the defaults of $(Caption) and $(ZoomRange).
REQUESTS WITH ISSUES
The Requests with Issues resource, lists the specific URLs of requests that have caused errors, showing the element type requested and status code.
page 64 l Click the URL to open this location in a new browser tab.
l Click any status code to display a full explanatory list of status codes.
l To export this list, click Export CSV, then click Open or Save to view or save as a Comma-Separated Values (CSV) file. AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Display Check the status codes requests must return to be listed. requests with status code
Filter Advanced users can create their own filters to show or hide the requests displayed using SWQL. Click Properties available for filtering to display the properties you can use.
RECORDING CUSTOM PROPERTIES
The Recording Custom Properties resource shows any custom properties set up for a recording.
If recording properties have already been set up, you can edit or create custom properties by clicking Edit Custom Properties Values on this resource. Otherwise go to Settings > Manage Custom Properties.
For more information, see Managing Custom Properties in the Orion Common Components Administrator Guide.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
SCREENSHOTS OF LAST XX FAILURES
This resource displays the screenshots taken during the most recent step failures. It shows the time of each failure, the step name, the error message, and a thumbnail of the screenshot.
l Click View screenshot full screen under the thumbnail to see a full-size image of the screenshot.
l Click View HTML under the thumbnail to view the HTML of the page as it appeared at the time of the screenshot.
page 65 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
AVAILABLE CUSTOMIZATION
Click Edit to:
l Change the Title and Subtitle of this resource
l Change the Maximum Number of Items to Display
l Filter the screenshots shown using an SWQL statement SCREENSHOTS OF LAST XX STEP FAILURES
This resource displays the screenshots taken during the most recent transaction failures. It shows the time of each failure, the step name, the error message, and a thumbnail of the screenshot.
l To view the details page for a step, click the step name
l To see a full-size image of the screenshot, click View screenshot full screen under the thumbnail
l To view the HTML of the page as it appeared at the time of the screenshot, click View HTML under the thumbnail AVAILABLE CUSTOMIZATION
Click Edit to:
l Change the Title and Subtitle of this resource
l Change the Maximum Number of Items to Display
l Filter the screenshots shown using an SWQL statement. STEP APPLICATION DEPENDENCIES
The Step Application Dependencies resource lists any applications that have been associated with this transaction step.
Step Dependencies enable you to apply dependencies at the level of a transaction step, therefore allowing the greatest degree of granularity for troubleshooting. If you do not require a separate dependency for each step in a transaction, you should use Transaction Dependencies instead.
To edit or add dependencies, click Edit in the Step Details resource.
For each node in the list, the current response time and percentage packet loss is displayed.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
page 66 STEP AVAILABILITY
The Step Availability Chart, lets you see the percentage of time a transaction step is in a particular state, such as Up, Down, Warning, Critical, or Unknown. The state of the transaction step at a given time can be determined by referencing the color-coding of the chart and the legend below the chart.
Move the mouse over the main chart to reveal a tool tip with more detailed information for a time slice within the period.
ZOOMING
Use the Zoom buttons to display data for 1 hour, 12 week, or 24 hours, or use the slider handles below the chart to create your own period. You can move the selected period to any point in the available data range using the slider bar.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Default Zoom Select the default zoom range to be shown when this resource is viewed. Range
Amount of Select the period of historical data you want to be available for this resource. historical data to load
Sample Interval Select a predefined sample interval. There may be gaps in the chart if you select a sample interval shorter than your transaction playback interval.
Chart Width Set the width of the chart in pixels. A value of 0 lets the chart automatically determine the best chart width.
Chart Height Set the height of the chart in pixels. A value of 0 lets the chart automatically determine the best chart height.
STEP DETAILS
The Step Details resource presents a table of general operational and administrative information for the selected step.
The Management row provides direct links to the following management actions:
l Edit - allows you to directly edit the transaction to which this step belongs.
l Play entire transaction now - initiates an immediate, unscheduled playback of the transaction the step belongs to.
The remaining table rows describe the following information: page 67 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Status Displays a green up icon if the step is running within the operating thresholds, or critical, warning, or down icons if it is not.
Page name The title of the web page accessed by the step.
URL The URL of the web page accessed by the step.
Duration The amount of time it took to play back this step.
Recording The recording used to create the transaction. Name
Location The location used to create the transaction.
Playback The period of time between successive playbacks of the transaction. interval
Last played The date and time this step was last played.
Next The date and time at which the step will be played again. If it is currently being played, it playback will read Now.
Actions The browser actions that comprise this step.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Show Actions List Click to toggle whether or not actions are displayed for this step.
STEP DURATION
The Step Duration Chart, located on the Transaction Details page, lets you see the time individual steps of a transaction takes to complete.
Note: AJAX calls are not included in step duration calculations.
This chart is interactive. Hovering the mouse over the chart will show each step duration for the selected time.
Beneath the chart the individual steps of the transaction are listed, showing the optimal threshold and 95% percentile for each step.
l The optimal threshold (or typical value) can be edited on the Edit Transaction Monitor page.
l The 95% percentile is a statistical concept indicating that for 95% of the time the step duration was below this figure.
page 68 ZOOMING
Use the Zoom buttons to display data for 1 hour, 12 week, or 24 hours, or use the slider handles below the chart to create your own period. You can move the selected period to any point in the available data range using the slider bar.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Time Period Here you can select the default period of data displayed, the amount of historical data available and the sample interval. If the sample interval is greater than the playback interval, the data within the sample will be summarized.
Advanced Here you can change the chart title and subtitle from the defaults of $(Caption) and $(ZoomRange).
STEP NODE DEPENDENCIES
The Step Node Dependencies resource lists any nodes that have been associated with this transaction step.
For each node in the list, the current response time and percentage packet loss is displayed.
Step Dependencies enable you to apply dependencies at the level of a transaction step, therefore allowing the greatest degree of granularity for troubleshooting. If you do not require a separate dependency for each step in a transaction, you should use Transaction Dependencies instead.
To edit or add dependencies, click Edit in the Step Details resource.
For each node in the list, the current response time and percentage packet loss is displayed.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
STEPS BY STATUS
This resource lists transaction steps by their status.
You can configured and rename this resource to display steps with a particular set of statuses. For example, it is often renamed "Steps with Problems," and filtered to show steps that have a status of Warning, Critical, Down, and Unknown.
To view the details page for a step or a transaction, click the step or transaction name.
page 69 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Statuses to filter The resource displays only the steps that have the selected statuses. Your selection by may include Up, Warning, Critical, Down, and Unknown statuses.
Filter (SWQL) Enables you to enter an SWQL query using transaction step properties to limit the steps displayed.
Properties Click + to expand the list of transaction properties you can use in the Filter (SWQL) available for field. filtering
TCP WATERFALL CHART
The TCP Waterfall Chart displays data for a transaction both cumulatively and sequentially. The benefit of this view is that you can see how each requested element affects page load performance, which elements are slowing things down and why. The stub at the left of the chart shows the element of the transaction being loaded, while the times for each element are shown to the right, color-coded in graphical form.
By default, only 20 requests are shown in the resource. To see all requests, click show xxx remaining requests to show the chart in full screen.
You can also expand the chart by clicking Show this chart in full screen.
The TCP Waterfall Chart only shows data from the last playback.
DNS The time it takes for the browser to look up the domain name of the requested object. lookup
Connection This represents the time for establishing a TCP connection, at which point data can start being transferred. (Also known as the "three-way handshake.")
Send The time for sending the request to the server. Good for measuring POST data.
Time to This is the time between when the request is sent to the server and the first response data first byte are received from the server. In another words it is the time the browser spends waiting on the web server to send the data back. This time is usually higher for the dynamically- generated content (such as aspx/php/jsp pages).
Content This is time it takes for the whole content to be sent from server to the browser. download
page 70 3xx HTTP Indicates a requests that resulted in the return of a 3xx HTTP status code. 3xx codes Status indicate that automatically forwarding or redirection to another resource (URL) without Codes interaction of the user.
4xx, 5xx Indicates a requests that resulted in the return of a 4xx or 5xx HTTP status code. 4xx codes HTTP are received in the server response when there is an error in the request from the client. Status 5xx codes are returned by the web server when it encounters a problem during processing Codes of the requested resource by the client.
l This chart is interactive. Clicking any item in the stub of the TCP Waterfall Chart will take you to that item, be it a graphic, web page, JavaScript element, and so on. Hovering your mouse over any item in the chart will bring up a tool-tip with detailed information about that particular item.
l There may be a slight discrepancy between the numbers found in the tool-tips and those shown on the chart. This is due to rounding. AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Maximum Number of Items to Enables you to specify the maximum number of items to display in Display the resource.
TOP XX LOCATIONS BY DURATION
The Top XX Locations by Duration chart is located on both the Transaction Details and Step Details page. This chart will display the duration of a transaction or step as it is played from multiple locations. With this view, you can easily see which locations are performing poorly for a given transaction or step. The worst, or slowest performing locations, are shown from the top down.
This chart is interactive. Move the mouse over the main chart to reveal a tool tip with more detailed information for a time slice within the period.
A list of the transactions appears below the chart, showing the current and average duration of each transaction. (The average is calculated using the selected amount of historical data loaded.) Click any transaction to display its Transaction Details view.
ZOOMING
Use the Zoom buttons to display data for 1 hour, 12 week, or 24 hours, or use the slider handles below the chart to create your own period. You can move the selected period to any point in the available data range using the slider bar.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes: page 71 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Title/Subtitle Edit the title and subtitle for this resource if required.
Maximum Enter the maximum number of locations to be displayed. Number of Items to Display
Time Period Here you can select the default period of data displayed, the amount of historical data available and the sample interval. If the sample interval is greater than the playback interval, the data within the sample will be summarized.
Advanced Here you can change the chart title and subtitle from the defaults of $(Caption) and $(ZoomRange).
TOP XX STEPS BY DURATION
This resource lists the steps with the longest running duration during the latest playback of the transaction. For each step, this resource displays the step name, the transaction it belongs to, the duration for the step in seconds, and the percentage of optimal duration this represents.
Click any step, transaction or location name to view its details page.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Maximum Number of Enables you to set the maximum number of items to display in the resource. Items to Display
Filter (SWQL) Enables you to enter a (SWQL) query using transaction properties to limit the scope of transaction monitors shown in this resource.
Properties available Click [+] to expand the list of transaction properties you can use in the Filter for filtering (SWQL) field.
TOP XX TRANSACTIONS BY DURATION
The Top XX Transactions by Duration Chart, located on the Location Details page, lets you see the amount of time an entire transaction took to complete.
This chart is interactive. Hovering over any part of the chart will provide detailed information about the transaction.
A list of the transactions appears below the chart, showing the current and average duration of each transaction. (The average is calculated using the selected amount of historical data loaded.) Click any transaction to display its Transaction Details view.
page 72 ZOOMING
Use the Zoom buttons to display data for 1 hour, 12 week, or 24 hours, or use the slider handles below the chart to create your own period. You can move the selected period to any point in the available data range using the slider bar.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Maximum Number of Enables you to specify the maximum number of items to display in the Items to Display resource.
Filter (SWQL) Enables you to enter a (SWQL) query using transaction properties to limit the scope of transaction monitors shown in this resource.
Properties available Click [+] to expand the list of transaction properties you can use in the Filter for filtering (SWQL) field.
TRANSACTION AVAILABILITY
The Transaction Availability Chart, lets you see the percentage of time a transaction is in a particular state, be it Up, Down, Warning, Critical or Unknown. The state of the transaction at a given time can be determined by referencing the color-coding of the chart and the legend below the chart. By hovering the mouse over the chart you can display a pop-up of further information.
ZOOMING
Use the Zoom buttons to display data for 1 hour, 12 week, or 24 hours, or use the slider handles below the chart to create your own period. You can move the selected period to any point in the available data range using the slider bar.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Default Zoom Select the default zoom range to be shown when this resource is viewed. Range
Amount of Select the period of historical data you want to be available for this resource. historical data to load
page 73 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Sample Interval Select a predefined sample interval. There may be gaps in the chart if you select a sample interval shorter than your transaction playback interval.
Chart Width Set the width of the chart in pixels. A value of 0 lets the chart automatically determine the best chart width.
Chart Height Set the height of the chart in pixels. A value of 0 lets the chart automatically determine the best chart height.
TRANSACTION APPLICATION DEPENDENCIES
The Transaction Application Dependencies resource lists the applications that have been associated with this transaction.
Dependencies in WPM allow you to tie together a transaction or transaction step to a resource in a type of parent-child relationship. A transaction level dependency applies to the whole transaction - if an event occurs anywhere during the transaction, the alert is triggered. if you want to troubleshoot your transaction on a more granular level you should use Step Dependencies.
To edit or add dependencies, click Edit in the Transaction Details resource. AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
TRANSACTION CUSTOM PROPERTIES
The Transaction Custom Properties resource shows any custom properties set up for a transaction.
If recording properties exist, you can edit or create transaction custom properties, click Edit Custom Properties Values on this resource. Otherwise go to Settings > Manage Custom Properties.
For more information, see Managing Custom Properties in the Orion Common Components Administrator Guide.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of this resource.
TRANSACTION DETAILS
The Transaction Details resource presents a table of general operational and administrative information for the selected transaction.
page 74 The Management row provides direct links to the following management actions:
l Edit: opens the Edit Transaction Monitor page, allowing you to directly edit the transaction.
l Unmanage: launches the Unmanage Monitor window, enabling you to suspend the playing of this transaction for a specified period of time.
l Play now: initiates an immediate, unscheduled playback of the transaction.
The remaining table rows describe the following information:
Status Displays a green up icon if the transaction is running within operating thresholds, or critical, warning, or down icons if it is not.
Recording The recording used to create the transaction. Name
Recording The internal reference number of this transaction. ID
Location The location and the status of the location for this transaction.
Playback The period of time between successive playbacks of the transaction. interval
Last played The date and time this transaction was last played.
Next The date and time at which the transaction will be played again. If it is currently being playback played, it will read Now.
Description The description for this transaction.
Steps A list of the steps in this transaction, showing the latest step duration and current status.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
TRANSACTION HEALTH OVERVIEW
This resource displays a pie chart overview showing the statuses of all your transactions. The legend beneath the chart can be expanded to list transactions by status.
AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title and Subtitle The title and the subtitle of the resource.
page 75 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Remember Checking this checkbox will automatically open tree structure of transactions, Expanded State grouped by status, every time the user accesses this page.
Hide Unmanaged Checking this checkbox will hide any transactions that have been marked as Transactions unmanaged.
Filter (SWQL) Enables you to form a (SWQL) query using transaction properties to limit the scope of transaction monitors shown in this resource.
Properties Click + to expand the list of transaction properties you can use in the Filter (SWQL) available for field. filtering
Advanced Click to edit the Chart Title and Chart Subtitle.
TRANSACTION NODE DEPENDENCIES
The Transaction Node Dependencies resource lists the nodes that have been associated with this transaction.
For each node in the list, the current response time and percentage packet loss is displayed.
Dependencies in WPM allow you to tie together a transaction or transaction step to a resource in a type of parent-child relationship. A transaction level dependency applies to the whole transaction - if an event occurs anywhere during the transaction, the alert is triggered. if you want to troubleshoot your transaction on a more granular level you should use Step Dependencies.
To edit or add dependencies, click Edit in the Transaction Details resource. AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
TRANSACTIONS BY STATUS
This resource shows a list of transaction names and their durations in seconds. The duration of a transaction is the sum of all its step durations.
You can configure and rename this resource to display transactions with a particular set of statuses. For example, it is often renamed "Transactions with Problems", and filtered to show transactions that have a status of Warning, Critical, Down, and Unknown.
To view the details page for a transaction, click the transaction name.
page 76 AVAILABLE CUSTOMIZATION
Click Edit to change the following resource attributes:
Title/Subtitle The title and the subtitle of the resource.
Statuses to filter The resource displays only the transactions that have the selected statuses. Your by selection may include Up, Warning, Critical, Down, and Unknown statuses.
Filter (SWQL) Enables you to form a (SWQL) query using transaction properties to limit the scope of transaction monitors shown in this resource.
Properties Click [+] to expand the list of transaction properties you can use in the Filter (SWQL) available for field. filtering
page 77 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Solutions
Being part of SolarWinds Orion, means you can use the common functionality as you would with NPM or any other Orion product.
l The AppStack Environment
l Custom Properties
l Alerts
l Reporting
page 78 The AppStack Environment
The Application Stack, or AppStack, is a term used to describe the various layers that make up a complex application delivery infrastructure. The AppStack Environment view is an interactive visual mapping within Orion that provides an in-depth perspective through the entire environment to help identify the root cause of performance and availability issues.
AppStack will automatically gather information about objects in your environment, as well as their respective relationships, and display them. Some relationships, such as groups and dependencies can be defined by the user.
Important: As a standalone product, AppStack is available in the software versions listed below. If you own one or more of the listed products in addition to Web Performance Monitor 2.2, AppStack will not function properly unless each version of the software is upgraded to the versions listed:
l Server & Application Monitor 6.2
l Storage Resource Monitor 6.0
l Virtualization Manager 6.2 INTRODUCTION TO THE APPSTACK ENVIRONMENT VIEW
The AppStack Environment view is designed to provide you with a powerful layer of troubleshooting visibility by exposing all participating objects in your environment, as well as their relationships to one another. This view is useful in assessing the overall health of your environment, as well as troubleshooting specific and related problems.
To help you better understand how this visualization of your environment can be used for troubleshooting, the following analogy was designed to provide you with a simple, high-level overview of how AppStack processes and displays information.
THE APPSTACK ENVIRONMENT VIEW ANALOGY
Imagine you work for a company comprised of many employees that work in various departments. In this example, you work in the Engineering department as an engineer:
page 79 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Now imagine you call in sick and are unable to work for two weeks. Certain employees in various departments will be affected by your absence. Others will not be affected. The illustration below highlights the employees who will be affected by your absence by fading those who are not affected.
page 80 Focusing on only the people who are affected by your absence can be beneficial from a task management perspective. Therefore, completely hiding those not affected by your absence will give a clean and concise view, displaying only the necessary information.
Now, instead of employees, imagine we are talking about your entire IT environment. The goal of the AppStack Environment view is to help you quickly assess the impact a given object has on its related objects. This relational view is the AppStack Environment view found in the web console.
page 81 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
THE APPSTACK ENVIRONMENT VIEW
The AppStack Environment, shown below, displays the status of individual objects in your IT environment through the Orion web console. Objects are categorized and ordered from left to right, with the worst status being shown on the left side of the view.
Clicking an object shows everything related to that object by fading unrelated objects, as shown:
page 82 Clicking Spotlight removes the faded, unrelated objects from the view entirely.
page 83 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Clicking the selected object at the top, or double-clicking it in the view, will take you to the Details page for that object for further investigation. APPSTACK CATEGORIES AND DATA
The following matrix outlines all of the categories associated with the AppStack Environment view. Different categories are available with each SolarWinds product, as indicated in the Product column
CATEGORY DEFINITION PRODUCTS
Groups Groups enable you to more effectively manage your environment by giving l SRM you the ability to logically organize monitored objects, regardless of device l SAM type or location. l VMan
l WPM
Applications In SAM, an application is a collection of component monitors grouped l SAM together to collect specific metrics concerning the application as a whole.
Transactions A transaction is a recording of web browser steps assigned to a specific l WPM location.
Steps A step is a collection of actions. For example, the actions required to l WPM navigate to a specific URL make up one step.
Servers A server is a computer capable of accepting requests from the client and l SAM giving responses accordingly. The server makes services, as access to data l VMan files, programs, and peripheral devices, available to workstations on a network.
Hosts A Host is defined as a server running a Hypervisor for virtualization. (E.g. It l SAM hosts multiple virtual machines.) l VMan
Virtual Virtual clusters are built with VMs installed at distributed servers from one l SAM Clusters or more physical clusters. The VMs in a virtual cluster are logically l VMan connected by a virtual network across several physical networks. Each virtual cluster is formed with physical machines or a VM hosted by multiple physical clusters.
Virtual A virtual datacenter is a centralized virtual repository for the storage, l SAM Datacenters management, and dissemination of data and information organized around l VMan a particular body of knowledge or pertaining to a particular business.
Virtual A VMware virtual center (vCenter) server is a centralized management l SAM Centers application that lets you manage virtual machines and ESXi hosts centrally. l VMan The vSphere client is used to access vCenter Server and ultimately manage ESXi servers.
page 84 CATEGORY DEFINITION PRODUCTS
Data Stores A data store is a repository of a set of data objects. These objects are l VMan modeled using classes defined in a database schema. A data store is a general concept that includes not just repositories like databases, but also simpler store types such as flat files. Some data stores represent data in only one schema, while other data stores use several schemas for this task.
Volumes A volume, or logical drive, is a single accessible storage area with a single l SRM file system, typically resident on a single partition of a hard disk. l SAM
LUNS A Logical Unit Number, or LUN, is a number used to identify a logical unit, l SRM which is a device addressed by the SCSI protocol or Storage Area Network protocols which encapsulate SCSI, such as Fibre Channel or iSCSI. A LUN may be used with any device which supports read/write operations, such as a tape drive, but is most often used to refer to a logical disk as created on a SAN.
NAS Network-attached storage (NAS) is a type of dedicated file storage device l SRM Volumes that provides local-area network (LAN) users with centralized, consolidated disk storage through a standard Ethernet connection.
Pools A storage pool (also called a RAID array ) is a collection of disk drives that l SRM become a logical entity. When you create a storage pool, you select the desired capacity (number of disk drives) and assign a RAID level to it which will provide a redundancy level.
VServers A virtual storage server (VServer) contains data volumes and one or more l SRM LIFs through which it serves data to the clients. A VServer can either contain one or more FlexVol volumes, or a single Infinite Volume.
A VServer securely isolates the shared virtualized data storage and network, and appears as a single dedicated server to its clients. Each VServer has a separate administrator authentication domain and can be managed independently by a VServer administrator.
In a cluster, a VServer facilitates data access. A cluster must have at least one VServer to serve data. VServers use the storage and network resources of the cluster. However, the volumes and LIFs are exclusive to the V-Server. Multiple Vservers can coexist in a single cluster without being bound to any node in a cluster. However, they are bound to the physical cluster on which they exist.
Storage Storage Arrays consist of two or more disk drives built into a stand-alone l SRM Arrays unit. Storage arrays provide increased availability, resiliency, and
page 85 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
CATEGORY DEFINITION PRODUCTS
maintainability by using existing components (controllers, power supplies, fans, and so on) often up to the point where all single points of failure are eliminated from the design.
UNDERSTANDING APPSTACK
The AppStack Environment view will help you find the root cause of application issues in a glance. This view provides automated and contextual visibility across applications, databases, physical servers, your virtual infrastructure, as well as storage resources.
The AppStack Environment view contains multiple tools and features to aid you in root cause analysis. The following sections provide detailed descriptions for each of these tools and features:
l Understanding status and colors
l Understanding Quick Links
l Understanding Categories
l Understanding the Overview Bar
l Understanding filtering options
l Understanding filter properties
l Understanding layouts
l Understanding the AppStack resource UNDERSTANDING STATUS AND COLORS
Objects in the AppStack Environment view are colored based on their current status, providing you a quick summary of your environment. Objects will be in one of the following states, represented by its icon's color and shape that corresponds to the following table:
STATUS COLOR EXAMPLE
Down Red
Critical Pink
Warning Yellow
Unknown Gray
Unreachable Black
Up Green
Other Blue -
page 86 STATUS COLOR EXAMPLE
External Purple -
Statuses only become available for filtering when an object in your environment is in that state. For example, if no objects have a status of Down, the Down status will not be available when filtering.
STATUS REPORTING
Servers can only provide an Up or Down status. To check CPU, memory, or hardware health status, hover the mouse over the server icon to view the detailed tool-tip. The reported status for applications and LUNs is based on performance thresholds.
UNDERSTANDING MIXED ICONS
The AppStack Environment view offers a parent/child relationship. (Parents can be either servers or hosts.) This relationship is represented as a mixed icon. The parent is the larger of the two icons that is hosting the child. For example, the following illustration graphically shows that an application (child) is Down on a node (parent) that is Up.
UNDERSTANDING QUICK LINKS
The Quick Links bar allows you to quickly open and close all visible object categories. Additionally, you can toggle whether or not to show the names of objects that have a distressed status.
l Expand All: Opens all categories, revealing the visible objects within each category. Note: Each category can be individually expanded and collapsed by clicking [+] and [-] next to the category name.
page 87 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
l Collapse All: Closes all categories, hiding the objects within each category. Note: Each category can be individually expanded and collapsed by clicking [+] and [-] next to the category name.
page 88 l Show/Hide Names: Allows you to toggle between showing and hiding the names for each object that is in a distressed state. Note: If more objects exist than are allowed to be displayed on the screen, the category name will display the number of displayed objects followed by the total number of objects. For example, (87 of 111), meaning only 87 objects of 111 total objects in this category are being displayed. This provides a numerical summary of your environment. Clicking More (located after the last visible object in the category) will display, by default, an additional 50 objects that are hidden from view. Related objects may be found by clicking More. The default number of 50 can be changed in the Settings page. For more information, see Customizing the AppStack Environment View.
UNDERSTANDING CATEGORIES
By default, the following AppStack Environment categories are available within Web Performance Monitoring.
l Groups
l Applications
l Servers
l Transactions
l Steps
Notes:
l Other Orion Core products offer additional categories.
l Empty categories can be hidden via the Change Layout Settings option in the drop down menu.
page 89 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
UNDERSTANDING THE CATEGORY STATUS SUMMARY
The Category Status Summary (located to the right of each category) parses, enumerates, and displays the number of objects in a given category, emphasizing the status as indicated by the colors. The Category Status Summary can be toggled to either be displayed at all times, or only when categories are collapsed. This option exists under the Change Layout Settings drop down option.
If no objects in a category exist with a particular status, that status will not show in the summary.
UNDERSTANDING THE OVERVIEW BAR
The Overview Bar summarizes your environment in a compact space. If your view is currently filtered, the filtered objects will be displayed above the Overview Bar, as shown. Individual filtered objects can be removed by clicking the [X] next to each object. To remove all filtered objects, click Clear All.
The doughnut chart in the Overview section graphically displays the ratio of objects to one another in all possible states using indicative colored slices. The total number of objects in your environment is also displayed.
Objects under the Issues header are parsed and enumerated according to status. Objects shown here will be in one of the following distressed states: Down, Critical, Warning, Unknown and Unreachable. An icon and count will only appear if at least one object is currently in that state.
UNDERSTANDING FILTERING OPTIONS
By default, every object is displayed when you enter the AppStack Environment view. If you are concerned only about objects with a certain status, you can filter the view by selecting one or more statuses and then applying the filter. Additionally, you can filter objects based on various properties, as well as one or more keywords. The illustration below details each tool and feature of the filtering sidebar:
page 90 Statuses only become available for filtering when an object in your environment is in that state. For example, if no objects have a status of Down, the Down status will not be available when filtering.
UNDERSTANDING FILTER PROPERTIES
The AppStack Environment allows you to filter what is displayed in this view, allowing you to see only the objects you want to see.
To filter the AppStack Environment view, take the following steps:
page 91 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
1. From the web console, navigate to Home > Environment.
2. Click [+] Add Filter Properties, as shown:
3. From the pop-up menu, select an object from the Orion Object drop down list:
Note: Multiple items can be added. 4. When done, click Add column.
page 92 5. The new filter appears in the filter column, as shown:
If no relations are shown in the AppStack resource on the Group Details view, then it is likely that this group contains no objects represented within the AppStack, such as switches, routers, and so on. If you have created a group that contains only objects which have no representation within the AppStack environment (e.g.: Nodes that are switches, routers, wireless access points, interfaces, and so on) then they will not have relationships and the only item displayed within the AppStack resource on the Group Details view is the group itself. This is normal behavior. Servers and virtual servers are the only node types that are represented within the AppStack environment. Groups made up of other object types which are not supported by the AppStack environment will not appear within the AppStack resource.
For more information, see Understanding filtering options . UNDERSTANDING LAYOUTS
A Layout is a user-defined filter (view-limitation), along with settings, that can be saved and recalled later within the AppStack Environment view. User-defined layouts can be used to tailor the AppStack Environment view to specific objects of interest. A default layout is provided and contains all objects visible in the AppStack Environment that is currently being monitored. The default layout cannot be modified.
New layouts are created by first filtering your environment, and then saving the changes via the Save As New Layout action in the Layout menu.
For example, to create a Layout where only IIS objects in the AppStack Environment view are shown, add the IIS filter property, apply the filter, and then save it as a new layout, naming the layout appropriately.
page 93 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Once saved, the layout is added to the drop down menu, allowing you to easily navigate to that layout with its defined filter and settings. The dot to the left of the name of the layout in the menu represents the layout currently in use, as shown:
Modifying Filter Properties of a Saved Layout
To change the filtering properties of the current layout, take the following steps:
1. Make changes to the filter. 2. Click Apply Filter, and then click Save (or Save as New Layout...) in the drop down menu.
Modifying Settings of a Saved Layout
To change the settings of the current layout, take the following steps:
1. Click Change Layout Settings from the drop down menu. 2. Click Save (or Save as New Layout...).
page 94 Deleting a Saved Layout
To delete a layout, take the following steps:
1. Select the layout from the drop down menu and then click Delete this Layout.
For more information, see Customizing the AppStack Environment View HIDING OBJECTS WITH "UP" STATUS
If you are not concerned about objects that are healthy and have an Up status, you can set up your display to limit the number of Up objects shown by default within each category. This is useful in troubleshooting situations, allowing you to only see objects in distress while limiting the visible number of objects that are healthy.
Additionally, you can hide the number of Up objects by changing the value to 0.
An environment with a large number of objects that are not in an Up state may benefit from using this limited view option.
For more information, see Understanding AppStack.
UNDERSTANDING THE APPSTACK RESOURCE
The full AppStack Environment view is designed to provide you with a powerful layer of troubleshooting visibility by exposing all participating objects in your environment, as well as their relationships to one another. By comparison, the AppStack resource only displays objects related to the target of the current Details page.
In essence, this resource displays the related objects you would see in the full AppStack Environment view after an object had been selected and then highlighted by clicking, Spotlight.
page 95 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
NAVIGATING TO APPSTACK
Navigating to the AppStack Environment view:
1. From the web console, navigate to Home > Environment.
page 96 2. You will be taken to the AppStack Environment view, as shown:
USING APPSTACK
Using AppStack as a troubleshooting tool is fairly straightforward. Simply navigate to the AppStack Environment view, and then click on an object to see what is related to that object. To investigate further, navigate to the Details page of the object or any related object.
For example, the illustration below displays all objects in the current environment. The application, MSSQLSERVER, is in a critical state, as indicated by its icon. To see what this application is related to, click the MSSQLSERVER icon.
page 97 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
To see objects related to an object, take the following steps:
1. From the web console, navigate to the AppStack Environment view by clicking Home > Environment. 2. Click any object, in this example, MSSQLSERVER. 3. Once an object is selected, related objects will be highlighted by the fading of unrelated objects, as shown:
To hide the unrelated objects completely from view, take the following step:
page 98 1. Once an object is selected, click Spotlight in the upper right-hand corner of the view.
To navigate to the details page of an object for further investigation:
1. Click the icon of the selected object to the left of the doughnut chart, or double-click the larger icon in the main view.
2. From the details page, you can now investigate the cause for the Critical status. CUSTOMIZING THE APPSTACK ENVIRONMENT VIEW
Administrators can customize this view by clicking Change Layout Settings in the Layout drop down menu of the AppStack page.
page 99 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
The following options are available:
Refresh Change the time between AppStack refreshes. Rate
Limit on Objects in the AppStack Environment view are ordered from left to right, with the worst Up status being shown on the left side of the view. Limiting the number of Up objects can Objects provide more room for objects needing attention. Additionally, limiting the number of Up Shown objects displayed can improve AppStack performance. per Category
Object Highlights distressed objects by displaying the names of these objects. Names
Align By default, all objects are left-aligned. This can be changed by selecting either Center or Objects Right-Aligned.
Show The Category Status Summary are the colored numbers to the right of each category, Category indicating the number of objects in a particular state. This can visible at all times, or only Status when categories are collapsed. Summary
page 100 Empty Selecting this option hides categories with no objects, giving the view a cleaner look. Categories
ADDING APPSTACK TO A NOC VIEW
Viewing the AppStack Environment in a NOC view can only be achieved by first adding a new NOC view, and then creating and applying an AppStack filter for this new view. Once complete, the AppStack resource will become part of the NOC view with the filter already applied.
To add the AppStack Resource to a NOC view, take the following steps:
1. From the web console, click Customize Page in the upper right-hand corner. 2. If not already done so, check Enable Left Navigation. 3. Click Add Tab. 4. Add a name for the tab in the field provided, then click Update. The new tab appears in the column to the left.
page 101 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
5. Add the AppStack Environment resource to a column by clicking the green [+], then selecting AppStack Environment from the pop-up dialog, as shown:
6. Click Add Selected Resources. 7. If not already done so, check Enable NOC view mode, then click Done.
8. Navigate to Home > Environment.
9. Filter your AppStack Environment according to you needs. When done, click Apply Filter.
page 102 10. Save the Layout as AppStack Environment, which was added in Step 5.
11. View the NOC by navigating to Home > Show in NOC Mode.
page 103 Custom properties
Custom properties are user-defined fields such as country, building, asset tag, serial number, etc., that you can define, associate with monitored network objects, and store in your SolarWinds database. After properties are added, they are available for use throughout the Orion Web Console.
For WPM, you can associate custom properties with transactions and recordings to add specific information for your specific requirements. These can then be used in the same way that other custom properties are used.
To create a custom property for WPM:
1. Log on to the Orion Web Console as an administrator. 2. Click Settings in the top right corner of the web console. 3. Click Manage Custom Properties in the Node & Group Management grouping. 4. Click Add Custom Property. 5. Select Transaction or Recording, and click Next. The dropdown list will show only the object types available for the SolarWinds Orion products you have installed.
6. To create a property based on a predefined template, click the appropriate Property Template. Property templates provide generic suggestions in the Property Name and Description fields and an appropriate custom property Format.
7. Edit the Property Name and Description fields, as appropriate. Property names must be unique for an object type. For example, you can have separate Comment properties for both Transactions and Recordings.
Property names are not case-sensitive. You cannot, for example, have properties called Comment and comment for the same object type.
8. Select the Format for the property. If Text is selected, you can click Edit to specify a maximum length. 9. Check the Required property box if this property must be provided for all objects. 10. To restrict the values that other, non-administrative users can select for the property, check Restrict values, and enter values, as follows: a. Enter an appropriate Value. b. Click Add Value. c. Repeat until you have entered all valid property values. d. To delete a property value, click X next to the property to delete. 11. Click Next.
page 104 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
12. Click Select
l Select an appropriate Group by: criterion, and click the group that includes the objects to which you want to apply this property
l Use the search tool to search for the objects to which you want to apply the selected property 13. Check the objects to which you want the selected custom property to apply. Click > to expand listed objects to view available child objects.
14. Click Add to add the checked objects to the Selected
For complete information on creating and managing custom properties, see Custom properties in the SolarWinds NPM Administrator Guide.
page 105 Alerts and WPM
An alert is an automated notification that a network event has occurred, such as a server becoming unresponsive. The network event that triggers a particular alert to activate is determined by conditions set up when you configure your alert.
Since Alerts can be created for any object in your Orion network, this includes WPM Locations, Transactions and Transaction Steps. For example, you could create a custom alert that is triggered when a specific location is unavailable for more than ten minutes. CREATING ALERTS
The following procedure shows how to quickly set up a simple alert, and assumes that default alert actions have already been set up. For complete documentation, see the Create Alerts in the SolarWinds NPM Administrator Guide.
1. Click Settings. 2. Under Alerts & Reports, click Manage Alerts. 3. Click Add New Alert. 4. Enter a Name and Description for the alert and click Next. 5. Select the object type you want to use to trigger this alert from the I want to alert on drop-down list. For WPM purposes this will likely be Player Location, Transaction or Transaction Step. 6. Set The scope of the alert. You can either apply it to all objects of this type or set up conditions to specify a set of objects. 7. Create the trigger condition that must be true or false for the alert to be triggered. You can create complex triggers using multiple AND/OR/NOT conditions, if required. A simple example trigger would be:
Object type: Location
Field: Status
Condition: is equal to
Value: Down
8. Click Next. 9. Leave the Reset Condition as is, and click Next. 10. Leave the Time of Day as is, and click Next. 11. Enter the message that you want to be displayed on the Alert resource and Alert details page when this alert is triggered. 12. To use variables in your message, such as Connection Status, Host Name or Transaction ID, position the cursor where you want to insert it and click Insert Variable.
page 106 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
a. Select the type of variable you want to insert and how to group them from the drop-down lists on the left. You can display Global variables, Alert variables or those specific to Locations, Step Requests, Transactions or Transaction Steps. The alert variables specific to each WPM object are listed in the Appendix: WPM alert variables. Global Variables and variables for other Core modules are listed in similar appendices in the Orion Core Administration Guide and appropriate Administrator Guides. b. The "Select variables to insert" popup window is displayed. c. Select the variable or variables you want to insert. When you select a variable, the SWIS code is displayed. d. Click Insert Variable to insert the selected variable(s) into your message.
You can add further trigger actions such as sending an email, playing a sound, executing an external program or sending a GET or POST request to a web server.
13. Click Next. 14. Leave the Reset Action as it is and click Next. 15. Scroll down to the bottom of the Summary and click Submit.
The alert is now added to the Manage Alerts page. VIEWING ALERTS
When set up, alerts are only displayed on the web console if they are active. Active Alerts are shown on the Home > Alerts view, on the Active Alerts resource and, in the case of transaction alerts, on the Active Transaction Alerts resource.
Clicking on the Alert name will open the Active Alert Details page for this alert. ACKNOWLEDGING ALERTS
On the Home > Alerts page, each active Alert has an Acknowledge button in the Acknowledged by column. Clicking this will halt any further escalation actions for this alert, and allow you to enter any relevant information in a notes popup. ADDING ALERT RESOURCES TO A VIEW
To add the All Active Alerts or Active Transaction Alerts:
1. Go to the View to which you want to add this resource, and click Customize Page. 2. Click + by the column to which you want to add the resource. 3. Check Active Alerts or Active Transaction Alerts in the Resource name column and click Add Selected Resources. 4. Click Done. 5. Click the Edit button for the resource you have just added.
page 107 6. Change the Title and add a Subtitle, if required. 7. If you want to display alerts that have been acknowledge, check the Show Acknowledge Alerts box. Otherwise, alerts will be hidden once they have been acknowledged on the Alerts page. 8. Click Submit.
page 108 WPM Reports
Full documentation on reports can be found in Manage reports in the SolarWinds NPM Administrator Guide. This includes scheduling reports, customizing the reports supplied with Orion modules such as WPM, and creating your own reports.
1. On the Orion Web Console, select Home > Reports. 2. Select Products from the Group by drop-down list. 3. Select WPM Reports. 4. The following reports are available:
l WPM Player Location Availability - Last Month
l WPM Player Location Availability - This Month
l WPM Player Location Availability - This Year
l WPM Recording Durations per Location
l WPM Transaction Availability - Last Month
l WPM Transaction Availability - This Month
l WPM Transaction Availability - This Year
l WPM Transaction Statistics
l WPM Transaction Step Availability - Last Month
l WPM Transaction Step Availability - This Month
l WPM Transaction Step Availability - This Year
l WPM Transaction Step Statistics
l WPM Transaction Step Variance - Last 30 Days
l WPM Transaction Step Variance - Last 7 Days
l WPM Transaction Step Variance - This Month
l WPM Transaction Step Variance - This Year 5. To view a report, click on its title and click View Report.
page 109 Appendices
This Appendix contains the following sections:
l Troubleshooting and Diagnostics
l Status icons
l WPM alert variables
Troubleshooting and Diagnostics
On occasion, you may encounter a problem with the Recorder or the Player that prevents you from creating or playing back a recording. This troubleshooting section discusses some of the known issues and workarounds that may help you get back on track:
l Common debugging scenarios
l For further troubleshooting topics, please see the SolarWinds Knowledge Base http://knowledgebase.solarwinds.com/kb/ COMMON DEBUGGING SCENARIOS
ISSUES WITH JAVASCRIPT
You may encounter the following issues while performing actions in the Recorder:
l JavaScript menu items are not recognized.
l Clicks on
l OnMouseOver events are not recognized.
Hold CTRL+SHIFT while performing the problem action. This adds additional data to the Recording that may allow access to the problematic element.
Use CTRL+SHIFT only to record the actions that are giving you problems. The additional data added to the recording may slow down playback considerably.
KEYBOARD INPUT DOES NOT WORK
Try using mouse clicks instead of keyboard navigation in the webpage.
LINKS DO NOT WORK
Try to find an alternative method. For example, if the Compose email link on a page does not work, perhaps the same action can be accomplished by clicking the Inbox button.
page 110 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
RECORDER HANGS OR BECOMES UNRESPONSIVE
If the Recorder hangs or becomes unresponsive, restart the Recorder program and recreate your recording.
ELEMENT NOT FOUND DURING PLAYBACK ERROR
If the element was not found during playback, recreate both the recording and the transaction.
TROUBLESHOOTING XY CAPTURE MODE
Following is a checklist that can help you diagnose common problems:
l If you are using proxy with authentication, ensure the credentials to the proxy are properly captured in the recording and/or the player is configured to use Active Directory accounts.
l Try adding steps to the recording to better identify the action on which the playback failed. By doing this, you will be breaking down the transaction to multiple steps. Now you can go step by step and examine the screenshots to see which action was not performed properly.
l Run the transaction in the recorder and ensure that all necessary items were loaded during playback. The object to be clicked on must be in place and active before the click action is executed.
l If page content is slow to load, try to insert a Wait action before the XY action. This will allow the content to load completely before executing the XY action.
l Try to re-record the recording on the same machine where the player is installed.
l If the playback is failing on the Image Match action, try the following:
l Examine the screenshot page to see if the image is present on the page.
l Ensure that the same version of Internet Explorer is used during both recording and playback.
l Image Matching may be affected by font smoothing settings. You should not use Image Matching on plain text. For text matches, use the Match Content action. Image Matching on animated objects is not supported.
Status icons
Orion modules, including WPM, use the following icons as status indicators in System Manager and Web Console resources. For alerts and events, additional information is provided with the icon in the resource. STATUS INDICATORS
The following table lists Orion icons with associated status indications, status types, and numerical status identifiers:
Status levels of type Ignore are not displayed in any status roll-up mode.
page 111 I STATUS INDICATION CON
Node or Interface is Down (Polling request timed-out) Error 2
Shutdown Error 4
Lower Layer Down Error 8
Unreachable Error 12
Node is in a Warning state (dropped packets or down Warning 3 interface)
Critical Warning 14
Mixed Availability Warning 15
Misconfigured Warning 16
Could Not Poll Warning 17
Unconfirmed Warning 19
Polling Engine Shutdown, Monitoring Stopped, System Error, Warning -- or Fail Over
System Warning; Node, Interface, or Volume Changed; Warning -- Interface Reappeared; Network Baseline Started/Finished
Node or Interface is Up OK 1
Dormant OK 6
Active OK 22
Inactive OK 24
Expired OK 25
Unknown Ignore 0
Node or Interface is Unmanaged Ignore 9
Interface is Unplugged but not Down Ignore 10
page 112 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
I STATUS INDICATION CON
Node is defined as External Ignore 11
(Node is not monitored by Orion NPM, but an application on the node may be monitored by Orion APM.)
Monitoring Disabled Ignore 26
Disabled Ignore 27
Not Licensed Ignore 28
Informational; Volume Reappeared N/A --
Monitoring Started, NPM Service Started, or Fail Back N/A --
Node, Interface, or Volume Removed N/A --
Interface Shutdown
Node Added N/A --
Interface or Volume Added (System Manager)
Interface or Volume Added (Web Console) N/A --
Node Rebooted N/A --
Interface Enabled N/A --
Interface Remapped N/A --
Volume Remapped N/A --
Interface or Volume Disappeared N/A --
STATUS ROLLUP MODE
In the Web Console, the Status Roll-up Mode designates how the availability status of a group of nodes is displayed. Three options are available for the case when there are objects at different status levels in a selected group:
Show Best Status is most useful for displaying groups that are defined as collections of redundant or backup devices. The following table indicates how the Show Best Status option operates:
Note: Compare Group Status results under the Show Best Status option with results for the same groups of objects under the Show Worst Status option.
page 113 OBJECT STATES GROUP STATUS
(Up, Warning, Down) (Up)
(Warning, Down) (Up)
(Warning, Down, Unknown) (Warning)
Show Worst Status ensures that the worst status in a group of objects is displayed for the whole group. The following table indicates how the Show Worst Status option operates:
OBJECT STATES GROUP STATUS
(Up, Warning, Down) (Down)
(Warning, Down) (Warning)
(Warning, Down, Unknown) (Down)
Mixed Status shows Warning ensures that the status of a group displays the worst warning-type state in the group. If there are no warning-type states, but the group contains a mix of up and down states, then a Mixed Availability ( ) warning status is displayed for the whole group. The following table indicates how the Mixed Status shows Warning option operates:
OBJECT STATES GROUP STATUS
(Critical)
(Critical)
(Mixed Availability)
WPM alert variables
This section contains the variables that can be used when creating Alert messages for WPM objects:
l WPM transaction alert variables
l WPM transaction step alert variables
l WPM step request alert variables
l WPM player location alert variables
page 114 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
WPM TRANSACTION ALERT VARIABLES
Description Variable
Average Load Percentage (Last 30 minutes) ${N=SwisEntity;M=Agent.AvgLoadPercentageLast30min} (Player Location)
Average Load Percentage (Last 60 minutes) ${N=SwisEntity;M=Agent.AvgLoadPercentageLast60min} (Player Location)
Connect Status (Player Location) ${N=SwisEntity;M=Agent.ConnectionStatus}
Critical Threshold ${N=SwisEntity;M=CriticalThreshold}
Description ${N=SwisEntity;M=Description}
Description (Agent Connection Status) ${N=SwisEntity;M=Agent.ConnectionStatusInfo.Description}
Description (Player Location) ${N=SwisEntity;M=Agent.Description}
Description (Recording Custom Properties) ${N=SwisEntity;M=Recording.CustomProperties.Description}
Description (Recording) ${N=SwisEntity;M=Recording.Description}
Description (Transaction Custom Properties) ${N=SwisEntity;M=CustomProperties.Description}
DNS Name (Player Location) ${N=SwisEntity;M=Agent.DNSName}
Hostname (Player Location) ${N=SwisEntity;M=Agent.Hostname}
In Cloud (Player Location) ${N=SwisEntity;M=Agent.InCloud}
IP Address (Player Location) ${N=SwisEntity;M=Agent.IP}
Is Managed Again ${N=SwisEntity;M=IsEnabled}
Is Player Initiated Communication (Player ${N=SwisEntity;M=Agent.IsActiveAgent} Location)
Last Duration ${N=SwisEntity;M=LastDuration}
Last Error Message ${N=SwisEntity;M=LastErrorMessage}
Last Played ${N=SwisEntity;M=LastPlayedUtc}
Load Percentage (Player Location) ${N=SwisEntity;M=Agent.LoadPercentage}
Name ${N=SwisEntity;M=Name}
Name (Player Location) ${N=SwisEntity;M=Agent.Name}
Name (Recording) ${N=SwisEntity;M=Recording.Name}
Number of Managed Transactions (Player ${N=SwisEntity;M=Agent.NumManagedTransactions}
page 115 Description Variable
Location)
Number of Transactions (Player Location) ${N=SwisEntity;M=Agent.NumAllTransactions}
OS Version (Player Location) ${N=SwisEntity;M=Agent.OSVersion}
Password (Player Location) ${N=SwisEntity;M=Agent.Password}
Playback Interval ${N=SwisEntity;M=Frequency}
Player Location ID ${N=SwisEntity;M=AgentId}
Player Location ID (Player Location) ${N=SwisEntity;M=Agent.AgentId}
Player Version (Player Location) ${N=SwisEntity;M=Agent.AgentVersion}
Port (Player Location) ${N=SwisEntity;M=Agent.Port}
Proxy Password (Player Location) ${N=SwisEntity;M=Agent.ProxyPassword}
Proxy URL (Player Location) ${N=SwisEntity;M=Agent.ProxyUrl}
Proxy Username (Player Location) ${N=SwisEntity;M=Agent.ProxyUserName}
RDP Enabled (Player Location) ${N=SwisEntity;M=Agent.RDPEnabled
Recording Custom Property ${N=SwisEntity;M=Recording.CustomProperties.custom_property_ name}
Recording ID ${N=SwisEntity;M=RecordingId}
Recording ID (Recording) ${N=SwisEntity;M=Recording.RecordingId}
Requires Interactive Session ${N=SwisEntity;M=Recording.RequiresInteractiveSession}
Short Description (Agent Connection Status) ${N=SwisEntity;M=Agent.ConnectionStatusInfo.ShortDescription}
Status ${N=SwisEntity;M=Status}
Status (Player Location) ${N=SwisEntity;M=Agent.Status}
Status Description ${N=SwisEntity;M=StatusDescription}
Status Description (Player Location) ${N=SwisEntity;M=Agent.StatusDescription}
Status ID (Agent Connection Status) ${N=SwisEntity;M=Agent.ConnectionStatusInfo.StatusId}
Transaction Custom Property ${N=SwisEntity;M=CustomProperties.custom_property_name}
Transaction ID ${N=SwisEntity;M=TransactionId}
Unmanage From ${N=SwisEntity;M=UnManageFrom}
page 116 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Description Variable
Unmanage From (Player Location) ${N=SwisEntity;M=Agent.UnManageFrom}
Unmanage To ${N=SwisEntity;M=UnManageUntil}
Unmanage To (Player Location) ${N=SwisEntity;M=Agent.UnManageUntil}
Unmanaged ${N=SwisEntity;M=Agent.UnManageUntil}
Unmanaged (Player Location) ${N=SwisEntity;M=Agent.Unmanaged}
Url (Player Location) ${N=SwisEntity;M=Agent.Url}
Uses Proxy (Player Location) ${N=SwisEntity;M=Agent.UseProxy}
Uses Proxy Authentication (Player Location) ${N=SwisEntity;M=Agent.UseProxyAuthentication}
Warning Threshold ${N=SwisEntity;M=WarningThreshold}
WPM TRANSACTION STEP ALERT VARIABLES
Description Variable
Average Load Percentage (Last 30 ${N=SwisEntity;M=Transaction.Agent.AvgLoadPercentageLast30min} minutes) (Player Location)
Average Load Percentage (Last 60 ${N=SwisEntity;M=Transaction.Agent.AvgLoadPercentageLast60min} minutes) (Player Location)
Connect Status (Player Location) ${N=SwisEntity;M=Transaction.Agent.ConnectionStatus}
Connection Status Message (Player ${N=SwisEntity;M=Transaction.Agent.ConnectionStatusMessage} Location)
Critical Threshold ${N=SwisEntity;M=CriticalThreshold}
Critical Threshold (Recording step) ${N=SwisEntity;M=Step.CriticalThreshold}
Critical Threshold (Transaction) ${N=SwisEntity;M=Transaction.CriticalThreshold}
Description ${N=SwisEntity;M=Description}
Description (Agent Connection ${N=SwisEntity;M=Transaction.Agent.ConnectionStatusInfo.Description} Status)
Description (Player Location) ${N=SwisEntity;M=Transaction.Agent.Description}
Description (Recording Custom ${N=SwisEntity;M=Recording.CustomProperties.Description} Properties)
Description (Recording Custom ${N=SwisEntity;M=Step.Recording.CustomProperties.Description} Properties) page 117 Description Variable
Description (Recording) ${N=SwisEntity;M=Recording.Description}
Description (Recording) ${N=SwisEntity;M=Step.Recording.Description}
Description (Transaction Custom ${N=SwisEntity;M=CustomProperties.Description} Properties)
Description (Transaction) ${N=SwisEntity;M=Transaction.Description}
DNS Name (Player Location) ${N=SwisEntity;M=Transaction.Agent.DNSName}
Hostname (Player Location) ${N=SwisEntity;M=Transaction.Agent.Hostname}
In Cloud (Player Location) ${N=SwisEntity;M=Transaction.Agent.InCloud}
IP Address (Player Location) ${N=SwisEntity;M=Transaction.Agent.IP}
Is Managed Again ${N=SwisEntity;M=IsEnabled}
Is Player Initiated Communication ${N=SwisEntity;M=Transaction.Agent.IsActiveAgent} (Player Location)
Last Duration ${N=SwisEntity;M=LastDuration}
Last Duration (Transaction) ${N=SwisEntity;M=Transaction.LastDuration}
Last Error Message ${N=SwisEntity;M=LastErrorMessage}
Last Error Message (Transaction) ${N=SwisEntity;M=Transaction.LastErrorMessage}
Last Played ${N=SwisEntity;M=LastPlayedUtc}
Last Played (Transaction) ${N=SwisEntity;M=Transaction.LastPlayedUtc}
Load Percentage (Player Location) ${N=SwisEntity;M=Transaction.Agent.LoadPercentage}
Name (Player Location) ${N=SwisEntity;M=Transaction.Agent.Name}
Name (Recording Step) ${N=SwisEntity;M=Step.Name}
Name (Recording) ${N=SwisEntity;M=Recording.Name}
Name Recording) ${N=SwisEntity;M=Transaction.Recording.Name
Name (Transaction) ${N=SwisEntity;M=Step.Recording.Name}
Number of Managed Transactions ${N=SwisEntity;M=Transaction.Agent.NumManagedTransactions} (Player Location)
Number of Transactions (Player ${N=SwisEntity;M=Transaction.Agent.NumAllTransactions} Location)
page 118 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Description Variable
Optimal Threshold ${N=SwisEntity;M=OptimalThreshold}
OS Version (Player Location) ${N=SwisEntity;M=Transaction.Agent.OSVersion}
Password (Player Location) ${N=SwisEntity;M=Transaction.Agent.Password}
Playback Interval ${N=SwisEntity;M=Frequency}
Player Location ID (Player Location) ${N=SwisEntity;M=Transaction.Agent.AgentId}
Player Location (Transaction) ${N=SwisEntity;M=Transaction.AgentId}
Player Version (Player Location) ${N=SwisEntity;M=Transaction.Agent.AgentVersion}
Port (Player Location) ${N=SwisEntity;M=Transaction.Agent.Port}
Proxy Password (Player Location) ${N=SwisEntity;M=Transaction.Agent.ProxyPassword}
Proxy URL (Player Location) ${N=SwisEntity;M=Transaction.Agent.ProxyUrl}
Proxy Username (Player Location) ${N=SwisEntity;M=Transaction.Agent.ProxyUserName}
RDP Enabled (Player Location) ${N=SwisEntity;M=Transaction.Agent.RDPEnabled
Recording Custom Property ${N=SwisEntity;M=Recording.CustomProperties.custom_property_name}
Recording ID ${N=SwisEntity;M=RecordingId}
Recording ID (Recording Step) ${N=SwisEntity;M=Transaction.AgentId}
Recording ID (Recording) ${N=SwisEntity;M=Recording.RecordingId}
Recording ID (Recording) ${N=SwisEntity;M=Transaction.Recording.RecordingId}
Recording ID (Transaction) ${N=SwisEntity;M=Transaction.RecordingId}
Recording Step ID ${N=SwisEntity;M=StepId}
Requires Interactive Session ${N=SwisEntity;M=Recording.RequiresInteractiveSession} (Recording)
Requires Interactive Session ${N=SwisEntity;M=Step.Recording.RequiresInteractiveSession} (Recording)
Short Description (Agent Connection ${N=SwisEntity;M=Transaction.Agent.ConnectionStatusInfo.ShortDescription} Status)
Status ${N=SwisEntity;M=Status}
Status (Player Location) ${N=SwisEntity;M=Transaction.Agent.Status}
page 119 Description Variable
Status (Transaction) ${N=SwisEntity;M=Transaction.Status}
Status Description ${N=SwisEntity;M=StatusDescription}
Status Description (Player Location) ${N=SwisEntity;M=Transaction.Agent.StatusDescription}
Status Decription (Transaction) ${N=SwisEntity;M=Transaction.StatusDescription}
Status ID (Agent Connection Status) ${N=SwisEntity;M=Transaction.Agent.ConnectionStatusInfo.StatusId}
Status ID (Recording Step) ${N=SwisEntity;M=Step.StepId}
Transaction Custom Property ${N=SwisEntity;M=CustomProperties.custom_property_name}
Transaction ID ${N=SwisEntity;M=TransactionId}
Transaction ID (Transaction) ${N=SwisEntity;M=Transaction.TransactionId}
Transaction Step ID ${N=SwisEntity;M=TransactionStepId}
Unmanage From ${N=SwisEntity;M=UnManageFrom}
Unmanage From (Player Location) ${N=SwisEntity;M=Transaction.Agent.UnManageFrom}
Unmanage From (Transaction) ${N=SwisEntity;M=Transaction.UnManageFrom}
Unmanage To ${N=SwisEntity;M=UnManageUntil}
Unmanage To (Player Location) ${N=SwisEntity;M=Transaction.Agent.UnManageUntil}
Unmange To (Transaction) ${N=SwisEntity;M=Transaction.UnManageUntil}
Unmanaged ${N=SwisEntity;M=Transaction.Agent.UnManageUntil}
Unmanaged (Player Location) ${N=SwisEntity;M=Transaction.Agent.Unmanaged}
Unmanaged (Transaction) ${N=SwisEntity;M=Transaction.UnManaged}
Url (Player Location) ${N=SwisEntity;M=Transaction.Agent.Url}
Url (Recording Step) ${N=SwisEntity;M=Step.Url}
Uses Proxy (Player Location) ${N=SwisEntity;M=Transaction.Agent.UseProxy}
Uses Proxy Authentication (Player ${N=SwisEntity;M=Transaction.Agent.UseProxyAuthentication} Location)
Warning Threshold ${N=SwisEntity;M=WarningThreshold}
Warning Threshold (Recording Step) ${N=SwisEntity;M=Step.WarningThreshold}
Warning Threshold (Transaction) ${N=SwisEntity;M=Transaction.WarningThreshold}
page 120 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
WPM STEP REQUEST ALERT VARIABLES
Description Variable
Average Load ${N=SwisEntity;M=TransactionStep.Transaction.Agent.AvgLoadPercentageLast30min} Percentage (Last 30 minutes) (Player Location)
Average Load ${N=SwisEntity;M=TransactionStep.Transaction.Agent.AvgLoadPercentageLast60min} Percentage (Last 60 minutes) (Player Location)
Blocked Duration ${N=SwisEntity;M=BlockedDurationMs}
Connection Begin ${N=SwisEntity;M=ConnectionBeginMs}
Connection ${N=SwisEntity;M=ConnectionDurationMs} Duration
Connect Status ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ConnectionStatus} (Player Location)
Connection Status ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ConnectionStatusMessage} Message (Player Location)
Critical Threshold ${N=SwisEntity;M=TransactionStep.Step.CriticalThreshold} (Recording step)
Critical Threshold ${N=SwisEntity;M=TransactionStep.CriticalThreshold} (Transaction Step)
Critical Threshold ${N=SwisEntity;M=TransactionStep.Transaction.CriticalThreshold} (Transaction)
Description ${N=SwisEntity;M=Description}
Description (Agent ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ConnectionStatusInfo.Description} Connection Status)
Description (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Description} Location)
Description ${N=SwisEntity;M=TransactionStep.Transaction.Recording.CustomProperties.Description} (Recording Custom Properties)
Description ${N=SwisEntity;M=TransactionStep.Step.Recording.CustomProperties.Description}
page 121 Description Variable
(Recording Custom Properties)
Description ${N=SwisEntity;M=TransactionStep.Step.Description} (Recording Step)
Description ${N=SwisEntity;M=TransactionStep.Transaction.Recording.Description} (Recording)
Description ${N=SwisEntity;M=TransactionStep.Step.Recording.Description} (Recording)
Description ${N=SwisEntity;M=TransactionStep.Transaction.CustomProperties.Description} (Transaction Custom Properties)
Description ${N=SwisEntity;M=TransactionStep.Description} (Transacription Step)
Description ${N=SwisEntity;M=TransactionStep.Transaction.Description} (Transaction)
DNS Begin ${N=SwisEntity;M=DNSBeginMs}
DNS Name (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.DNSName} Location)
DNS Resolution ${N=SwisEntity;M=DNSResolutionDurationMs} Duration
Download Duration ${N=SwisEntity;M=DownloadDurationMs}
Hostname (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Hostname} Location)
In Cloud (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.InCloud} Location)
IP Address (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.IP} Location)
Is Managed Again ${N=SwisEntity;M=TransactionStep.Transaction.IsEnabled} (Transaction)
Is Player Initiated ${N=SwisEntity;M=TransactionStep.Transaction.Agent.IsActiveAgent} Communication
page 122 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Description Variable
(Player Location)
Last Duration ${N=SwisEntity;M=TransactionStep.LastDuration} (Transaction Step)
Last Duration ${N=SwisEntity;M=TransactionStep.Transaction.LastDuration} (Transaction)
Last Error Message ${N=SwisEntity;M=TransactionStep.LastErrorMessage} (Transaction Step)
Last Error Message ${N=SwisEntity;M=TransactionStep.Transaction.LastErrorMessage} (Transaction)
Last Played ${N=SwisEntity;M=TransactionStep.LastPlayedUtc} (Transaction Step)
Last Played ${N=SwisEntity;M=TransactionStep.Transaction.LastPlayedUtc} (Transaction)
Load Percentage ${N=SwisEntity;M=TransactionStep.Transaction.Agent.LoadPercentage} (Player Location)
MimeType ${N=SwisEntity;M=MimeType}
Name (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Name} Location)
Name (Recording ${N=SwisEntity;M=TransactionStep.Step.Name} Step)
Name (Recording) ${N=SwisEntity;M=TransactionStep.Transaction.Recording.Name}
Name Recording) ${N=SwisEntity;M=TransactionStep.Step.Recording.Name}
Name (Transaction) ${N=SwisEntity;M=TransactionStep.Transaction.Name}
Number of ${N=SwisEntity;M=TransactionStep.Transaction.Agent.NumManagedTransactions} Managed Transactions (Player Location)
Number of ${N=SwisEntity;M=TransactionStep.Transaction.Agent.NumAllTransactions} Transactions (Player Location)
Optimal Threshold ${N=SwisEntity;M=TransactionStep.OptimalThreshold} (Transaction Step)
page 123 Description Variable
OS Version (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.OSVersion} Location)
Password (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Password} Location)
Playback Interval ${N=SwisEntity;M=TransactionStep.Transaction.Frequency} (Transaction)
Player Location ID ${N=SwisEntity;M=TransactionStep.Transaction.Agent.AgentId} (Player Location)
Player Location ${N=SwisEntity;M=TransactionStep.Transaction.AgentId} (Transaction)
Player Version ${N=SwisEntity;M=TransactionStep.Transaction.Agent.AgentVersion} (Player Location)
Port (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Port} Location)
Proxy Password ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ProxyPassword} (Player Location)
Proxy URL (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ProxyUrl} Location)
Proxy Username ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ProxyUserName} (Player Location)
RDP Enabled ${N=SwisEntity;M=TransactionStep.Transaction.Agent.RDPEnabled (Player Location)
Recording Custom ${N=SwisEntity;M=Recording.CustomProperties.recording_property_name} Property
Receive Begin ${N=SwisEntity;M=ReceiveBeginMs}
Receive End ${N=SwisEntity;M=ReceiveEndMs}
Recording ID ${N=SwisEntity;M=TransactionStep.Step.RecordingId} (Recording Step)
Recording ID ${N=SwisEntity;M=TransactionStep.Transaction.Recording.RecordingId} (Recording)
Recording ID ${N=SwisEntity;M=TransactionStep.Step.Recording.RecordingId} (Recording)
page 124 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Description Variable
Recording ID ${N=SwisEntity;M=TransactionStep.Recording.RecordingId} (Transaction Step) Step Request
Recording ID ${N=SwisEntity;M=TransactionStep.Transaction.RecordingId} (Transaction)
Recording Step ID ${N=SwisEntity;M=TransactionStep.StepId} (Transaction Step)
Request Begin ${N=SwisEntity;M=RequestBeginMs}
Request Index ${N=SwisEntity;M=RequestIndex}
Requires Interactive ${N=SwisEntity;M=TransactionStep.Transaction.Recording.RequiresInteractiveSession} Session (Recording)
Requires Interactive ${N=SwisEntity;M=TransactionStep.Step.Recording.RequiresInteractiveSession} Session (Recording)
Send Begin ${N=SwisEntity;M=SendBeginMs}
Send Duration ${N=SwisEntity;M=SendDurationMs}
Send End ${N=SwisEntity;M=SendEndMs}
Short Description ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ConnectionStatusInfo.ShortDescription} (Agent Connection Status)
Size ${N=SwisEntity;M=Size}
Status (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Status} Location)
Status (Transaction ${N=SwisEntity;M=TransactionStep.Status} Step)
Status (Transaction) ${N=SwisEntity;M=TransactionStep.Transaction.Status}
Status Code ${N=SwisEntity;M=StatusCode}
Status Description ${N=SwisEntity;M=TransactionStep.Transaction.Agent.StatusDescription} (Player Location)
Status Description ${N=SwisEntity;M=TransactionStep.StatusDescription} (Transaction Step)
page 125 Description Variable
Status Decription ${N=SwisEntity;M=TransactionStep.Transaction.StatusDescription} (Transaction)
Status ID (Agent ${N=SwisEntity;M=TransactionStep.Transaction.Agent.ConnectionStatusInfo.StatusId} Connection Status)
Step Full Name ${N=SwisEntity;M=StepFullName}
Step ID (Recording ${N=SwisEntity;M=TransactionStep.Step.StepId} Step)
Step Order ${N=SwisEntity;M=TransactionStep.Step.StepOrder} (Recorder Step)
Time to First Byte ${N=SwisEntity;M=TimeToFirstByteDurationMs}
Total Duration ${N=SwisEntity;M=TotalDurationMs}
Transaction Custom ${N=SwisEntity;M=CustomProperties.transaction_property_name} Property
Transaction ID ${N=SwisEntity;M=TransactionId}
Transaction ID ${N=SwisEntity;M=TransactionStep.TransactionId} (Transaction Step)
Transaction ID ${N=SwisEntity;M=TransactionStep.Transaction.TransactionId} (Transaction)
Transaction Step ID ${N=SwisEntity;M=TransactionStepId}
Transaction Step ID ${N=SwisEntity;M=TransactionStep.TransactionStepId} (Transaction Step)
Transaction Step ID ${N=SwisEntity;M=TransactionStepRequestId} (Transaction)
Transaction Step ${N=SwisEntity;M=TransactionStepRequestId} Request ID
Unmanage From ${N=SwisEntity;M=TransactionStep.Transaction.Agent.UnManageFrom} (Player Location)
Unmanage From ${N=SwisEntity;M=TransactionStep.UnManageFrom} (Transaction Step)
Unmanage From ${N=SwisEntity;M=TransactionStep.Transaction.UnManageFrom} (Transaction)
page 126 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Description Variable
Unmanage To ${N=SwisEntity;M=TransactionStep.Transaction.Agent.UnManageUntil} (Player Location)
Unmanage To ${N=SwisEntity;M=TransactionStep.UnManageUntil} (Transaction Step)
Unmanage To ${N=SwisEntity;M=TransactionStep.Transaction.UnManageUntil} (Transaction)
Unmanaged (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Unmanaged} Location)
Unmanaged ${N=SwisEntity;M=TransactionStep.UnManaged} (Transaction Step)
Unmanaged ${N=SwisEntity;M=TransactionStep.Transaction.UnManaged} (Transaction)
Url ${N=SwisEntity;M=Url}
Url (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.Url} Location)
Url (Recording Step) ${N=SwisEntity;M=TransactionStep.Step.Url}
Uses Proxy (Player ${N=SwisEntity;M=TransactionStep.Transaction.Agent.UseProxy} Location)
Uses Proxy ${N=SwisEntity;M=TransactionStep.Transaction.Agent.UseProxyAuthentication} Authentication (Player Location)
Warning Threshold ${N=SwisEntity;M=TransactionStep.Step.WarningThreshold} (Recording Step)
Warning Threshold ${N=SwisEntity;M=TransactionStep.WarningThreshold} (Transaction Step)
Warning Threshold ${N=SwisEntity;M=TransactionStep.Transaction.WarningThreshold} (Transaction)
WPM PLAYER LOCATION ALERT VARIABLES
Description Variable
Average Load Percentage (Last 30 minutes) ${N=SwisEntity;M=AvgLoadPercentageLast30min}
page 127 Description Variable
Average Load Percentage (Last 60 minutes) ${N=SwisEntity;M=AvgLoadPercentageLast60min}
Connect Status ${N=SwisEntity;M=ConnectionStatus}
Connection Status Message ${N=SwisEntity;M=ConnectionStatusMessage}
Description ${N=SwisEntity;M=Description}
Description (Agent Connection Status) ${N=SwisEntity;M=ConnectionStatusInfo.Description}
DNS Name ${N=SwisEntity;M=DNSName}
Hostname ${N=SwisEntity;M=Hostname}
In Cloud ${N=SwisEntity;M=InCloud}
IP Address ${N=SwisEntity;M=IP}
Is Player Initiated Communication ${N=SwisEntity;M=IsActiveAgent}
Load Percentage ${N=SwisEntity;M=LoadPercentage}
Name ${N=SwisEntity;M=Name}
Number of Managed Transactions ${N=SwisEntity;M=NumManagedTransactions}
Number of Transactions ${N=SwisEntity;M=NumAllTransactions}
OS Version ${N=SwisEntity;M=OSVersion}
Password ${N=SwisEntity;M=Password}
Player Location ID ${N=SwisEntity;M=AgentId}
Player Version ${N=SwisEntity;M=AgentVersion}
Port ${N=SwisEntity;M=Port}
Proxy Password ${N=SwisEntity;M=ProxyPassword}
Proxy URL ${N=SwisEntity;M=ProxyUrl}
Proxy Username ${N=SwisEntity;M=ProxyUserName}
RDP Enabled ${N=SwisEntity;M=RDPEnabled
Short Description (Agent Connection Status) ${N=SwisEntity;M=ConnectionStatusInfo.ShortDescription}
Status ${N=SwisEntity;M=Status}
Status Description ${N=SwisEntity;M=StatusDescription}
page 128 ADMINISTRATOR GUIDE: WEB PERFORMANCE MONITOR
Description Variable
Status ID (Agent Connection Status) ${N=SwisEntity;M=ConnectionStatusInfo.StatusId}
Unmanage From ${N=SwisEntity;M=UnManageFrom}
Unmanage To ${N=SwisEntity;M=UnManageUntil}
Unmanaged ${N=SwisEntity;M=Unmanaged}
Url ${N=SwisEntity;M=Url}
Uses Proxy ${N=SwisEntity;M=UseProxy}
Use Proxy Authenticity ${N=SwisEntity;M=UseProxyAuthentication}
page 129