<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Lenz, Thank you for your answer</div><div><span style="background-color: transparent;"><br></span></div><div><span style="background-color: transparent;">Here is what I think:</span><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><span style="background-color: transparent;"><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;">1) If I use an external Perl/Python daemon to parse queue_log and put it into the MYSQL database - I must also monitor this script (for example,to restart it in case of failure) although this external daemon is rather easy to maintain and it means an
"independence" from the DEPRECATED app_mysql.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;">2)If I use the app_mysql module- although it is very convenient (asterisk developers maintain it) but as it has a DEPRECATED status - I am afraid using this module (I am not sure about its future).</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;">3) Still know nothing about odbc support for queue_log</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style:
normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;">So I chose 1).</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><br></div><div><br></div> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Lenz Emilitri <lenz.loway@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> Dmitry <mbike2000ru@yahoo.com>; Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users@lists.digium.com> <br> <b><span style="font-weight: bold;">Sent:</span></b>
Thursday, November 22, 2012 3:36 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [asterisk-users] Queue_log into MySQL - best practices<br> </font> </div> <br>
<div id="yiv1828430150"><div>Hi Dmitry,<br></div><div>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 :)</div>
<div>l.</div><div class="yiv1828430150gmail_extra"><br><br><div class="yiv1828430150gmail_quote">2012/11/22 Dmitry <span dir="ltr"><<a rel="nofollow" ymailto="mailto:mbike2000ru@yahoo.com" target="_blank" href="mailto:mbike2000ru@yahoo.com">mbike2000ru@yahoo.com</a>></span><br><blockquote class="yiv1828430150gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif;"><div>Hi, </div><div><br></div><div style="font-style:normal;font-size:16px;background-color:transparent;">
I use asterisk 1.8.</div><div style="font-style:normal;font-size:16px;background-color:transparent;"> Currently I use a perl daemon to parse queue_log into MySQL. It works reliably.</div>
<div style="font-style:normal;font-size:16px;background-color:transparent;"><br></div><div style="font-style:normal;font-size:16px;background-color:transparent;">
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.</div>
<div style="font-style:normal;font-size:16px;background-color:transparent;"><br></div><div style="font-style:normal;font-size:16px;background-color:transparent;">
My question is:</div><div style="font-style:normal;font-size:16px;background-color:transparent;">What is the best/preffered approach to put queue_log into MySQL in asterisk 1.8 and up?</div>
<div style="font-style:normal;font-size:16px;background-color:transparent;">1) To use external daemons to parse /var/log/queue_log?</div><div style="font-style:normal;font-size:16px;background-color:transparent;">
2) To use the deprecated app_mysql? the status does not guarantee that this application will be in the future</div><div style="font-style:normal;font-size:16px;background-color:transparent;">
3) To use odbc to access mysql? but I could not find a procedure for it. And I doubt it is possible.</div><div style="font-style:normal;font-size:16px;background-color:transparent;">
<br></div><div style="font-style:normal;font-size:16px;background-color:transparent;">BR,</div><div style="font-style:normal;font-size:16px;background-color:transparent;">
Dmitry Pavlenko</div></div></div></blockquote></div><br><br clear="all"><br>-- <br><div>Loway - home of QueueMetrics - http://queuemetrics.com<br></div><div>Test-drive WombatDialer beta @ http://wombatdialer.com
</div><br>
</div>
</div><br><br> </div> </div> </div></body></html>