-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
On Sunday 25 Nov 2012, Dmitry wrote:
[snip]
3) Still know nothing about odbc support for queue_log
Happily using ODBC (PostgreSQL, but should be mostly DB-independent) for
queue_log here. The setup is a bit hairy, but can share if enough
people show interest.
Regards,
-- Raj
--
Raj Mathur
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
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
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
if I'm wrong.
Thanks,
Andrew
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Dmitry
Sent: Thursday, 22 November 2012 6:58 PM
To: asterisk-users@lists.digium.com
Subject: [asterisk-users] Queue_log into MySQL - best practices
Hi,
I
