QueueMetrics > Running QueueMetrics

lag upon retrieving call details // verbose logging

(1/2) > >>

qmax:
On the page with activity reports detalization:
results_calls_ok.jsp
results_calls_ko.jsp

pressing "details" popup button
sometimes lags for very long (more then 10 seconds)
it appears at $Id: LocalFiles.java,v 1.3 2009/02/16 11:40:28 lenz-mobile Exp $ is searching....

the system was not high loaded at the moments.

i'd like to make queuemetrics more verbose in logging
to detect the bottleneck.



QueueMetrics:
I tell you what it is: you have too many audio recordings, and QM wil scan all them.

You should use a PM like LocalFilesByDay to reduce searching - see here: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s17.html#_pms_to_match_recorded_calls

qmax:

--- Quote from: QueueMetrics on June 24, 2009, 17:53:04 ---I tell you what it is: you have too many audio recordings, and QM wil scan all them.

You should use a PM like LocalFilesByDay to reduce searching - see here: http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s17.html#_pms_to_match_recorded_calls

--- End quote ---

we have about 200 000 records, keeping them several month.
is this number large for default record finder ?

all recording configured to form filenames exactly as "q${QUEUEID}-${UNIQUEID}.wav"
this way there's no need to scan all files, but record finder knows exactly what filename is.
we used our own record finder, that utilized this feature.

is there such PM exists or planned ?

QueueMetrics:
The best thing would be to split up the directory structure - maybe dividing them simply like /year/month or /year/month/queue - and using the LocalFilesByDay PM.

qmax:
ok.
i've set up it this way:
audio.server=it.loway.app.queuemetrics.callListen.listeners.LocalFilesByDay
default.monitored_calls=/var/spool/asterisk/%QU/
and restarted queuemetrics

now i have:
astra:/var/spool/asterisk/monitor # find -name '*1247745633.22860*'
./6/q6-1247745633.22860.wav

but details popup only shows Call ID, but not link to file.

what's wrong here ?

Navigation

[0] Message Index

[#] Next page

Go to full version