Viewing the results of synthetic transaction monitoring

BMC Synthetic End User Experience Monitoring provides results for end-to-end availability errors, execution errors, and accuracy errors. You can examine details about synthetic transactions with the following system tools:

Synthetic transactions in the Console

You can examine details about synthetic transactions in the BMC Application Performance Management Console, through the Performance Analysis pages. To see the transaction results, create Application Watchpoints based on the Execution Plan name, or use Watchpoints from the synthetic device configuration pack.

You can drill down from the Performance Analysis page to investigate synthetic transactions. Each run of an Execution Plan is displayed as a single session.

Example of synthetic transactions on the Sessions Found page

^{Click to enlarge image.}

• The User column displays the name of the transaction with the following syntax: agentGroup @ executionPlan.
• The Total Pages column displays the following sum: numberOfTransactions + numberOfCustomTimers + numberOfPageTimers

Clicking a transaction show its details in the Session Overview page:

Example of a synthetic transaction on the Sessions Overview page

^{Click to enlarge image.}

The first element on the timeline is the first transaction run by the script. The transaction has the following naming syntax: executionPlan-->transactionName. The transaction name comes from the script. If the script contains more than one transaction, they are displayed in chronological order on the session timeline.

Following the transaction name, are the page timers or custom timers, with the following naming syntax: executionPlan-->transactionName-->timer. The timers are aligned with the end of the transaction, on the right-most edge of the transaction or the timeline, and not in chronological order.

You can use the Session Overview tools for analyzing the session further.

Synthetic transactions in the Analyzer

For each Execution Plan that you define, you can create a Watchpoint to filter synthetic response data for monitoring. You can also use Watchpoints from the synthetic device configuration pack. Examples of Watchpoints for synthetic monitoring include the following data filters:

• Synthetic execution results
• Synthetic execution results for a specified Agent Group
• Synthetic execution results with an availability error or an accuracy error or an execution error
• Synthetic execution results of an Execution Plan across all Agent Groups
• Synthetic execution results of a Business Service across all Agent Groups

In the Analyzer, Session Browser, you can see a session for each Execution Plan execution on a TEA Agent. The TEA Agent Group is listed under the User ID column, and its associated Execution Plan is listed in the Group ID column.

You can drill down into a single session and examine the transactions, custom timers, and page timers. Each item is represented as a page.

You can use the Session Browser tools to analyze a query result further.

Related topics

Configuring synthetic monitoring

Synthetic transaction query parameter reference