"who is using my app?" is vague?
Do you mean I wonder who logged into my SAAS app today (or this week)?, OR
I wonder what users logged in today?, OR
I wonder who is currently in my system right now?
If you are viewing a query, and go to lunch and come back 3 hours later (like Bruce usually does), if your timeout was set to 10 mins, you can see a Log message (if your Logging was on) of Aware getting the Logout notification (and whatever code runs at that point).
I wonder what the mechanism is that Aware uses to activate the timeout?
Like... if its 10 minutes, who initiates the actual timeout...
a) does it happen the next time the users refreshes the screen (I don't think so. he may get a timeout msg, but the Logout Notification has already happened.)
b) does Aware have an internal in-memory table with a timestamp for when this session is void? and if so, then that time gets pushed back each time some traffic happens on that thread. (I think this is YES) -- And, this might be the LIRU table?
I use code (at Login & Logout) to update a Login Status table that looks like this:
(Note, I just logged in to generate this page)

This has been around for ages.
The only issue is that as you make longer timeouts, then lots of users appear to be logged in (when they may be out a a long lunch with Bruce).
Now, since Aware has evolved (like now individual users can have diff. Timeout durations), I'd argue that not all things concerning Timeouts and User Monitoring have evolved at the same pace. Perhaps whats needed is an improvement by Vlad to store/make available/save into LIRU,etc., the LAST ACTIVITY TIMESTAMP. While this wouldn't have anything to do with Timeouts, per se, it WOULD help system admins monitor user usage and ultimately "see who is using my app".
If you're trying to see if its OK to publish an update and I wonder how many people will get kicked, then running the User Login Status process AND seeing how many mins IDLE will be of great value.