AppDynamics Application Intelligence Platform
This topic explains the default data retention periods for data stored by the AppDynamics On-Premise Controller.
The Controller database holds information about following components:
The Controller uses MySQL to store this data.
You can change the amount of data you retain in the Controller database by changing the retention period for events, snapshots, and metric data. If you notice the Controller database growing too large, consider lowering your retention settings. You can also purge old data that is no longer needed by lowering the retention settings.
You can modify the default retention periods for events, snapshot and incidents data.
Setting longer retention periods can significantly affect database size and Controller performance. AppDynamics strongly recommends that you monitor your system carefully if you change any of these settings from the default, and be prepared to roll back your changes if necessary.
Use the root account password to access the Admin console when the Controller is installed in single- or multi-tenant mode. If you have not set this password, call AppDynamics Support to get the default password.
Change the data retention period for incident and event data and transaction snapshots are determined by the following parameters:
|Property Name||About the property||Default||Allowed Values|
|events.retention.period||The retention time for events in hours.||336 hours (2 weeks)||1 to 840 hours (5 weeks)|
|snapshots.retention.period||Determines the retention time for transaction snapshot data in hours.||336 hours (2 weeks)||1 to 840 hours (5 weeks)|
|incidents.retention.period||Determines the data retention time for incidents, including policy violations or very slow transactions, in hours.||336 hours (2 weeks)||1 to 840 hours (5 weeks)|
After you lower one of the data retention period settings, data in the database that falls outside the scope of the new data retention period is discarded. As a result, the size of the database should drop anywhere from 30 to 60 minutes after you make the change. If it does not, see Troubleshooting Controller Database Growth Issues.
You can modify the default metric data retention periods. The metric retention periods control how long data is retained at 1-minute, 10-minute, and 1-hour resolution (see Metric Data Display in Graphs).
Setting longer retention periods for metric data can quickly and significantly affect database size and Controller performance. If you need to review details for an issue that occurred during a period for which you have only 10-minute or 1-hour data, AppDynamics provides access to diagnostic data at a more detailed level than might be visible on a graph, so increasing the default retention periods is not often necessary. See.
There is a special case in which you can lose minute data. If metrics.min.retention.period is under 36 hours and you change it to 36 hours or higher, or if metrics.min.retention.period is 36 hours or higher and you change it to a value under 36 hours, special repartitioning is required, and therefore you will lose all the minute data after you save the settings.
Log in to the Controller administration console. See.
Use the root account password to access the Admin Console. If you have not set this password, call AppDynamics Support to get the default password.
Change the data retention period by modifying the values for the following settings and saving. The settings are:
About the property
The number of hours 1-minute data will be retained in hours. Its value should always be less than the value for metrics.ten.min.retention.period.
1 to 168 hours (1 week)
The number of hours 10-minute data will be retained in hours. Its value should always be greater than the value for metrics.min.retention.period and less than metrics.retention.period.
2 to 504 hours (3 weeks)
The number of days 1-hour data will be retained in days. Its value should always be greater than the value for metrics.ten.min.retention.period.
30 to 730 days (2 years)
For example, if you change the metrics.min.retention.period property to 3, metric data displayed for all time ranges less than or equal to 3 hours will be shown at one-minute resolution. Metric data for time ranges greater than 3 hours and less than metrics.ten.min.retention will be shown at 10-minute resolution, and metric data for older time ranges will be shown at 1-hour resolution.
Another example: If you change the metrics.ten.min.retention property to 168, all time ranges less than or equal to 168 hours (1 week), and greater or equal to min.retention.period will be displayed at 10-minute resolution.
The values in the UI Time Range dropdown menu do not change even if the data retention periods are reconfigured.
The business transaction retention period determines how long the Controller retains a "stale business transaction" as a registered business transaction. A stale business transaction one that has not received a request in a given period of time.
By default, the business transaction registration is retained forever. You can specify a set timeout period for the business transaction if needed. If it has not seen a request in the period of time you configure, the business transaction registration is discarded, making the business registration slot available for another business transaction.
Log in to the Controller administration console. See.
If changing the data retention settings does not improve the rate of database growth for your system, first make sure you have.
If you still see no improvement, file a support ticket that describes the problem along with a listing of your data directory. To generate the listing, run the following command on the Controller machine:
The command writes the output to the controller.output file, which you can attach to your support ticket.