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" <[email protected]> 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 >
-- _____________________________________________________________________ -- 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
