AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    Related Pages:

    Your Rating:
    1 Star2 Star3 Star4 Star5 Star
    28 rates

    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 > Action Suppression tab. 

    Objects Affected by Action Suppression

    You can 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:

    • Application
    • Business Transaction
    • Tier
    • Node
    • Server

    Within the time period configured for the action suppression, no policy actions are invoked for health rule violation events that occur on the specified object(s).

    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, check the action suppression configurations list to see whether action suppression with reporting disabled is currently active for that object.

    You can configure the entities that the action suppression affects for each object. The following table lists the entities for which you can suppress the actions, depending on the configured object scope. 

    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").
    • 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.

    • 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.
    • All servers
    • Specific 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.

    • No labels