PurePaths Historical Data
Relying on historical purepath data has been a key driver for relying in Dynatrace, and normally having up to 2 weeks worth of data stored in the session store for our profile; We are seeing other applications consuming a lot more space against the shared Dynatrace environment which has reduced our ability in seeing historical purepath data older than1 week; However the biggest issue we see is that as our session store is deleted, we need to start from scratch and start accumulating again purepath data for a number of days perhaps a week or more before the session store is deleted again
We understand this is driven by a the storage quota and other system profiles consumption, however we are trying to find out its possible in configuring somehow in having the ability of a continuous chunk of historical data; Rather than accumulating lets say 2 weeks of historical data and then having it deleted and then starting all over again in accumulating a number of days of historical purepath data; would it be possible in having some sort of continuous session store (we are limited to about 5GB) were we could define a 1 week period worth of data and as we reach closer the 5GB limit of our session store, start deleting one day worth of purpepath data at a time rather than the entire session store set?
Juan,
this is exactly what our continous session storage does. It's a rolling buffer, deleting the oldest data as the store fills up to make space for the new ones.
Ar you saying you are using only 5Gb store and that can keep 2 weeks of data? or was that a typing error?
Reinhard
We can clearly see that all session stores have a 5GB limit, once that limit is met a new one is created and older session stores are deleted according to overall storage availability/quota. Our web application does not generate a lot of data and usually within a single session store we have had up to 2 weeks or more of purepath data. So if i understand correctly regardless of how many days worth of data on a single session store (in our case with a 5GB), another session store (with another 5GB) will be created for storing additional purepath data?
What actions could we take to ensure that we will always be able in having some amount of historical purepath available as session stores are removed?
As you said the session stores are in 5 GB increments, and these are the files handled FIFO, so you will need to have a higher multiple of 5 allocated for session storage to maintain some historical data.
Rick B
