PurePaths and Timeframe
Hi,
I had an incident on March 9, which could query PurePaths until yesterday(March 10).
Today I can not query PurePaths from 9 March.
why is it?
I have configured the collector with:
And the storage settings:
Thanks!!
Perfect !! Thanks Thomas! this works!
Now, I thought we had collected PurePaths at least two weeks.
And we could consult at any time.
I have several profiles and see one of them in detail:
Recording: Continuous (data since: 02/18/2015 16:45:02)
Although not understand why I do not have a more recent date.
Moreover, arbitrarily, we will find that the dynatrace collecting for two weeks and dynatrace has decided to eliminate PurePaths. Thus we reach a day when we can only see PurePath just 30 minutes ago.
I still do not understand how work the collector and stored PurePaths.
Thanks Thomas!!
This is strange that one day run a timeframe ok and the next day not.
Since I have not exceeded the limits placed on data warehouse and storage.
Thanks Bakai.
Right click the system profile that you're trying to get the PurePaths from and then go to Details. In the Recording field it should say something like "Continuous (data since: 2015-03-07 11:12:33)".
All of your PurePaths are stored on the server so as new PurePaths come in, Dynatrace will drop the oldest PurePaths. The date shown in the details tells you how far back you can currently go. Depending on how many PurePaths you analyze in a day, it could be completely reasonable for you to no longer have PurePaths from March 9th. You can always select a group of PurePaths, right click -> Store session to lock them from getting erased as new PurePaths comes in.
Tom
Hi!
It seems your session storage is not full, so maybe the timeframe you applied was not appropriate
