QueueMetrics > Running QueueMetrics

Logrotate & Queuemetrics Issue

(1/3) > >>

tsolaaa:
Hello Everyone,

We are running Queuemetrics 1.7.1.0 with Asterisk 1.8.3 and logrotate.

Every night at 12:00 we have logrotate run, when this happens any agents listed in the Real-Time page on QM disappears.

I'm guessing this happens because QM no longer sees the agents active in the logs and thinks they have left the queue.

Has anyone else had this issue or found a work-around?

Thanks!

marcos:
Hi.

If you're using a DB as a queue data source for QueueMetrics this is not related to the log-rotation of your queue_log file.
This is, more probably, something is reported to this FAQ: http://www.queuemetrics.com/faq.jsp#faq-020-midnight-rt

If, instead, you're using the queue_log file as a source, I suggest to install the qloader daemon and let it able to upload all events to QueueMetrics database. This is the best modality you can have to overcome to the log-rotation problem.

Thank you and regards,
Marco Signorini.

tsolaaa:

--- Quote ---If you're using a DB as a queue data source for QueueMetrics this is not related to the log-rotation of your queue_log file.
This is, more probably, something is reported to this FAQ: http://www.queuemetrics.com/faq.jsp#faq-020-midnight-rt
--- End quote ---

We are currently a 24/7 call center, could you recommend the correct value for realtime.startHour ?

Currently we are set at

#The hour of the day to start real-time monitoring or sXX: sliding window of XX hours
realtime.startHour=0

I want to avoid making any changes without knowing the possible implications.

Thank you.

QueueMetrics:
You should use a sliding window that is a couple of hours longer than an agent's longest shift, e.g. if they do 6 hours, set it to s8 for safety. Consider that the longer the sliding window, the more load QM takes when running a report.

tsolaaa:
So I have changed the value from "0" to "s12" since we have 3 separate shifts all working for 10 hours.

Is there any possibility of any future releases of QM to keep an agent state and keep track of who's logged in and out instead of parsing the log file every time? I understand the need for the sliding window for performance concerns, however once the sliding window expires and that agent has not logged out, QM stops reporting that agent, and then we start to accumulate "logged in" agents who aren't being shown in QM.

Thanks for your support.

Navigation

[0] Message Index

[#] Next page