Archive Events

An event is purged after two weeks, at which point it is no longer accessible. To save an event beyond the default snapshot lifespan for future analysis, you can archive the event.

Event Purging in Ephemeral Environments

Events associated with nodes that are deployed to machine instances in an ephemeral environment are subject to being purged. This occurs because the node associated with the events is identified by a label consisting of two discrete parts: a node name and a machine instance name. The node name is always fixed, but the machine instance name changes in ephemeral environments. Thus, when a node is redeployed to a new machine instance, the label identifying the node changes.

For example, the label for a node in an ephemeral environment might consist of the fixed node name "Node1" "INSTANCE-M-T1": NodeINSTANCE-M-T1 "NodeINSTANCE-M-T1"

Events Archived by Default

Splunk AppDynamics archives application configuration change events by default. In the Controller UI, these events display asApplication Configuration Change. You can view the Splunk AppDynamics REST APIs.

Warning: Once APPLICATION_CONFIG_CHANGE events are archived or deleted, you can no longer retrieve them through the Splunk AppDynamics REST APIs.

Manually Archive Events

To manually archive events:

  1. Select the event from the events list.
  2. Click Actions > Archive Event.
  3. Click Archive to confirm the action.

This indicates that an event has been archived. You can click the column heading to sort by archived events.

Modify Event Retention Period (On-Premises Controllers)

For on-premises Controllers, administrators can modify the default two-week period by configuring the events.retention.period property in Administration > Controller Settings.