Part of the problem may be that we changed the binary log format to have IP as a distinct type, rather than encoding it as a string. That likely made us incompatible. I checked the squidpeek site and its like to squid-cache.org but couldn't find any specification for the squid log format.
Friday, February 24, 2012, 11:20:40 AM, you wrote: > I'm using Calarmaris to parse and get some basic stats from the logs. It > can output in HTML and get graphs too. > Andrew > On 24/02/2012 17:15, "Brendan Webb" <[email protected]> wrote: >>Yup. I'm using traffic_logstats to output a summary, which is great. I'm >>also using Squidpeek, which Mark Nottingham was kind enough to tweak in >>order to get working with ATS' logs. >>However, I'd like to be able to use something like Webalizer to provide >>additional log file analysis. >>On Feb 23, 2012, at 10:37 PM, Nick Berry wrote: >>> Brendan, >>> Have you looked at traffic_logstats? Human readable format as well as >>>json output. >>> On Feb 23, 2012, at 4:16 PM, Brendan Webb wrote: >>>> Is anyone successfully using a Squid log analysis tool with Traffic >>>>Server's Squid-formatted logs? Each Squid log analysis tool I try >>>>returns errors processing the lines in my Traffic Server logs.
