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
ApplicationAll entities within the application.
Business Transaction
  • 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").
Tiers
  • All tiers in the application.
  • Specific tiers.

In a tier-level configuration, the suppression affects:

  • all the nodes in the specified tier(s)
  • individual node health rules as well as tier-level health rules

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
  • All nodes
  • Java nodes
  • .NET nodes
  • PHP nodes

Within these node types you can suppress actions for:

  • All nodes
  • Nodes in specific tiers
  • Specific nodes
  • Nodes with names, meta-info, environment variables or JVM system environment properties with specified matching criteria
In a node-level configuration, the suppression affects node health rules only.
Servers
  • All servers
  • Specific servers