[asterisk-bugs] [Asterisk 0017082]: [patch] Improve realtime queue logging
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jun 28 18:29:47 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17082
======================================================================
Reported By: coolmig
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 17082
Category: Applications/app_queue
Reproducibility: always
Severity: feature
Priority: normal
Status: ready for testing
Asterisk Version: SVN
JIRA: SWP-1164
Regression: No
Reviewboard Link: https://reviewboard.asterisk.org/r/731/
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-23 11:06 CDT
Last Modified: 2010-06-28 18:29 CDT
======================================================================
Summary: [patch] Improve realtime queue logging
Description:
I was playing with the RT queue log functionality, and found this
limitations:
1. If you choose RT queue logging, you won't have the traditional plain
text file file log. This file is very useful for backup purposes.
2. The column 'data' stores all the parameters separated by '|', which is
not the best way to store it.
I managed to program a patch which overcomes this limitations, and works
this way:
1. If you enable RT queue logging, the queue log will still be logged in
the plain text file, so you have some backup in case of some database
disaster.
2. The parameters are now "exploded", and put in separate fields for each
one. The only thing here is that this code must be changed in case that
some queue log event delivers more than 4 parameters (the only event that
gives 4 parameters is TRANSFER).
3. The calldate is now stored just like the CDR, with a full datetime.
4. The plain text file is left as is, for compatibility purposes.
5. The fieldnames on the table changed a little.
======================================================================
----------------------------------------------------------------------
(0123985) coolmig (reporter) - 2010-06-28 18:29
https://issues.asterisk.org/view.php?id=17082#c123985
----------------------------------------------------------------------
Yay it works! Without the 'time' field check, it enables the improved
behavior and it inserts records in the table like a charm:
id time callid queuename agent event
data1 data2 data3 data4 data5
3 28/06/2010 03:44:04 p.m. NONE NONE NONE QUEUESTART
4 28/06/2010 03:44:09 p.m. NONE NONE NONE QUEUESTART
5 28/06/2010 03:44:59 p.m. NONE NONE NONE QUEUESTART
6 28/06/2010 03:46:56 p.m. 1277765200.1 NONE Agent/1001 AGENTLOGIN
SIP/100-00000001
7 28/06/2010 03:48:47 p.m. 1277765326.2 pruebas NONE ENTERQUEUE
101 1
8 28/06/2010 03:48:47 p.m. 1277765326.2 pruebas Agent/1001 CONNECT
1 1277765326.3 0
9 28/06/2010 03:49:00 p.m. 1277765326.2 pruebas Agent/1001 TRANSFER
1101 default 1 13 1
10 28/06/2010 03:50:08 p.m. 1277765200.1 NONE Agent/1001 AGENTLOGOFF
SIP/100-00000001 192
But... testing the standard queue_log to file, it seems that it does not
work regardless of the realtime backend or the settings... I don't know
what could be wrong. I'll keep an eye on it.
Issue History
Date Modified Username Field Change
======================================================================
2010-06-28 18:29 coolmig Note Added: 0123985
======================================================================
More information about the asterisk-bugs
mailing list