Editing an application's synthetic settings

Best practice to start the Execution Plans

It is recommended not to start and run all Executions Plans at the same time. Starting all Executions Plans at the same time would spike the memory and CPU and could adversely affect the system performance. It is better to stagger the script start and run for an optimized performance.


Editing an application's synthetic settings (applicable to versions 11.3.02 and later)

Click here to expand

To run synthetic functionality on an application, you need to turn Synthetic on for the application and then configure the application accordingly.  To turn Synthetic on for an application, on the Edit Application page, set the Synthetic field for the application to ON.

Synthetic ON.png

Warning

If you set the Synthetic field to OFF, all synthetic configurations for the application, including all Execution Plans, are deleted.

To run synthetic functionality, you also must make sure the current status is set to Active.

Synthetic_Active.png

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 the use of the application

  • Synthetic metric rules — Rules for opening events based on the measured metrics of individual transactions (not part of this topic). For more information, see Configuring and managing synthetic metric rules.

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 define a Global SLA for your application

Note

You can also add custom SLA levels for individual execution plans. See To edit the Custom SLA for an Execution Planfor more details.

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
     Synthetic_View_Global_SLA.png 
  1. Click the expand_summary.png icon to open the Global SLA settings.

  2. For each metric, set the following options:

    • Minor Threshold and Critical Threshold—Levels indicating when an event is triggered
      Default values are 10% for Minor and 20% for Critical.
    • Send Notification — Level of event that triggers a notification. The following options are available:
      • Never — An event is generated and the applications color indication is affected, but no notification is sent.
      • When minor or critical threshold is breached — An event is generated and notification is sent.
      • When critical threshold is breached — An event is generated and the applications color indication is affected, but notification is sent only for critical events.
    • Transaction Latency — (Performance only) Threshold beyond which the latency triggers an event
      Default is 2000 milliseconds. 

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

  3. Click Save. 

Enabling and disabling synthetic SLA events

If you do not want SLA-based events to be generated, you can disable them. To do this, from the TrueSight Operations Management menu, select  Configuration > Synthetic Metric Rules and scroll down to the bottom of the page to the Synthetic SLA section, and click the SLA Events switch to turn it off. The switch effects all applications.

syn_SLA_switch.png

If you have synthetic SLA events disabled, and you want to turn them on, you can use the same SLA Events switch.

Notes

  • SLA events are disabled by default in new installations.
  • SLA events remain enabled by default in upgrades from previous versions of TrueSight Operations Management.

