It is sometimes desirable to obtain a snapshot of the reports QueueMetrics produces at a given moment in time for future access or for uniformity of comparison. You may, for example, want to store on disk a snapshot of the current daily activity every day at 19.00, fur future reference.
The ROBOT profile was thought for this purpose: automating access to the wealth of statistics that QueueMetrics is able to provide.
To set this up, first make sure that you have at least one user holding the key ROBOT that is used for remote access. A sample user called robot password robot is provided in the sample database that ships with QueueMetrics.
![[Note]](../images/icons/note.png){kind=icon} | Note |
|---|---|
For security reasons, this user must be manually enabled in the standard database. |
Point your browser to the QueueMetrics server with a URL like the following:
http://server/queuemetrics/qm_rep.do?user=robot&pass=robot&queues=q1&period=t0
will download today’s report - the full version - for queue "q1", while the following one
http://server/queuemetrics/qm_rt.do?user=robot&pass=robot&queues=q1|q2
or, for the ajax based page version
http://server/queuemetrics/qm_rt_ajax.do?user=robot&pass=robot&queues=q1|q2
will download the realtime page for queues "q1" and "q2", and
http://server/queuemetrics/qm_wab.do?user=robot&pass=robot&queues=q1|q2
or, for the ajax based page version
http://server/queuemetrics/qm_wab_ajax.do?user=robot&pass=robot&queues=q1|q2
will download the realtime wallboard for queues "q1" and "q2".
It is then easy to automate this behaviour using an automated downloader, like for example the wget command in the Unix environment.
The following web parameters are accepted by the qm_rt (realtime page) and qm_rep (report page) generators:
| Parameter | Notes | WAB | RT | REP |
|---|---|---|---|---|
user | The user name. Mandatory. | X | X | X |
pass | The user password. Mandatory. | X | X | X |
logfile | The log file to use ( with full path). If not defined, the default one will be used. | X | X | X |
queues | One or more queues to be analyzed. Use the pipe symbol to separate multiple entries. Use the Asterisk name for each queue. | X | X | X |
reportname | The wanted dynamic report name. If this parameter is not specified, the default report will be shown. If the report name contains special characters, they should be properly encoded (for example with %20 for spaces) | X | ||
period | The time period to use. Composed by a single letter plus the number of days to report about. t0: today - t1: yesterday d1: last 24hrs - d2: last 48 hrs | X | ||
filter | A single agent’s name, like Agent/123, that will be used a s a filter for the analysis. | X | ||
t_from | Initial time, expressed in the format yyyy-MM-dd.HH:mm:ss, e.g. 2006-01-03.12:00:00. | X | ||
t_to | Ending time, expressed in the format yyyy-MM-dd.HH:mm:ss, e.g. 2006-02-04.03:00:00. | X | ||
reloads | Always set to 1 if the session is to generate a reloadable page. Do not use for general report extraction. | X | X |
If you run a report, a time interval must be specified, i.e. you have to supply either a "period" or a "t_from"/"t_to" couple.
In addition to the key ROBOT, your user will need the key QUEUE_AN for reporting and REALTIME for realtime monitoring.
By using the ROBOT profile in conjunction with reloads=1, it is quite simple to set-up an unattended wallboard for QueueMetrics.
First of all set up a low-cost Linux box to boot in its graphical environment, automatically launch a web browser and go to the following URL:
http://server/queuemetrics/qm_wab.do?user=robot&pass=xxx&reloads=1&queues=q1|q2
or, for the ajax based page version
http://server/queuemetrics/qm_wab_ajax.do?user=robot&pass=xxx&reloads=1&queues=q1|q2
This command will show an auto-reloading wallboard showing the real-time status of queues Q1 and Q2.
If you connect the new Linux box to a large screen or a video beamer and set it in your call-center where it will be visible by your agents, you have just set-up a wallboard at a very low cost using commodity hardware and requiring no human intervention but turning it on in the morning and turning it off in the afternoon.
You can do the same with the real-time screen by using the qm_rt.do or the qm_rt_ajax.do commands to create a very simple real-time monitor running all day long for your supervisors.
![[Important]](../images/icons/important.png){kind=icon} | Important |
|---|---|
Please note that there is a difference between results produced by the XML rpc realtime calls and the realtime statistics produced through the QueueMetrics GUI when the key realtime.members_only is equal to true. The difference is related to the agents list shown. Being the list of queues, in the XML RPC call, specified by a list of names instead of a list of queue unique identifiers, is not possible to correctly identify elementary queues from macro queues having the same name. In this situation the agent list will always be calculated as sum of all agents associated to all elementary queues composing the macro queue, even if the macro queue has directly assigned agent. |