Alert Sensitivity Tuning Questions and Answers

No, AST is available for SaaS customers only.

You can use AST to fine-tune health rules that monitor business transactions, service endpoints, or remote services only. You must set the health rule evaluation scope to 'average for all nodes' of the affected entity.

If you define a persistence threshold for a condition, the metric data is plotted directly on the AST graph. If you do not define a persistence threshold, a 'moving average' for the selected metric is plotted. For more information, see Why use 'moving average'?.

Unless persistence thresholds are used, health rules compare the moving average of a metric to a threshold or a baseline. Thus, representing the moving average in the graph is appropriate. 

Yes, you can define 'persistence threshold' for a health rule. However, you cannot use the moving average for the metric. For more information, see Moving Average.

Depending on the baseline configuration you define, AST presents a graphical view of the metric data for the given baseline configuration. The graphical view instantly updates when you update any configuration. You can also view granular details by modifying the graphical view. The historical metric data in the graph helps you calibrate the sensitivity of the metric evaluation (and the sensitivity of the health rule).

The graphical view may not display due to multiple reasons. Check if you have:

• Created the health rule for a business transaction, a service endpoint, or a remote service.
• Set the health rule evaluation scope to 'average of nodes'.

Yes, you can use AST to configure conditions for both critical and warning criteria.

There is no change in the evaluation of boolean expressions for health rule conditions.

Yes, you can use AST when editing an existing health rule.