To create or edit an Execution Plan

  1. On the TrueSight console, from the navigation page, select Configuration > Applications.
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. Perform one of the following actions:
    • To define a new Execution Plan, on the Execution Plans action menu, click Create Execution Plan.
    • To edit a previously defined Execution Plan, from the action menu of the specific Execution Plan, select Edit Execution Plan Settings.
  5. In General Settings, configure the following settings:

    • Enter a unique Name for the Execution Plan and, optionally, a Description for the Execution Plan. 
      The description appears in a tooltip when you place the cursor over the Execution Plan name on the list of Execution Plans.

      Note

      Execution Plan names must be unique within the same application configuration. You can use the same Execution Plan name in different application configurations.

    • To change the the Execution Plan Status, select Active or Inactive.
      The status of the Execution Plan determines whether the script runs. The Execution Plan is also affected by the status of the application. The status of the application takes precedence.
    • For a new Execution Plan: Select the script file that this Execution Plan runs.
      You cannot change the script when you edit an Execution Plan.

  6. In Script Attributes, set values for the script attributes that require user input, such as URLs, host names, and passwords.

    Note

    • App Visibility does not validate script attribute values. For information about provided scripts, see Using-scripts-to-simulate-end-user-transactions.
    • Script attributes of scripts provided by BMC do not support non-English characters.
    • If you define the Execution Plan to run a Silk Test script on more than one location, ensure that each TEA Agent in each location has an administrator account that uses the same user name and password.  

  7. In Locations, you can assign or unassign locations where the Execution Plan runs. 

    • To assign locations to the Execution Plan, click Select Locations and select locations to add.
    • To unassign locations from an Execution Plan, click Select Locations  and clear the check boxes for the relevant locations.


  8. Click OK.

  9. In Execution Plan Schedule, you see a summary of the current schedule settings for the Execution Plan

    EP_Schedule_Summary.png

    To edit the schedule, click Edit Schedule.

    Execution_Plan_Schedule.png

    In the Execution Plan Schedule dialog box, set the following options:

    Repetition

    Repeat Every

    Set how often the Execution Plan runs. This must be a whole number of minutes or hours.

    • Minimum is 1 minute.
    • Maximum is 24 hours.
    • Default is 5 minutes.

    Timeout Period

    Set the amount of time the Execution Plan is allowed to run before it stops automatically.  

    Advanced Settings

    Initial Execution Schedule


    Starts the initial or first run of the Execution Plan in one of the following cases:

    • Execution Plan creation
    • Execution Plan updation
    • TEA Agent restart


    Start In Multiples of Minutes

    Set the start time in multiples of minutes specified within the hour. When an Execution Plan is created or updated, or TEA Agent restarted, the first run occurs in the specified time based on a criteria. Set any value between 1-30 (Min is 1 and Max is 30 minutes). The specified time is calculated using the following criteria:

    Calculation criteria:

    - If the specified minutes returns no remainder (zero value) when divided by 60, the execution starts at 00 mins within the hour.

    - If the specified minutes returns a remainder (non-zero value) when divided by 60, the execution starts at <the specified minutes> after HH:00.

    For example, you specify 08 minutes. The execution might start at HH:08, HH:16, HH:24,... or HH:56. If the Execution Plan is created at 11:18, the first run will start at 11:24 and will continue to execute at every interval configured as per the Repeat Every settings.

    Start At

    Set the Execution to start at the exact specified time. Specify the time in mm:ss format. For example, if you specify 16:00  (mm:ss) and the current time is 11:05, the Execution Plan will start running at 11:16:00. If the current time is 11:28:00, the Execution Plan will start running in the next hour at 12:16:00

    • Minimum is 00:01 mm:ss.
    • Maximum is 59:59 mm:ss.

    Random Delay (Maximum in minutes)

    (Optional) Set this to the maximum range of delay before the Execution Plan starts. A different delay value is randomly set for each location where the Execution Plan runs. In each location, the Execution Plan runs at start time as configured in Initial Execution Schedule + the random delay set for the Execution Plan in that location. You can skip this option if you do not want a random delay.

    • Minimum is 1 minute.
    • Maximum is 60 minutes.
    • Default is 5 minutes.

    See examples at the end of this procedure.

    Life Cycle

    Effective Immediately
    or
    Effective From 

    Select Effective Immediately to start running the Execution Plan immediately.

    Select Effective From to start running the Execution Plan from a specific date and time.

    Never Expire
    or
    Expire On

    Select Never Expire to indicate the Execution Plan should continue running and will never expire.

    Select Expire On to set an expiration date and time for the Execution Plan. The Execution Plan will not run anymore after the expiration date/time passes.

    Time Zone

    Coordinated Universal Time (UTC)

    Select this to schedule the Execution Plan according to UTC time.

    TEA Agent Time

    Select this to schedule the Execution Plan according to the local time of the TEA Agent where the Execution Plan runs.

    Click  Save.

  10. In Execution Log Settings set how you want execution logs to be saved for this Execution Plan. 
    syn_Ex_Log_settings.png
    The following options are available:
    • Always — An execution log is saved for every execution of the Execution Plan.
    • Never — No execution logs are saved for this Execution Plan
    • On Error (default) — Execution logs are saved for executions that have availability, accuracy, or execution errors.
  11. Click Save to save the Execution Plan settings.

Note

Initial configuration operations might take several minutes to take effect, depending on the heartbeat interval of the TEA Agent (30 seconds, by default) and the amount of time to download the scripts to the TEA Agent computer. 

Random Delay Examples

Random Delay randomly assigns time for the existing initial execution schedule configuration over a set range so that all Execution Plans do not start at the same time and overload the system.

Example A

Execution Plan Test_Purchase is set to run every 5 minutes in 3 locations (A, B, and C) with a Random Delay setting of 5 minutes. The random values are automatically assigned over the five-minute interval (for example, 1:34, 3:28, and 2:56).If the current time is 13:58 and Start in multiple of minutes is 6, the results would be as follows:

Location

Execution start time
(Without Random Delay)

Random Delay

Execution start time
(Initial schedule + Random Delay)

A

14:00:00

00:01:34

14:01:34, 14:06:34, 14:11:34, ...

B

14:00:00

00:03:28

14:03:28, 14:08:28, 14:13:28, ...

C

14:00:00

00:02:56

14:02:56, 14:07:56, 14:12:56, ...

Example B

