cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Data Retention

daniel_kaar
Guide

How does the data retention look like for Dynatrace? What resolution is available for how long? Is there a difference between SaaS and Managed?

7 REPLIES 7

michael_kopp
Dynatrace Pro
Dynatrace Pro
  • Long term data is kept for several years and gets aggregated over time. This includes all Host/Process metrics and high priority service requests. 1 minute resolution is available for 14 days, after which it gets aggregated to 5 minutes. After a month it gets aggregated to hours.
  • Resolution of AWS monitoring data depends on AWS itself (not all metrics are available from AWS in minute resolution, but sometimes only 5minute)
  • Code level information is kept for 10 days in SaaS. This includes detailed PurePath information.
  • Request level information for Services is kept up to 35 days, this includes charts and topx request information
  • key Requests are treated as long term data in our metric store
  • In a managed setup it is dependent on the amount of storage available to the managed cluster.
  • User Session details are kept for 35 days in SaaS

If you need more information please contact me directly.


@Michael K, is it possible to extend code and request level information for longer than 10 days

michael_kopp
Dynatrace Pro
Dynatrace Pro

Request level info should be available in SaaS for 35 days now. Code level for 10 days. we can technically extend it yes, but that should be discussed with your sales representative.

If you have managed then you can configure that yourself in the tenant management UI.

Is this still true? I'm trying to find a table in the current documentation to reflect SaaS retention periods

it is still true yes, we are still behind here on documentation.

chris_thompson
Dynatrace Participant
Dynatrace Participant

Here's a link to the long-awaited 'Data retention periods' Help topic: https://www.dynatrace.com/support/help/shortlink/data-retention


That is perfect, thanks for publishing this.