Unsupported contentThis version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Synthetic transaction monitoring

You use synthetic transaction monitoring to predict application health and user experience. App Visibility enables you to manage the performance and reliability of your applications by executing complex business transactions and monitoring performance and functional behavior. Synthetic transaction monitoring enables your business to proactively check service level agreements (SLAs) and receive notification of a breach before the end user is impacted. The following tables explains some of the basic concepts that you need to understand App Visibility's synthetic transaction monitoring:

Concept

Description

Synthetic transaction scripts

A transaction script is a sequence of instructions that simulate user transactions. BMC Synthetic Transaction Monitoring uses prerecorded .ltz scripts to simulate end-user transactions, and BMC provides some basic scripts. You can create realistic and customizable scripts through an external scripting tool and then upload, deploy, and manage the scripts in the Operations Management console.

The scripting tool, Borland Silk Performer Synthetic Transaction Monitoring for BMC Software, also serves as an execution module to run scripts on the computer with the BMC Synthetic Transaction Execution Adapter (TEA) Agent. Each computer with the TEA Agent requires an execution module to run the scripts. On each TEA Agent computer, you can install the full Silk Performer installation, a smaller execution-module-only installation, or TrueLog Explorer, which supports Silk Performer testing efforts with a framework from which you can customize test scripts and view execution log results.

For details about working with synthetic transaction scripts, see Using-scripts-to-simulate-end-user-transactions.

Location

A location is a logical group of TEA Agents, grouped for load balancing and high availability, and according to the needs of your organization. Each script is run on one Agent in a location. If several scripts are run on the same location, the scripts are distributed evenly across the location.

Each TEA Agent is assigned to a location during Agent installation.

Execution Plan

An Execution Plan provides the interface for a script and its execution. Through an Execution Plan, you specify the configuration for the script (including custom attributes), locations on which the script runs, run schedules, and blackout periods.

For details about working with Execution Plans, see Viewing-an-application-s-synthetic-settings and Editing-an-application-s-synthetic-settings.

Execution

An execution is the result of a single instance of a script run according to the parameters set in the associated Execution Plan. Each execution may contain one or more transactions. Executions are simulations of end-user processes, and are used to detect issues that might occur before the real end users encounter them.

Failed to execute the [export-ignore] macro. Cause: [Missing macro content: this macro requires content (a body)]. Click on this message for details.

 

Related topics

Setting-up-and-managing-synthetic-transaction-monitoring

Monitoring-synthetic-transactions-to-predict-application-health

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*