AppDynamics Application Intelligence Platform
An event is a change in application state that is of potential interest.
AppDynamics summarizes events generated for a specific AppDynamics entity - a business application, business transaction, tier or node- on the Dashboard tab of the entity's dashboard.
AppDynamics reports all events for an application in the application Events List. To access the events list, select Events from the left navigation pane.
The events that occurred within the period indicated by the time range dropdown menu appear in the Events List.
You can filter the types of events displayed in the list by checking which events you are interested in. You can learn more about a specific event by selecting it from the list and viewing its details.
To view and set event filters, click Show Filters. To hide them, click Hide Filters.
AppDynamics also displays the list of events for the entity in the Events tab of the business transaction, tier or node dashboards.
The event categories are:
The event categories include events of different types.
Health Rule events include:
You can filter the specific health rules by affected entity to specify which event data should be displayed.
Slow transactions include:
AppDynamics provides default thresholds that define slow, very slow and stalled transactions, but you can reconfigure them for your environment. See Configure Thresholds.
Error events include error snapshots and all application server exceptions.
You can restrict the errors for which events are displayed by selecting only errors caused by specific exceptions. If you do not select specific exceptions, all the error events are displayed.
Code problems include:
Application change events include:
The AppDynamics Internal Diagnostics events include:
You can create a Custom event using the REST API.
You can create email digests to notify recipients when specific events occur. See Configure Email Digests.
Normally events are purged after a configurable time - by default, two weeks. To save an event beyond the normal snapshot lifespan – for example, if you want to make sure an event associated with a particular problem is retained for future analysis – archive the event.
Customers with on-premise controllers can modify the default two-week period by configuring the events.retention.period in the Controller Settings section of the Administration console.
When you are viewing your Events list, a small icon in the far right column indicates that an event has been archived.
To view archived events in the Events list, sort on the far right column. All archived events will be displayed together.