Inactive users time setting affects metrics
Hello forum,
within our installation we have two isntances of monitoring for the same application. The only difference is the Visit setting for inactive users, that is the first one has the limit at 5 minutes for inactive users, while the second one is 30 minutes.
Since that there is this difference we have noted consquently noticeable difference also for the metrics: "Number of visit", "Apdex", "Bounce rate" and much more.
How does this kind of setting affect the metric calculation?
This setting impacts any metrics calculated that require us to have a complete visit. That includes all Visit-based Business Transactions and metrics such as Visit Duration or Action Count (per Visit). It also impacts the "Concurrent Visit" metrics as you will have more visits that are still in progress if you have a longer timeout period
Andi
Hi Andi,
thank you for your help. Anyway I have still some doubts about it. It is clear that for longer timeout period I will have bigger Action Count per visit and Visit Duration. But why also "Visit" metrics is affected by this parameter ? I mean that a visit is a visit even if my timeout period set at 1 s, while the graph, I've attached, showing the double number of visits for the application with 30 mins of timeout.
Also why the Apdex is affected by this paramter?
Hello,
could be the Apdex is affected by the timeout settings since that the number of visit count changes according to the timeout value?
Moreover I can't get the link between the visit count and timeout setting.
