[
https://issues.apache.org/jira/browse/VCL-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Peeler resolved VCL-707.
------------------------------
Resolution: Fixed
tested. Was able to load .log file into excel and parse easily.
> Improve ability to parse vcld.log
> ---------------------------------
>
> Key: VCL-707
> URL: https://issues.apache.org/jira/browse/VCL-707
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Priority: Minor
> Fix For: 2.4
>
>
> The lines in vcld.log are deliminated by a '|' pipe character. This makes is
> easy to split up the lines with grep or when imported into a spreadsheed.
> There are some problems with the current vcld.log output which causes fields
> to not appear in the same column in excel if you do a Text to Columns with
> the '|' deliminator.
> For multiline messages, the date and calling sub are only written to the
> first line to reduce the log size:
> 2013-06-06 13:03:58|24316|2375:3115|test|utils.pm:mysub(4500)|:first line
> |24316|2375:3115|test| : 2nd line
> When split up in Excel, the '2nd line' text will be placed under the
> 'utils.pm' field becuase there is an extra '|' deliminator in the first line.
> If you try to analyze the occurances of lines generated by a particular
> subroutine, you have to take an extra step of ignoring the line number. It
> would be helpful if the line number were deliminated by '|'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