Execution Plan Test_Run is set to run every 10 minutes in 5 locations, with a Random Delay setting of 20 minutes. The random values are automatically assigned over the twenty-minute interval (for example, 11:59, 3:13, 7:38, 18:27, and 17:34). If the current time is 13:03:00 and Start at is 05:00, the results would be as follows:

Location

Execution start time
(Without Random Delay)

Random Delay

Execution start time
(Initial schedule + Random Delay)

A

13:05:00

00:11:59

13:16:59, 13:26:59, 13:36:59, ...

B

13:05:00

00:03:13

13:08:13, 13:18:13, 13:28:13, ...

C

13:05:00

00:07:38

13:12:38, 13:22:38, 13:32:38, ...

D

13:05:00

00:18:27

13:23:27, 13:33:27, 13:43,27, ...

E

13:05:00

00:17:34

13:22:34, 13:32:34, 13:42:34, ...


To edit the Custom SLA for an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Custom SLA.

  5. For each metric that you want to set differently from the Global SLA, set Value Type for the metric you want to customize to Custom, and then set the following options:

    • Minor Threshold  and  Critical Threshold — Levels indicating when an event is triggered
    • Send Notification — Level of event that triggers an automatic notification. The following options are available:
      • Never — An event is generated and the applications color indication is affected, but no notification is sent.
      • When minor or critical threshold is breached — An event is generated and notification is sent.
      • When critical threshold is breached — An event is generated and the applications color indication is affected, but notification is sent only for critical events.
    • Transaction Latency — (Performance only) Threshold beyond which the latency triggers an event.

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

  6. Click Save.

To reset the SLA for an Execution Plan to the Global SLA

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Reset to Global SLA.
    A confirmation message appears asking if you want to reset the SLA for this Execution Plan. 
  5. Click Yes.

To deactivate an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Deactivate.

To activate an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. Place the mouse cursor over the Inactive status of the Execution Plan to see why the Execution Plan is inactive. 
    Deactivated_by_Execution_Plan.png      
  1. If the deactivation is at the Execution Plan level, from the action menu of the Execution Plan, select Activate.

To delete a defined Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Delete.
  5. Click Save.

Editing an application's synthetic settings (applicable to version 11.3.01)

Click here to expand

To run synthetic functionality on an application, you need to turn Synthetic on for the application and then configure the application accordingly.  To turn Synthetic on for an application, on the Edit Application page, set the Synthetic field for the application to ON.

Synthetic ON.png

Warning

If you set the Synthetic field to OFF, all synthetic configurations for the application, including all Execution Plans, are deleted.

To run synthetic functionality, you also must make sure the current status is set to Active.

Synthetic_Active.png

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 the use of the application

  • Synthetic metric rules — Rules for opening events based on the measured metrics of individual transactions (not part of this topic). For more information, see Configuring and managing synthetic metric rules.

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 define a Global SLA for your application

Note

You can also add custom SLA levels for individual execution plans. See To edit the Custom SLA for an Execution Planfor more details.

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
     Synthetic_View_Global_SLA.png 
  1. Click the expand_summary.png icon to open the Global SLA settings.

  2. For each metric, set the following options:

    • Minor Threshold and Critical Threshold—Levels indicating when an event is triggered
      Default values are 10% for Minor and 20% for Critical.
    • Send Notification — Level of event that triggers a notification. The following options are available:
      • Never — An event is generated and the applications color indication is affected, but no notification is sent.
      • When minor or critical threshold is breached — An event is generated and notification is sent.
      • When critical threshold is breached — An event is generated and the applications color indication is affected, but notification is sent only for critical events.
    • Transaction Latency — (Performance only) Threshold beyond which the latency triggers an event
      Default is 2000 milliseconds. 

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

  3. Click Save. 

Enabling and disabling synthetic SLA events

If you do not want SLA-based events to be generated, you can disable them. To do this, from the TrueSight Operations Management menu, select  Configuration > Synthetic Metric Rules and scroll down to the bottom of the page to the Synthetic SLA section, and click the SLA Events switch to turn it off. The switch effects all applications.

syn_SLA_switch.png

If you have synthetic SLA events disabled, and you want to turn them on, you can use the same SLA Events switch.

Notes

  • SLA events are disabled by default in new installations.
  • SLA events remain enabled by default in upgrades from previous versions of TrueSight Operations Management.

