Page tree

Unsupported content

 

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

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.
  • Blackout settings—Time periods when the Execution Plans do not run. 
  • 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 BMC TrueSight Operations Management 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. 
     

For more details about the specific metrics, see Monitoring synthetic transactions in the Locations view and Monitoring synthetic transactions in the Executions view.

 

Note

 To hide the Global SLA settings, click the  icon.

To view synthetic blackout settings

  1. On the BMC TrueSight Operations Management console, from the navigation page, select  Configuration > Applications.
  2. Click the application that you want to see. 
  3. Click the Synthetic tab to see the synthetic configuration details for the application.
  4. Click  Blackout Settings button.

    The current blackout settings for the application are displayed.

    (Click picture to see more details.)

     

    The following details are displayed: 

    • Repeat on indicates weekly blackout periods  that occur at the same times on the same days:

      ParameterDescription
      Days of the weekDays on which you the blackout period occurs
      Start TimeStart time for the blackout period
      Start Time is the same for all selected days of the week. 
      DurationLength of the blackout period
      Duration is the same for all selected days of the week. 
    • Occur once indicates a one-time blackout period:

      ParameterDescription
      Start TimeStart time for the blackout period 
      DurationLength of the blackout period

For more details about blackout settings, see Daylight saving time and blackout periods.


To view the list of defined Execution Plans for an application

  1. On the BMC TrueSight Operations Management 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.

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