This utility reads in QlikView Server session logs from a user configured windows folder. The dashboard shows # sessions, # distinct users, peak concurrent sessions, cumulative duration of sessions and a session:user ratio.
The utility can be used to analyze peak concurrency events, solution adoption, most active users (and candidates for Named Cals), and it drills down to individual session details (sessions tab). Use the trend chart on the concurrency tab to drill down to the minute level of detail !
Hope you find it handy and feel free to send me your suggestions.
Hi Jonathan Poole - nice tool but I think it's a bit hidden away here. Have you considered posting it as a Document (and maybe tagging it with "Performance" also) so it reaches a wider audience?
Hi, Jonathan-- This is a great tool. Peak concurrency makes sense to me -- the most users with simultaneous sessions. I'm having trouble understanding the Peak User:Session Ratio, though. What is this telling you? The definition is (Total Users)/(Peak Concurrency). Can you explain what this is or why you would want to know this?
Imagine you want to review your user activity and find out if Named CALs or Session CALs would have been better. The Distinct users / peak concurrency tells you what your ratio is. I think if you have 11:1 or greater (like 15:1 or 20:1) , session CALs are a cheaper way to go, and that is to say, if you had just enough session CALs to cover your peak concurrency you are in a cheaper option (not to mention its way easier to manage QV with session CALs ... no user assignments !!) .
If your ratio is low (like 5:1) than named users it the way to go. It means your users are BUSY and if you had sessions they would be occupying them forcing you to buy more.
If you hit the 'top users' tab and select your high frequency users, and then EXCLUDE the selection (so that you get everybody but the top 10), notice how the ratio may greatly change. This means you may need to license your busy users with named CALs because their ratio is very low, and license everybody else with sessions.
Typically, named Users for very busy users + session license for everybody else is the way to maximize the simplicity of session CALs without getting burned on the cost of high frequency users.
Make sense ?
Is the file in your first post the most current?
I've modified my copy several times and want to make sure I'm not drifting too far from your copy.
Added Top Applications tab with the below objects
Top 15 apps - total session count (stacked bar chart - shows users for each app)
Top 15 Apps - Cumulative session duration (stacked bar chart - shows users for each app)
Added a Misc Stats tab that shows usage counts by day (stacked bar chart showing apps)
Added a "PROD / Non-PROD" application tag so I can filter on the production applications (we run some development / staging apps on the prod server)
V12: for QVWName expression - changed '\' to '/', fixed the prod / non-prod grouping
Hi John - yes it is. I had one additional copy that i haven't shared that can read session logs from different folders with the intention that the user create different folder names for each server and place the respective session logs from each server into those folders. BUt the only change that came with that update was basically a list box to select your server.
If you are interested in that , i can share and then you can copy/paste the load script to your copy.