QM has a very detailed activity log, that you can usually find under the name localhost-date.txt
[root@dalet logs]# cd /usr/local/queuemetrics/tomcat/logs/
[root@dalet logs]# ll
total 1704
-rw-r--r-- 1 root root 204002 Oct 22 17:15 catalina.out
-rw-r--r-- 1 root root 1236275 Oct 20 19:22 localhost_log.2008-10-20.txt
-rw-r--r-- 1 root root 35527 Oct 21 13:59 localhost_log.2008-10-21.txt
-rw-r--r-- 1 root root 252935 Oct 22 17:15 localhost_log.2008-10-22.txt
For example, these lines are a successful login:
2008-10-20 11:19:36 StandardContext[/queuemetrics][31D52F5DE469DF0F11A03A6AE565276D] User 'demoadmin' belongs to class '3'
2008-10-20 11:19:36 StandardContext[/queuemetrics][31D52F5DE469DF0F11A03A6AE565276D] User 'demoadmin' owns keys 'USER QUEUE_AN USR_AGENT USR_QUEUE USRADMIN REALTIME AGREP CALLMONITOR USR_LOCATION USR_OUTCOME USR_PCODE RTLIVE CHPASSWD MON_AUDIO MON_VNC USR_MYSQL'
As you can see there is a session identifier ID (the [31D52F5DE469DF0F11A03A6AE565276D] ) that you can use to find further verbs that are linked to the same log-on session - using this approach, access to each and every function of QM can be audited if needed.