Page tree

With BMC Synthetic End User Experience Monitoring, you can disable monitoring and notifications, such as for maintenance or troubleshooting. You can directly disable a Business Service or Execution Plan, or you can disable them by setting blackout periods.

An Execution Plan inherits the active and inactive status from the associated Business Service, including the blackout periods. The relationship between a Business Service blackout period and an Execution Plan blackout period is a logical OR, meaning that the Execution Plan is in a blackout period if either the applicable Business Service, or the Execution Plan, or both are in blackout. For configuration details, see Defining an application to group Execution Plans and Defining an Execution Plan to run a script.

To see the factor or factors creating an inactive status, hover over the status. A tooltip displays the cause of the inactive status, such as displayed in the following figures:

Inactive status caused by Execution Plan blackout period

Inactive status caused by users of Execution Plan and Business Service

The following table shows how the different activity statuses affect the Business Service and Execution Plan:

Legend: (tick) = Active, (error) = Inactive, BusSrvc = Business Service, ExecPlan = Execution Plan

Configuration

Status and Notification
Business ServiceExecution PlanBusiness ServiceExecution Plan
User
status
In
blackout
User
status
In
blackout
StatusByStatusBy
(tick)No(tick)No(tick)not applicable(tick)not applicable
(tick)No(error)No(tick)not applicable(error)ExecPlan user
(tick)No(tick)Yes(tick)not applicable(error)ExecPlan blackout
(tick)No(error)Yes(tick)not applicable(error)

ExecPlan user +
ExecPlan blackout

 
(error)No(tick)No(error)BusSrvc user(error)BusSrvc user
(error)No(error)No(error)BusSrvc user(error)BusSrvc user +
ExecPlan user
(error)No(tick)Yes(error)BusSrvc user(error)BusSrvc user +
ExecPlan blackout
(error)No(error)Yes(error)BusSrvc user(error)BusSrvc user +
ExecPlan user +
ExecPlan blackout
 
(tick)Yes(tick)No(error)BusSrvc blackout(error)BusSrvc blackout
(tick)Yes(error)No(error)BusSrvc blackout(error)BusSrvc blackout +
ExecPlan user
(tick)Yes(tick)Yes(error)BusSrvc blackout(error)BusSrvc blackout +
ExecPlan blackout
(tick)Yes(error)Yes(error)BusSrvc blackout(error)BusSrvc blackout +
ExecPlan user +
ExecPlan blackout
 
(error)Yes(tick)No(error)BusSrvc user +
BusSrvc blackout
(error)BusSrvc user +
BusSrvc blackout
(error)Yes(error)No(error)BusSrvc user +
BusSrvc blackout
(error)BusSrvc user +
BusSrvc blackout +
ExecPlan user
(error)Yes(tick)Yes(error)BusSrvc user +
BusSrvc blackout
(error)BusSrvc user +
BusSrvc blackout +
ExecPlan blackout
(error)Yes(error)Yes(error)BusSrvc user +
BusSrvc blackout
(error)BusSrvc user +
BusSrvc blackout +
ExecPlan user +
ExecPlan blackout

Related topics

Daylight saving time and blackout periods
Defining an application to group Execution Plans
Defining an Execution Plan to run a script