Continuous Sessions in 4.0
Yes I have looked at the filesystem size several times. To me ,it seems like a Webinar or some high contact method is needed to make the underlying architecture of Continuous Sessions a clear reality to customers that depend on this feature, and its of course a Production targetted one, which makes this still new feature an enigma to me and perhaps even Consultants at Compuware.
I would definitely love to attend a deep-dive Webinar on dT Sessions & Continuous Sessions mode.
Thanks for this feedback Frank. Will add it to our list of upcoming dynaLearn Webinars
We use continuous session storage only in production but it never fills up the disk quota I have given it and we tend to see about 10,000 Pure Paths per day, pretty much a steady state. How can I tune both the RAM memory size and disk memory size to allow let's say 100,000 of these pure paths to be saved (estimating 10 days, or even 90 days), is there a way to do this?
Hi Frank
First of all - make sure that the file system location you have configured really has the space available that you have configured in the quota. dynaTrace will use this quote - but - also will make sure to not completely fill up the disk. So - doublecheck if there is enough disk space
As to optimization: The Golden Rule is to only capture data you really need, e.G: if you do not need to see all exceptions exclude those that are not of interest for you. Same is true for log statements, SQL Bind Values, HTTP Parameters, ... The smaller the PurePaths are the more can fit in memory and the more can fit on disk
If you say you have 10k PP / Day I dont see any problem why you shouldnt be able to store up to 90 days on disk. Are you sure it is really only 10k/day?
Andi
Thanks Andreas. As a follow up, the total storage quota is for ALL profiles/apps, correct? That is, I cannot assign each app a certain amount of disk space as a quota, correct? It would be nice to assign a larger app/profile a larger amount of disk space for its sessions so that a smaller app, running say a load test, did not take up all the disk space.
Thats correct. And I think this was one of the feature requests discussed at the recent Customer Summit - so - our Product Management is already aware of that.
When you say "a load test is taking up space" do you mean that you have one dynaTrace Server that is used in both Production and Pre-Production? Our recommendation is to have different dynaTrace Servers in different environments and to use Continouos Session Recording in Production but go Start/Stop Session Recording in Pre-Prod Environments. Thats also the reason why Cont. Session Recording is on by default for Production Licenses but off for Testing/Dev-Team Licenses
No. We have a non-prod and a prod instance. But in non-prod we have many apps and one running a load test could take up all the session space. I guess in non-prod we could do manual recording but sometimes we forget and kick off load tests and then don't have the sessions recorded.
When kicking of load-tests you can use our REST Interfaces to Start/Stop Session recording - this will prevent you from forgetting to kick-off recording. With that you will get a load testing session for every load test and wont run into the problem that one of the projects is "eating up" session space
Our REST Interfaces and how to use them to integrate your testing tools are well documented in dynaLearn: dynaTrace 4 - Testing - Integrations
All transactions are accessed through the System Profile. So - you can now define a Dashboard, select your System Profile and any timeframe you want to analyze. dynaTrace will then show you those PurePaths for your selected timeframe.
You can still store or export PurePaths for a certain timeperiod or select individual ones. Once stored they will show up as a stored session.
For more information on Sessions check out the content on dynaLearn: dynaTrace 4 - Core Concepts - Sessions. Check the Slides under "Session Overview" and the additional links to the Online Documentation
when enabling "continuous transaction storage" do the sessions all end up in the "main" system profile area? or do they get folders under "Session Storage" in folders?
