how long is data stored for key request?

[mony_r88]

What's the correct answer?

[Bert_VANDEGAER_]

I believe none of the answers listed is 100% correct.

Seems that 'key requests' are 'Timeseries metrics' and therefor only limited by the amount of Cassandra diskspace available. So limitation lies within granularity and there the minimum interval is 1 -minute for the first 14 days and 5 minutes for 14-28 days.

So, I'd think the last option 14-28 days... is the 'best' answer, but it won't be 'single-request' granulatiry if more request happened within 5 minutes.

https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/data-...

[mevlut_soner]

Hi Monica,

By default, detailed history of all requests is stored for 10 days. Longer-term historical data is maintained for requests that you manually identify as key requests. Trend lines for key requests are stored perpetually, however the granularity of long-term history is gradually reduced over time:

• 0-14 days: 1-minute interval granularity available for dashboarding and API access.
• 14-28 Days: 5-minute interval granularity available for dashboarding and API access.
• 28-400 days: 1-hour interval granularity available for dashboarding and API access.
• 400+ days: 1-day interval granularity available for dashboarding and API access.

See: https://www.dynatrace.com/support/help/how-to-use-dynatrace/services-and-transactions/monitoring/mon...

Best Regards,
Mevlüt

[HannahM · Accepted solution]

Hi Monica, single-request granularity is raw data. That is stored for the same amount of time whether it is a key request or not. So the answer would be 35 days.

[MaciejNeumann]

This is the correct answer. Here is the link to the documentation, with all the details about Data retention periods:

https://www.dynatrace.com/support/help/how-to-use-dynatrace/data-privacy-and-security/data-privacy/d...

As you can see, the Requests and request attributes are stored in Dynatrace Saas for 35 days.

[jose_damian_rui]

Sorry but I realize that Dynatrace exam test considers "14-28 days" answer as wrong

On the other hand , explicit reference to 35 days is not reflected on the dynatrace documentation

https://www.dynatrace.com/support/help/how-to-use-dynatrace/transactions-and-services/monitoring/mon...

And to have a "clear view" (ironic mode) Dynatrace documentation reflects as Unlimited the data retention for key requests (https://www.dynatrace.com/support/help/how-to-use-dynatrace/data-privacy-and-security/data-privacy/d... 😞

Maybe dynatrace certification exams are wrong ?

I really appreciate your comments and references for clarifying!

Many Thanks.

Damián

[MaciejNeumann]

As Hannah wrote in this topic earlier, requests and request attributes the stored for the same amount of time, whatever if it is a key request or not. So the correct answer is 35 days, as we can see in this documentation file:

https://www.dynatrace.com/support/help/how-to-use-dynatrace/data-privacy-and-security/data-privacy/d...

[jose_damian_rui]

Sorry Maciej but in the link you are referring I can see that data retention for key requests is "unlimited"

So for me it seems ambiguous and not clear.

If someone could explain I really appreciate.

Many Thanks!

[MaciejNeumann]

In the question that you posted, there is a clear mention of the single-request granularity. The timeseries metrics are for the interval granularity (so the different kind of granularity than the question is asking about), as you can see here:

The single-request granularity, as Hannah already mentioned, is raw data. That is stored for the same amount of time whether it is a key request or not. The answer, in this case, is 35 days.

I hope that this clarifies everything!

[mahendran_a1 · Accepted solution]

Hi Jose and Monica,

The correct answer is first 35 days with single request granularity