[asterisk-bugs] [Asterisk 0017082]: [patch] Improve realtime queue logging
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jun 23 15:06:31 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17082
======================================================================
Reported By: coolmig
Assigned To:
======================================================================
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-23 15:06 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.
======================================================================
----------------------------------------------------------------------
(0123790) tilghman (administrator) - 2010-06-23 15:06
https://issues.asterisk.org/view.php?id=17082#c123790
----------------------------------------------------------------------
I took a look at your configuration, and I figured that a much better way
to implement this would be to use the adaptive realtime features, plus an
additional configuration option, which allows the current behavior to
remain, which avoids breaking any existing setups, while at the same time
permitting an upgrade to the capabilities that you've described here.
For legacy reasons, I have not altered any fields other than the data
fields, though, due to the ability of adaptive realtime, we could model
those, as well.
Testing and feedback would be appreciated.
Issue History
Date Modified Username Field Change
======================================================================
2010-06-23 15:06 tilghman Note Added: 0123790
======================================================================
More information about the asterisk-bugs
mailing list