Page tree

This topic presents the POST 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.

URI stem for synthetic transactions

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

teaAgentIP/bmc-synthetic-1.0/businessServiceName/executionPlanName-->transactionName-->timer

  • teaAgentIP represents the IP address of the TEA Agent
    The first public IP addressed is displayed, if accessible. If a public address is not accessible, then the private IP address of the TEA Agent is displayed.
  • businessServiceName represents the name of the Business Service
  • executionPlanName represents the name of the Execution Plan
  • transactionName represents the name of the default script
  • timer is displayed on if applicable and represents the name of a custom timer or page timer in the script

POST parameters for synthetic transactions

POST parameterValue

bmc_syn_name

Name of the transaction and timer (if relevant), using the following syntax: executionPlan---transactionName---timer
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

Name of the transaction in the script

bmc_syn_script
Name of the script run in the Execution Plan
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
Number of execution errors in the transaction
bmc_syn_av_err_msg

Availability error message or messages. Messages are separated by a series of dashes (---------------).

bmc_syn_acc_err_msg

Accuracy error message or messages. Messages are separated by a series of dashes (---------------).

bmc_syn_exec_err_msg
Execution error messages. Messages are separated by a series of dashes (---------------).
bmc_syn_session_termination
Signal for the end of a session
bmc_syn_custom_timer
Name of the custom timer
bmc_syn_page_timer
Name of the page timer

You can use the 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.post_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.post_param("bmc_syn_bs") is "PetRocks Online Services")