Converse agora com nosso suporte
Chat com o suporte

Foglight Transaction Recorder 5.6.13 - Recorder User Guide

Overview of Foglight synthetic monitoring Use the Foglight Transaction Recorder Create and upload Foglight Transaction Recorder scripts View Foglight Transaction Recorder results Settings How Do I... Appendix: Best practices Appendix: Troubleshoot the Foglight Transaction Recorder Appendix: API for FTR Timer Usage

Turn on Tag and Follow before the recording process begins

1
Click Tools > Settings.
2
Click Recorder > HTML.
3
Set Tag and Follow to True.
4
Click OK.

Insert an Internet Instruction and turn on Tag and Follow after a script is recorded

* 
NOTE: If you already have an Internet Instruction in the script, you only need to set the Tag and Follow property to True.
1
Click the icon on the Script Window toolbar. The Insert Wizard displays. Edit the Internet Settings instruction only if it doesn't exist in a script.
2
Click the Internet Settings property.
3
Set the Tag and Follow property to True.
4
Click OK.

Scale Foglight Transaction Player client machines

One of the goals of Transaction Player agents is to measure the response time of the monitored system. A client machine that is running more concurrent scripts than can be supported by the hardware reports slower response times than are being experienced by users. Therefore, it is important to understand the effects of overloading a Transaction Player client machine.

Script playback can be both CPU and memory intensive, depending on the length of the script, and the size and complexity of the web pages. Complex pages require more CPU resources to parse the page elements. Larger pages require more memory to temporarily store the results. Due to the dynamic nature of the scripts and the data being gathered, results are stored in memory until the script completes and are then written to disk. Therefore, longer scripts with complex pages can require large amounts of memory. Scripts running over secure connections (HTTPS) require the decryption of each page which can severely load the CPU.

As a client machine is configured to run additional scripts, the user should monitor CPU usage. This can be done in the Intelligent Agent or simply by looking at the performance in Task Manager. The CPU can be expected to spike at the beginning and end of a script execution, but should not remain pegged at 100% or maxed out.

When CPU saturation occurs, in most cases the CPU is simply overloaded. An additional client machine must be configured for monitoring and some of the scripts moved to the new machine. Other conditions that create a heavy load on the CPU are insufficient memory and heavy use of the system paging file. Combining the CPU requirements of Transaction Player with heavy paging can result in a CPU being pegged at 100% and staying there for long periods. In this condition, the response times reported by the agent are slower than those being experienced by users.

Before configuring a new client machine, the user should examine the use of the page file, and determine if more memory can resolve performance problems. If the client machine is Windows 2000 or 2003, the Foglight NT System agent can provide this information. Otherwise, Task Manager or Performance Manager shows this information. The key metric is Page Faults, which tells the user how frequently the machine has to go to the disk to swap memory.

Another option is to disable network statistic collection in the Intelligent Agent. This feature stores a tremendous amount of timing detail for each page in a script. Although this feature can be useful for isolating problems, CPU and memory usage can be reduced significantly by turning this feature off.

Set the Recording Method dialog

During the Foglight Transaction Recorder recording process, the Recording Method dialog displays and you can:

•
Record as a New User—selecting this option records an FTR script as a user who has never been to this Web site before. No cookies exist.
•
Record as an Existing User—selecting this option utilizes cookies that exist for the user currently logged into a machine.
Figure 60. Recording method dialog box

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação