Examine a Health Rule Violation

To view details about a particular health rule violation:
  1. Select the health rule violation row in the list.
  2. Click Details to view the health rule violation details.

Health rule violation for entities other than business transactions:

The Health Rule Violation page display the violation details:

  • violation state

  • violation window

  • overall violation duration

  • timeline of the violation

  • violation events

  • action executed

The following image displays the health rule violation details for a node.

Click the Affects link to see the dashboard of the entity affected by the health rule. Alternately, click the View Dashboard During Health Rule Violation button to view the dashboard at the time the violation occurred.

Note: The hyperlink to access the affected entity dashboard is not displayed for a Server health rule with entity type Machine_Instance when a health rule violation occurs. Navigate to the Health Rule window, Affected Entities tab to view the list of affected entities.

You can also access details of a health rule violation from the health indicators in the UI. For example, if you see the red indicator on the dashboard indicating that Business Transaction Health or Server Health is critical, click it to get the list of business transactions or tiers and then click the icon in the Health column of the list.

The Health Rule Violation Window field refers to the time period used to assess a Health Rule. This period may differ slightly from the actual evaluation time, as AppDynamics processes data that may be a few minutes old due to the delay between data collection and its availability.

The Summary tab displays details of the health rule violation. When you select the Trigger only when violation occurs x times in last y minute(s) option in health rule condition, the average of the violating metric values is displayed.

For example, you create a condition where an alert must trigger when the value of Calls Per Minute > 6 and this condition must occur three times in the last five minutes. In this case, the Controller checks the Calls Per Minute value for each minute in the last five minutes. Suppose in the first minute Calls Per Minute value is 7, in the second minute the Calls Per Minute value is 9, in the third minute Calls Per Minute value is 8, in the fourth minute Calls Per Minute value is unknown (metric did not report any data), and in the fifth minute Calls Per Minute value is 3. In this scenario, the Calls Per Minute value is greater than 6 for three times and this satisfies the condition. Therefore, an alert is triggered and in the health rule violation summary, you view the average value of the violating metric as 8, which is (7+9+8)/3.

Health rule violation for business transaction:

For a health rule violation related to a business transaction, you can view the AI-generated summaries of the issue and its suspected root cause.

The Summary | AI-generated section provides a concise overview of the issue, including details of the impacted business transaction, the start and end times of the violation, the violation states (for example, critical or warning), and information about the deviating metrics. Splunk AppDynamics SaaS leverages AI to analyze and correlate all metrics related to the health rule violation, generating an informative summary. This comprehensive summary enables you to quickly understand the nature and context of the issue.

Warning: It is important to verify and validate any AI-generated recommendations before acting on them. AI outputs may contain inaccuracies, incomplete information, or unintended biases. You must exercise your own judgment and cross-check AI suggestions to ensure they meet their specific requirements and compliance standards.

In the example, the health rule is violated for the business transaction /web-api/selectReward because the error rate per minute is higher than the normal range for a specific duration.

If you want to view the business transaction dashboard at the time of the health rule violation, click View Dashboard During Violation.

The Suspected Root Causes tab displays the most probable reasons behind the health rule violation. You can view up to three suspected root causes, each accompanied by an AI-generated summary that explains the underlying issue. The section also provides AI-generated recommendations to help you resolve the identified problems. In the Sources list, you can click the business transaction snapshots to examine the potential issues related to each violation.

In the following example, there is only one suspected root cause, which is database-related exceptions.

Click the business transaction snapshot bf553848-8a86-4f0d-9686-d8f0f91ee4cc to examine the issues. You can analyze the flow map to identify the erroneous nodes.

The Violation Events tab displays detailed information about health rule violation events, including when each event occurred, its severity level, current status, and a description of the event. You can also view the start time of each violation, as well as when it was resolved or canceled.