AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

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.

Event Categories

The event categories are:

  • Health Rule Violations
  • Slow Transactions
  • Errors
  • Code Problems
  • Application Changes
  • AppDynamics Internal Diagnostics
  • Custom

The event categories include events of different types.

Health Rule Violation Events

Health Rule events include:

  • Health Rule Violation Started - Warning 
  • Health Rule Violation Started - Critical
  • Health Rule Violation Continues - Warning
  • Health Rule Violation Continues - Critical
  • Health Rule Violation Upgraded - Warning to Critical
  • Health Rule Violation Downgraded - Critical to Warning
  • Health Rule Violation Ended
  • New in 3.9.1 Health Rule Violation Canceled (this event is generated for an incident if the originating health rule is deleted or modified so that the violating condition no longer applies)  
  • New in 3.9.4 Health rules which cannot currently be evaluated (when a necessary metric is not available, when a necessary baseline is not available, when a new health rule has just been added, or when the system has just restarted) are now displayed with a status of a greyed-out question mark or "Unknown" 

You can filter the specific health rules by affected entity to specify which event data should be displayed.

For information about health rules and health rules violations see Health Rules and Troubleshoot Health Rule Violations.

Slow Transactions

Slow transactions include:

  • Slow
  • Very Slow
  • Stalled

AppDynamics provides default thresholds that define slow, very slow and stalled transactions, but you can reconfigure them for your environment. See Configure Thresholds.

Errors

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

Code problems include:

  • Resource Pool Limit Reached
    This event is generated when the maximum size for any resource pool, such as a thread pool or a connection pool, is reached.

Application Changes

Application change events include:

  • App Server Restarts
    This event is generated when an app server is restarted.

AppDynamics Internal Diagnostics

The AppDynamics Internal Diagnostics events include:

  • Agent Enabled / Disabled
    This event is generated when an agent is enabled or disabled. See Manage App Agents.
  • Bytecode Transformer Log
    This event is generated when an entry is added to the bytecode transformer log. This log shows what AppD instruments and what classes are loaded in the JVM. See bci-log-config for information about bytecode transformer log.
  • AppDynamics Internal Diagnostics
    This event is used by AppDynamics for internal debugging.
  • Internal UI Event
    This event is used by AppDynamics for debugging data sent from the agent to the controller to the UI.

Custom Events

You can create a Custom event using the REST API.

See Create a Custom Event.

Notifications of Events

You can create email digests to notify recipients when specific events occur. See Configure Email Digests.

Archiving Events

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.

To Archive an Event

  1. Display the Events list.
  2. Select one or more events.
  3. Click the Archive button in the toolbar.

When you are viewing your Events list, a small icon in the far right column indicates that an event has been archived.

To Find Archived Events

To view archived events in the Events list, sort on the far right column. All archived events will be displayed together.

Learn More