To create or edit an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. Perform one of the following actions:
    • To define a new Execution Plan, on the Execution Plans action menu, click Create Execution Plan.
    • To edit a previously defined Execution Plan, from the action menu of the specific Execution Plan, select Edit Execution Plan Settings.
  5. In General Settings, configure the following settings:

    • Enter a unique Name for the Execution Plan and, optionally, a Description for the Execution Plan. 
      The description appears in a tooltip when you place the cursor over the Execution Plan name on the list of Execution Plans.

      Note

      Execution Plan names must be unique within the same application configuration. You can use the same Execution Plan name in different application configurations.

    • To change the the Execution Plan Status, select Active or In active.
      The status of the Execution Plan determines whether the script runs. The Execution Plan is also affected by the status of the application. The status of the application takes precedence.
    • For a new Execution Plan: Select the script file that this Execution Plan runs.
      You cannot change the script when you edit an Execution Plan.

  6. In Script Attributes, set values for the script attributes that require user input, such as URLs, host names, and passwords.

    Note

    • App Visibility does not validate script attribute values. For information about provided scripts, see Using-scripts-to-simulate-end-user-transactions.
    • Script attributes of scripts provided by BMC do not support non-English characters.
    • If you define the Execution Plan to run a Silk Test script on more than one location, ensure that each TEA Agent in each location has an administrator account that uses the same user name and password.  

  7. In Locations, you can assign or unassign locations where the Execution Plan runs. 

    • To assign locations to the Execution Plan, click Select Locations and select locations to add.
    • To unassign locations from an Execution Plan, click Select Locations  and clear the check boxes for the relevant locations.

    Click  OK .

  8. In Execution Plan Schedule, you see a summary of the current schedule settings for the Execution Plan.
    EP_Schedule_Summary.png
    To edit the schedule, click Edit Schedule.

    See the following video for a description on setting an Execution Plan schedule:

    Execution_Plan_Schedule.png

    In the Execution Plan Schedule dialog box, set the following options: 

    Repetition

    Repeat Every

    Set how often the Execution Plan runs. This must be a whole number of minutes or hours.

    • Minimum is 1 minute.
    • Maximum is 24 hours.
    • Default is 5 minutes.

    Timeout Period

    Set the amount of time the Execution Plan is allowed to run before it stops automatically.  

    Advanced Settings

    Coordinated Universal Time (UTC)

    Select this to schedule the Execution Plan according to UTC time.

    TEA Agent Time

    Select this to schedule the Execution Plan according to the local time of the TEA Agent where the Execution Plan runs.

    Random Start-Time Delay (Maximum in minutes)

    Set this to the maximum range of delay before the Execution Plan starts. A different delay value is randomly set for each location where the Execution Plan runs. In each location, the Execution Plan runs at start time + the random delay set for the Execution Plan in that location.

    • Minimum is 1 minute.
    • Maximum is 60 minutes.
    • Default is 5 minutes.

    See examples at the end of this procedure.

    Effective Immediately /
    Effective From 

    Select Effective Immediately to start running the Execution Plan immediately.

    Select Effective From to start running the Execution Plan from a specific date and time.

     

    Never Expire /
    Expire On

    Select Never Expire to indicate the Execution Plan should continue running and will never expire.

    Select Expire On to set an expiration date and time for the Execution Plan. The Execution Plan will not run anymore after the expiration date/time passes.

    Click  Save .

  9. In Blackouts, If you have blackout periods set for this Execution Plan, you see a table listing the blackout periods.
    EP_Blackout_Table.png
    The following details are shown in the table (see the descriptions the fields in the editing a blackout section below for more details):

    Column

    Description

    Time Zone

    The clock used to calculate the blackout period:

    • UTC — Coordinated Universal Time
    • Local — Local time of the TEA Agent running the Execution Plan

    Period

    Time period when the blackout period is in effect

    Recurrence

    When, and how often the blackout period recurs

    Description

    Optional description

    • To add a blackout period for this Execution Plan, click Add Blackout . See the following video for a description on adding blackouts:

    • To edit a blackout period for this Execution Plan, click Edit on the blackout period's action menu.
      Edit_EP_Blackout_Period.png
      Edit_EP_Blackout_Period.png
      In the Blackout Settings dialog box, set the following options: 
      EP_Blackout_Settings.png 

      Description (optional)

      Enter a logical name or description for the blackout period.

      Time Period

      Coordinated Universal Time (UTC) / TEA Agent Local Time

      Select Coordinated Universal Time (UTC) to schedule the blackout according to UTC time.

      Select TEA Agent Local Time to schedule the blackout according to the local time of the TEA Agent where the Execution Plan runs.

      Effective Immediately /
      Effective From

      • Effective Immediately — Start using the blackout period immediately. 
      • Effective From — Select a time and date from which the blackout period is in effect.

      Never Expire /
      Expire On

      • Never Expire — The blackout period continues running and never expires.

      • Expire On — Expiration date and time for the blackout period. The blackout period does not run anymore after the expiration date/time passes.

        Note

         The blackout period includes the entire minute indicated in the Expire On field. For example, if you select 8:00 as your expiration time, the blackout continues until 8:00:59.

      Recurrence

      All Day

      Select this to set the blackout period to cover the entire day for the selected days.

      Start Time, End Time

      Select the start and end times of the blackout period for the selected days of the week. The same Start Time and End Time apply to all selected days.

      Days of the week

      Select the days of the week when the blackout period takes effect. At least one day must be selected.

      Click Save.

    • To delete a blackout period, click Delete on the action menu for the blackout period.
      Delete_EP_Blackout.png
  10. In Execution Log Settings set how you want execution logs to be saved for this Execution Plan. 
    syn_Ex_Log_settings.png
    The following options are available:
    • Always — An execution log is saved for every execution of the Execution Plan.
    • Never — No execution logs are saved for this Execution Plan
    • On Error (default) — Execution logs are saved for executions that have availability, accuracy, or execution errors.
  11. Click Save to save the Execution Plan settings.

