You can temporarily suppress a policy's automatic invocation of actions and alerts. You may want to do this while you are performing maintenance on or troubleshooting a component.
Suppressing an action does not suppress the evaluation of any health rules linked to the action via a policy. Health rule violation events continue to be raised and surfaced to the UI.
- To turn off the evaluation of a specific health rule, click Alert & Respond->Health Rules, select the Health Rule, click the edit pencil, and uncheck the Enabled box in the Edit Health Rule Overview panel.
- To turn off all health rule evaluation, uncheck Evaluate Health Rules at the top left of the Health Rules screen.
To see action suppression configurations created for an application:
- Click Alert & Respond -> Actions.
- Click the Action Suppression tab.
The list of action suppression configurations displays in the left panel with the objects affected by a selected configuration displayed in the right panel.
Notice that the Object Scope list shows both Tiers and Nodes. Because the nodes are children of the tiers, action suppression affects them as well. Selecting an Application as Object Scope can produce a list of many items if the application is complex enough. All tiers and nodes are shown, although no business transactions are shown in the list.
Objects Affected by Action Suppression
You configure action suppression for a specific time period to apply to a specific object or several objects. The following entities can be the objects of action suppression:
- Business Transaction
Within the time period configured for the action suppression, no policy actions are fired for health rule violation events that occur on the specified object(s).
You can also optionally disable reporting of metrics for an object for which actions are suppressed. Using this option can cause reported metrics for those objects to change without notice. If you see a sudden unexpected change in reported metrics for an object, check the action suppression configurations list to see whether action suppression with reporting disabled is currently active for that object.
If the object scope of an action suppression is at the node level, the suppression affects only node health rules.
If the object scope of an action suppression is at the tier level, the suppression affects individual node health rules as well as tier-level health rules.
For example, if a tier-level health rule is configured to fire an action when a percentage of the nodes violates the condition, and then action suppression is configured on certain nodes in that tier, those nodes are still evaluated by the tier-level health rule.
Application-Level Action Suppression
In an application-level configuration, all entities in the application are affected.
Business Transaction Action Suppression
In a business-transaction-level configuration, you can suppress actions in:
- All business transactions in the application
- All business transactions within specific tiers
- Specific business transactions
- Business transactions with names having patterns that match certain criteria (such as all business transactions with names that start with "XYZ")
Tier-Level Action Suppression
In a tier-level configuration, all the nodes in the specified tier(s) are affected. You can suppress actions for:
- All tiers in the application
- Specific tiers
Node-Level Action Suppression
In a node-level configuration, you can specify the types of nodes for which to suppress actions:
- All nodes
- Java nodes
- .NET nodes
- PHP nodes
and within those types you can suppress actions for:
- All nodes
- Nodes in specific tiers
- Specific nodes
- Nodes with names, meta-data, environment variables or JVM system environment properties with matching criteria that you specify
Machine-Level Action Suppression
You can suppress actions run on specific machines. Actions run on all the nodes on the specified machine (s) are suppressed.
Health Rules Affected by Action Suppression
By default, an action suppression configuration applies to actions triggered by all events that are generated by the configured objects.
You can refine the configuration to apply only to actions triggered by specific health rule violations. For example, if an application contains HealthRuleA, HealthRuleB and HealthRuleC, but only HealthRuleC is configured for action suppression, actions will continue to fire for violations of HealthRuleA and HealthRuleB during the configured time period.