Synthetic transaction query parameter reference


Tip

This topic is for users of BMC Synthetic End User Experience Monitoring version 2.5.00. For version 2.5.01, see Synthetic-transaction-POST-parameter-reference.

This topic presents the query parameters that are specific to synthetic transactions. Use these parameters to filter synthetic transactions and create rules, such as error detection rules, for the information that is most relevant to your environment. The filtered results are displayed in the Real User Analyzer at the page level. To configure the system to display the the parameters, see Configuring-a-confidentiality-policy-for-synthetic-transactions.

URI stem for synthetic transactions

For synthetic transactions, the URI stem always consist of the following elements:

<teaAgentIP>/bmc-synthetic-1.0/<businessServiceName>/<executionPlanName>

  • <teaAgentIP> represents the IP address of the TEA Agent
  • <businessServiceName> represents the name of the Business Service
  • <executionPlanName> represents the name of the Execution Plan

Query parameters for synthetic transactions

Query parameter

Value

bmc_syn_tea_id

ID of the TEA Agent. You can see this ID number by hovering over the Agent name in the  Transaction Execution Adapter Agents window.

bmc_syn_tea_name

Name of the TEA Agent

bmc_syn_tea_group_id

ID of the Agent Group. You can see this ID number by hovering over the Agent Group name in the TEA Agent Groups window.

bmc_syn_tea_group

Name of the Agent Group

bmc_syn_bs_id

ID of the Business Service. You can see this ID number by hovering over the Business Service name in the Business Services window.

bmc_syn_bs

Name of the Business Service

bmc_syn_ep_id

ID of the Execution Plan. You can see this ID number by hovering over the Execution Plan name in the Execution Plans window.

bmc_syn_ep

Name of the Execution Plan

bmc_syn_tn_id

ID of the transaction

bmc_syn_tn

Script (BDF) file name. The TEA Agent executes the default script defined in the project (LTP) file.*

bmc_syn_sub_tn

Transaction in the script (BDF) file, such as TINIT, or TMAIN.*

bmc_syn_av_err

Number of availability errors in the transaction

bmc_syn_acc_err

Number of accuracy errors in the transaction

bmc_syn_exec_err

ID of the execution error in the transaction

* The scripting utility creates an LTZ archive file. The archive file contains the LTP project file, which holds BDF script file. For information, refer to BMC TM ART Monitor Workbench documentation.

The following example displays the query parameters for a synthetic transaction:

Example

192.0.32.10/bmc-synthetic-1.0/My Business Service/My Execution Plan?bmc_syn_tea_id=4&
bmc_syn_tea_name=My Agent&bmc_syn_tea_group_id=1&bmc_syn_tea_group=MyGroup&
bmc_syn_bs_id=1&bmc_syn_bs=My Business Service&bmc_syn_ep_id=112&
bmc_syn_ep=My Execution Plan&bmc_syn_tn_id=1&bmc_syn_tn=UrlCheck&
bmc_syn_sub_tn=UrlCheck&bmc_syn_av_err=2&bmc_syn_acc_err=0&bmc_syn_exec_err=0

You can use the query parameters to create Watchpoints, as shown in the following examples:

Examples
  • To configure a Watchpoint for the "PetRocks Dealer Portal" Execution Plan, use the following filter:
    (url.stem_string contains "bmc-synthetic-1.0" ignorecase) AND (url.query_param("bmc_syn_ep") is “PetRocks Dealer Portal")
  • To configure a Watchpoint for the "PetRocks Online Services" Business Service, use the following filter:
    (url.stem_string contains "bmc-synthetic-1.0" ignorecase) AND (url.query_param("bmc_syn_bs") is "PetRocks Online Services")

 

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