Re: Parsing access.log

[Mihai Zsigmond]

Hi, Tajur is right. Although you may miss one or two messages which do not reach your script (I had a case like that recently). On the other hand, if is for billing and statistics, you don't need "realtime" parsing of the log, for instance a half-hour lag is perfectly acceptable. I have a script in Perl called from cron which parses the log and fills up a table in MySQL. If you need "to see if everything is working perfectly" it is a better idea to write a script for watching the status page of Kannel and take appropiate action if something is changed in that page (again called from cron at let's say every 5 minutes). Hope this could help... Best regards, Mihai Heru Tjatur wrote: On Mar 13, 2008, at 4:56 PM, Illimar Reinbusch - Telejazz.com wrote: Hi Has anyone done parsing access.log to somekind database, for example MySQL? I would need allmost realtime access to logs, to see if everything is working perfcetly, mainly needed by my supervisors for statistics and billing purposes. Why should use the hard-way? I add extra script to store any MT messages submitted before sending an MT-message, in get-url/exec for incoming MO messages, and finally updating their status with DLR hope this could help ... --tjatur Thanks, Illimar