Viewing an application's synthetic settings

To see synthetic settings for an application, you need to turn Synthetic on for the application and then configure the application accordingly. See Editing synthetic settings for an application for more details.


Synthetic configuration includes the following:

  • Global SLA—Service Level Agreement that applies to all Execution Plans defined for this application.
  • Execution Plans—Plans for running predefined scripts to simulate use of the application.

An Execution Plan provides the interface for a script and its execution. Through an Execution Plan, you specify configuration values for the script, indicate on which locations the script runs, and define the run schedule.

BMC Synthetic Transaction Execution Adapter (TEA) Agents can process up to 120 Execution Plans each.

This topic contains the following procedures:

To view the Global SLA for your application

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the name of the application that you want to see.
  3. Click the  Synthetic  tab. 
     
  4. Click the  icon to view the Global SLA details.

For more details about the specific metrics, see Monitoring synthetic transactions by location and  Monitoring synthetic transactions by execution .

Note

 To hide the Global SLA settings, click the  icon.

To view the list of defined Execution Plans for an application

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the name of the application that you want to see.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed:

    ColumnDescription
    NameName of the Execution Plan This name is always unique within an application. It is possible for different applications to have Execution Plans with the same name. 
    StatusActive or Inactive Place the mouse cursor over the word Inactive to see the reason for the Deactivation. Possible causes are:
    • User-initiated inactive status of an application
    • User-initiated inactive status of an Execution Plan
    • Blackout period of an application

    For more details, see  Application and Execution Plan status .

    SLA SettingsCustom or Global
    • Global indicates that the SLA for this Execution Plan conforms to the Global SLA for the application.
    • Custom indicates that at least one of the metrics for this Execution Plan's SLA is customized. 
      Place the mouse cursor over the word Custom to see which metrics have custom values.
    Script Name Name of the script used by the Execution Plan If the name ends with an ellipsis, the script name is too long to be displayed here. Place the cursor over the truncated script name to see the entire name.
    LocationsNumber of locations in use by this Execution Plan Place the mouse cursor over the number of location to see the names of the individual locations.

To sort the list based on a specific column, click the relevant column heading. To sort in reverse order, click the column heading again.

To view the recent executions for an Execution Plan

From the Application Configuration screen, you can view details of all the transactions executed by an individual Execution Plan in the last 15 minutes. This allows you to easily see the results of any changes you make to an Execution Plan.

  1. From the list of Execution Plans, click on the action menu for the Execution Plan.
  2. Select Show Recent Executions.

Transactions executed in the last 15 minutes are displayed at the bottom of the screen.
 

The data displayed in the table is refreshed automatically every minute. To temporarily disable the refresh, deselect the Auto Refresh checkbox. Deselecting Auto Refresh does not effect the view in the future. Subsequent views of recent executions will have Auto Refresh enabled.

The following details are displayed:

ColumnDescription
Transaction Start Time

Start time of the transaction

Transaction

Name of the transaction

LocationLocation associated with the transaction
LatencyAmount of time (in milliseconds) the transaction took for completion from end to end
Availability Errors

Number of availability errors in the transaction

Availability errors occur when the application does not respond, or when the application responds with an error that indicates it is unavailable.

Accuracy Errors

Number of accuracy errors in the transaction

Accuracy is calculated with the assumption that monitored applications are working as designed and that the information transmitted to clients is correct. Functions that can be evaluated to determine accuracy include link checking, content validation, title validation, and response data verification.

Execution Errors

Number of execution errors in the transaction (unlikely to exceed 1)

An execution error indicates that there were problems with the script execution. It does not indicate anything about the health of the application.

Execution Start Time

Start time of this execution

Related topics

Editing an application's synthetic settings

Using scripts to simulate end-user transactions

Application and Execution Plan status

Daylight saving time and blackout periods

Preparing Silk Test script execution for synthetic transaction monitoring

Was this page helpful? Yes No Submitting... Thank you

Comments