Chat now with support
Chat with Support

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

Use Error Overrides

When an FTR script is playing back and error codes are encountered, they can stop the script from running and appear in the Results dialog.

Figure 49. Example of error codes

You can override errors by setting them as an information message by using the Error Override feature.

To add an error override:
1
Select the root of the script.
2
In the Common Properties window, click the Error Overrides ellipse button.
The Error Overrides dialog displays.
3
Click Add.
4
Enter the error number (for example 0x80004005) and set the Severity to the required level.
5
Click OK.
When the script is played again, the error message is reported with the selected severity and the script continues to play.

Insert validation rules

Validation rules allow you to verify that a web page loaded properly. A validation rule can be created to verify the properties of any HTML elements. A wizard allows you to create validation rules for:

•
Anchors
•
Images
•
Frames
•
HTML source/text validation

This wizard is available during recording or during playback when a script is paused. All Validation rules are converted into Javascript instructions.

Figure 50. Validation Rules dialog box

 
* 
NOTE: Execution of numerous validation rules can be CPU intensive. It is advisable to create the minimal amount of validation rules that ensure your script is executing correctly.
To validate a rule:
1
Click the New Validation Rule icon .
2
Click New.
3
Select the desired rule (anchor, images, frames, or source).
4
Click Next.
The JavaScript Validation Rule dialog displays.
5
Accept the default rule name.
6
Click Next.
7
Select the severity level by deciding if failing this validation results in an information, warning, or error condition. Script execution halts on an error condition, but warning and information messages are logged and the script allowed to continue.
8
Click Next.
9
Select the anchors, images, frames or text to validate.
10
Click Finish.
11
Create additional rules if required.
12
Click OK when all validations are created.

Insert Transactions

 
* 
NOTE: Transactions cannot be inserted when the root of the Script Window is selected.

Transactions can be used to create a logical grouping of instructions into business processes, such as logging on, running a report, and logging off.

Figure 51. Insert Transactions dialog box

Expected Time

Expected Time is the amount of time a transaction can take before it exceeds a Service Level Agreement requirement. When the expected time is exceeded, an error is logged.

To create a transaction:
1
Select one or more instructions in the Script Window.
2
Click the Transaction icon .
The New Transaction dialog displays.
3
Enter the transaction name.
4
Set the appropriate Expected Time.
5
Click OK.

Rebaseline a script

When a script is rebaselined, the time-out and expected times are cleared and the script is replayed. Upon completion of the script, the Expected Time Wizard displays, allowing you to adjust the expected times and time-out for the script.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating