AppDynamics Application Intelligence Platform
To view the events list, select Events from the left navigation pane.
The events list reports the most recent events in your application. If the Fetch More link is visible you can click it to retrieve older events.
You can get details about an event in the list. The content of the details depends on the type of event. If the event is an application change, such as an application restart, the details might be a static description of the event. If the event is a slow transaction or an error, the details are transaction snapshots from which you can drill down to the root cause of the problem.
If all of the checkboxes in the entire event filter are clear, no events are filtered out and all events are reported.
If one or more of the checkboxes in the event filter are checked, all events are filtered out except for those event types that are checked.
You can filter events to display by event type and by object.
In the FILTER BY EVENT TYPE section of the filter panel, you can filter based on the event type (such as Slow Transactions or Code Problems) and subtype (such as Slow Transactions -> Very Slow Transactions or Code Problems -> Code Deadlock).
You can filter health rule violation events on the health rule type and on specific health rules. For example, you can specify events caused by business transaction performance health rules or only node health rule violations events caused by the "Memory utilization is too high" health rule.
When you filter by AppDynamics entity type in the FILTER BY OBJECT section of the filter panel, you can select specific business transactions or tiers and nodes for which to report events. If you filter by business transaction, filtering by tier and/or node is disabled. If you filter by tier and/or node, filtering by business transaction is disabled.
If you filter by event type but not by object (in other words, at least one of the event type filters is checked but all of the object filters are clear) the events of the selected type are displayed for all AppDynamics entities (business transactions, tiers, and nodes).
1. In the left panel of the event viewer, check the check boxes for the types of events to display.
2. Clear the check boxes for the types of events not to display.
To clear all the check boxes, click Clear Criteria.
If you are filtering Error events, checking the Errors checkbox causes all error snapshots and all errors caused by application server exceptions to be displayed. To reduce the number of error events, you can filter the list by specifying that only error snapshots caused by specific exceptions should be displayed. To do this:
1. In the Errors section of the Event filter panel click Select Specific Exceptions.
2. In the list of exceptions that appears, click the exception or exceptions for which you want to see error events.
3. Click Select.
If you select any exceptions, only error snapshots caused by the selected exceptions are displayed.
If you do not select any exceptions, all error snapshots caused by all exceptions are displayed.
1. In the Filter by Custom Events section of the Event filter panel, click "+" to create a new filter. The Add Custom Event Filter appears.
2. Define the custom event type and, if desired, particular properties on that event, as key/value pairs. Selecting the match value All indicates a logical AND. Selecting the match value Any indicates a logical OR. Click Save.
In the case of Any, at least one property must exist and match. In the case of All, all properties must exist and match.
For information on setting up custom events, see Use the AppDynamics REST API.
1. In the events list select the event for which you want to see details.
2. Click View Event Details.
Usually AppDynamics displays a summary of the event in a new window.
If the event produced a transaction snapshot, as for example in the case of a slow transaction event, AppDynamics displays the transaction snapshot associated with the event. From there you can drill down to the root cause. See Transaction Snapshots. Note that by default, transaction snapshots are purged from the database after two weeks. If you want to be able to review a snapshot that is more than two weeks old, you should archive the snapshot before it is purged.