Note

Initial configuration operations might take several minutes to take effect, depending on the heartbeat interval of the TEA Agent (30 seconds, by default) and the amount of time to download the scripts to the TEA Agent computer. 

Random Start-Time Delay Examples

Random Start-Time Delay randomly assigns start times over a set range so that all Execution Plans do not start at the same time and overload the system.

Example A

Execution Plan Test_Purchase is set to run every 5 minutes in 3 locations (A, B, and C) with a Random Start-Time Delay setting of 5 minutes. The random values are automatically assigned over the five-minute interval (for example, 1:34, 3:28, and 2:56).The results would be as follows:

Location

Execution Times

A

00:01:34, 00:06:34, 00:11:34, ...

B

00:03:28, 00:08:28, 00:13:28, ...

C

00:02:56, 00:07:56, 00:12:56, ...

Example B

Execution Plan Test_Run is set to run every 10 minutes in 5 locations, with a Random Start-Time Delay setting of 20 minutes. The random values are automatically assigned over the twenty-minute interval (for example, 11:59, 3:13, 7:38, 18:27, and 17:34). The results would be as follows:

Location

Execution Times

A

00:11:59, 00:21:59, 00:3 1:59 , 00:4 1:59, ...

B

00:03:13, 00:13:13, 00:23:13, 00:33:13, ...

C

00:07:38, 00:17:38, 00:27:38, 00:37:38, ...

D

00:18:27, 00:28:27, 00:38:27, 00:48:27, ...

E

00:17:34, 00:27:34, 00:37:34, 00:47:34, ...


To edit the Custom SLA for an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Custom SLA.

  5. For each metric that you want to set differently from the Global SLA, set Value Type for the metric you want to customize to Custom, and then set the following options:

    • Minor Threshold  and  Critical Threshold — Levels indicating when an event is triggered
    • Send Notification — Level of event that triggers an automatic notification. The following options are available:
      • Never — An event is generated and the applications color indication is affected, but no notification is sent.
      • When minor or critical threshold is breached — An event is generated and notification is sent.
      • When critical threshold is breached — An event is generated and the applications color indication is affected, but notification is sent only for critical events.
    • Transaction Latency — (Performance only) Threshold beyond which the latency triggers an event.

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

  6. Click Save.

To reset the SLA for an Execution Plan to the Global SLA

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Reset to Global SLA.
    A confirmation message appears asking if you want to reset the SLA for this Execution Plan. 
  5. Click Yes.

To deactivate an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Deactivate.

To activate an Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. Place the mouse cursor over the Inactive status of the Execution Plan to see why the Execution Plan is inactive. 
    Deactivated_by_Execution_Plan.png      
  1. If the deactivation is at the Execution Plan level, from the action menu of the Execution Plan, select Activate.

To delete a defined Execution Plan

  1. On the TrueSight console, from the navigation page, select  Configuration > Applications .
  2. Click the action menu of the relevant application and select Edit.
  3. Click the Synthetic tab. 
    The Execution Plans that are defined for the application are listed. 
  4. From the action menu of the specific Execution Plan, select Delete.
  5. Click Save.

Related topics

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

Configuring-and-managing-synthetic-metric-rules

 

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