Application and Execution Plan status

With TrueSight Synthetic Monitor with Silk Performer, you can disable monitoring and notifications, such as for maintenance or troubleshooting. You can directly disable synthetic functionality for the application or an Execution Plan, or you can disable individual Execution Plans temporarily by setting blackout periods.

An Execution Plan inherits the active and inactive status from the associated application, however if the Execution plan is disabled or in blackout, this overrides the active application status. For configuration details, see Viewing and editing an application's synthetic settings.

Notifications can be disabled or enabled for individual SLA thresholds at the application level (Global SLA) or Execution Plan level (Custom SLA). Custom SLA settings override Global SLA settings.

The following table shows how the different activity statuses affect the application, Execution Plan, and SLA notifications:

Legend: (tick) = Active, (error) = Inactive, App = application, EP = Execution Plan

Configuration

 Status and Notification
ApplicationExecution PlanApp
status
EP
status

SLA
Notification

Synthetic
status

SLA
Notification

EP
status

Blackout

SLA
Notification 
(tick)(tick)(tick)No(tick)(tick)(tick)(tick)
(tick)(error)(tick)No(tick)(tick)(tick)(tick)
(tick)(tick)(tick)No(error)(tick)(tick)(error)
(tick) (error)  (tick)(error)(error)
(error) (tick)  (error)(error)(error)
(tick)(tick)(tick)Yes (tick)(error)(error)

Related topics

Daylight saving time and blackout periods
Viewing an application's synthetic settings
Editing an application's synthetic settings

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

Comments