Download PDF
Download page Action Suppression.
Action Suppression
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.
To see action suppression configurations created for an application:
- Click Alert & Respond > Actions.
- Select the desired component such as Applications, User Experience, Databases, or Servers.
- Click Action Suppression.
You can configure the entities that the action suppression affects for each object. Within the time period configured for the action suppression, no policy actions are invoked for health rule violation events that occur on the specified objects. You can disable the reporting of metrics for agents associated with the object for which actions are suppressed. This option can cause reported metrics to change without notice. If you see a sudden unexpected change in reported metrics for an object, review the action suppression configurations list to determine whether action suppression with reporting disabled is currently active for that object.
Objects Affected by Action Suppression for an Application
You can configure action suppression for a specific time period to apply to a specific object or several objects. These entities can be the objects of action suppression:
- Application
- Business Transaction
- Tier
- Node
- Server
The table lists the entities for which you can suppress the actions depending on the configured object scope for an application.
Object Scope | Affected Entities |
---|---|
Application | All entities within the application. |
Business Transaction |
|
Tiers |
In a tier-level configuration, the suppression affects:
For example, if a tier-level health rule is configured to invoke 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. |
Nodes |
Within these node types you can suppress actions for:
|
Servers |
|
Objects Affected by Actions Suppression for Databases
The table lists the entities for which you can suppress the actions depending on the configured object scope for databases.
Object Scope | Affected Entities |
---|---|
All Databases | All databases in the account |
Specific Databases | Databases that you have selected in the account |
Objects Affected by Actions Suppression for Servers
The table lists the entities for which you can suppress the actions depending on the configured object scope for servers.
Object Scope | Affected Entities |
---|---|
Any Object | All objects within the servers. |
Subgroups |
|
Servers |
|
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 be invoked for violations of HealthRuleA and HealthRuleB during the configured time period.
Disable Health Rule Evaluation
Suppressing an action does not suppress the evaluation of any health rules linked to the action through a policy. Health rule violation events continue to be raised even when actions are suppressed. You can turn off the evaluation of a specific health rule or all health rules. See Disable All Health Rules.