QueueMetrics > Running QueueMetrics

Realtime page shows wrong information

(1/1)

tonils:
Hi

In the screenshot below, the second call being processed has a waiting time of 0:32. This can not be?!? The call is marked as entered at 9:27:18 and you can (almost) see the time of the page as 09.27.22. I would have thought that the waiting time shhould be 0:04 at most. QueueMetrics and asterisk run on the same server.

Here are the queue_log entries for the call
1234769238|1234769221.186809|9001|NONE|ENTERQUEUE||XXXXXXXXXX
1234769243|1234769221.186809|9001|Agent/1059|CONNECT|5|1234769238.186816
1234769372|1234769221.186809|NONE|Agent/1059|CALLSTATUS|dcd||
1234769376|1234769221.186809|9001|Agent/1059|COMPLETECALLER|5|133|1

Can you help me find out why this appears wrong?

Tony

QueueMetrics:
This is an easy one: the "live" data (green and red) is calculated against the local clock; so if the clock between Asterisk and the QM server is off by a few seconds, you will see wrong times (and sometimes even negative numbers).

Please go to the "Licence" page and see if the clocks of Asterisk, QM and MySQL are aligned.

tonils:
Hi Lorenzo

That was my first thought, As mentioned, QueueMetrics is running on the same server as ASterisk. The licencing page states that "MySQL Time is aligned with Java Time"

Is the local PC clock involved at all?

Tony

QueueMetrics:
No, it's all server-side. Are you 100% sure that it's the same call you are seeing? i.e., if you go to the reports and click on it, you see that its Asterisk-isd is "1234769221.186809" ?

tonils:
Yes, if I look at the detail in the reports, it is correct

Navigation

[0] Message Index