QueueMetrics > Running QueueMetrics

Logrotate & Queuemetrics Issue

<< < (2/3) > >>

QueueMetrics:
But by using a sliding window that is longer than a single shift, you should be sure you always have data....

tsolaaa:
I am honestly not sure what you are saying.   :-\

In a perfect world, I would love to have all the agents log out at the end of the day and if not, have their supervisors do it for them, but that is not possible.

I am just looking for the best method to have Queuemetrics not drop logged in agents when the clock hits midnight.

Our current setting:

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

What can you recommend to be the best practice to have Queuemetrics not drop logged in agents at midnight, if we have three shifts (Morning, Noon and Grave), each lasting ten hours, being a 24/7 company.

I apologize for not understanding, but I do not what to change a setting without understanding how it fully works.

QueueMetrics:
Instead of starting from midnight, the sliding window will start looking for agent data at (say) minus ten hours from now, so if your shifts last (say) 8 hours, you are sure that you have data in the last 10 hours. Of course agents must log off at the end of a shift.

tsolaaa:
Our agents constantly forget to log out at the end of their shift. We do not have a way of forcing them to log out.

Therefore, we are trying to find the best method of having Queuemetrics keep reporting an agents status, even if they forget to log out at the end of their shift.

If I understand correctly, by using a sliding window, QM will gather agent data minus XX hours. (Whatever is set in the realtime.startHour=sXX)  However, this is still a limitation because

it will drop agents from the real-time page after the sliding window time expires.

I am asking if there is any way around this, so that QM will always report an agents status until that agent actually logs off.

QueueMetrics:
You could have a sliding windows of 2x the shift, but this adds a bit of load on the server.

Navigation

[0] Message Index

[#] Next page

[*] Previous page