Hi,? I use asterisk 1.8. ?Currently I use a perl daemon to parse queue_log into MySQL. It works reliably. But I know that there is a method (http://www.voip-info.org/wiki/view/Asterisk+queue_log+on+MySQL and http://work.mikeboylan.com/asterisk-queuelog-to-mysql) to write to MySQL directly with app_mysql which has a DEPRECATED status. My question is: What is the best/preffered approach to put queue_log into MySQL in asterisk 1.8 and up? 1) To use external daemons to parse /var/log/queue_log? 2) To use the deprecated app_mysql? the status does not guarantee that this application will be in the future 3) To use odbc to access mysql? but I could not find a procedure for it. And I doubt it is possible. BR, Dmitry Pavlenko -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20121121/e206a177/attachment.htm>
Lenz Emilitri
2012-Nov-22 09:36 UTC
[asterisk-users] Queue_log into MySQL - best practices
Hi Dmitry, we usually advise against writing queue_log events straight to a database, as it is marginally more likely that the DB has issues that a simple flat file. And when data is lost it's lost forever. Still everybody seems to love writing data straight to the DB :) l. 2012/11/22 Dmitry <mbike2000ru at yahoo.com>> Hi, > > I use asterisk 1.8. > Currently I use a perl daemon to parse queue_log into MySQL. It works > reliably. > > But I know that there is a method ( > http://www.voip-info.org/wiki/view/Asterisk+queue_log+on+MySQL and > http://work.mikeboylan.com/asterisk-queuelog-to-mysql) to write to MySQL > directly with app_mysql which has a DEPRECATED status. > > My question is: > What is the best/preffered approach to put queue_log into MySQL in > asterisk 1.8 and up? > 1) To use external daemons to parse /var/log/queue_log? > 2) To use the deprecated app_mysql? the status does not guarantee that > this application will be in the future > 3) To use odbc to access mysql? but I could not find a procedure for it. > And I doubt it is possible. > > BR, > Dmitry Pavlenko >-- Loway - home of QueueMetrics - http://queuemetrics.com Test-drive WombatDialer beta @ http://wombatdialer.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20121122/15e04cbd/attachment.htm>
Have you considered using something like Splunk to aggregate your log files and store a copy for later analysis? Even if you want it to be available to someone, say a remote customer, via a web panel, I believe you could even have Splunk put it into another database or make a view in Splunk's database. I believe that might work. On Nov 22, 2012 2:01 AM, "Dmitry" <mbike2000ru at yahoo.com> wrote:> Hi, > > I use asterisk 1.8. > Currently I use a perl daemon to parse queue_log into MySQL. It works > reliably. > > But I know that there is a method ( > http://www.voip-info.org/wiki/view/Asterisk+queue_log+on+MySQL and > http://work.mikeboylan.com/asterisk-queuelog-to-mysql) to write to MySQL > directly with app_mysql which has a DEPRECATED status. > > My question is: > What is the best/preffered approach to put queue_log into MySQL in > asterisk 1.8 and up? > 1) To use external daemons to parse /var/log/queue_log? > 2) To use the deprecated app_mysql? the status does not guarantee that > this application will be in the future > 3) To use odbc to access mysql? but I could not find a procedure for it. > And I doubt it is possible. > > BR, > Dmitry Pavlenko > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20121122/af22b2b4/attachment.htm>
Hi Dmitry, I've been using the below for a long time and it works perfectly. I've built a custom solution in terms of the tables. My understand of the external queue logging to MySQL is that it uses the Realtime engine to do so, so it's not affected by app_mysql directly. Please do correct me if I'm wrong. Thanks, Andrew From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Dmitry Sent: Thursday, 22 November 2012 6:58 PM To: asterisk-users at lists.digium.com Subject: [asterisk-users] Queue_log into MySQL - best practices Hi, I use asterisk 1.8. Currently I use a perl daemon to parse queue_log into MySQL. It works reliably. But I know that there is a method (http://www.voip-info.org/wiki/view/Asterisk+queue_log+on+MySQL and http://work.mikeboylan.com/asterisk-queuelog-to-mysql) to write to MySQL directly with app_mysql which has a DEPRECATED status. My question is: What is the best/preffered approach to put queue_log into MySQL in asterisk 1.8 and up? 1) To use external daemons to parse /var/log/queue_log? 2) To use the deprecated app_mysql? the status does not guarantee that this application will be in the future 3) To use odbc to access mysql? but I could not find a procedure for it. And I doubt it is possible. BR, Dmitry Pavlenko -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20121123/61e4bf0c/attachment.htm>