You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Andy Kurth (JIRA)" <ji...@apache.org> on 2013/06/06 19:13:20 UTC
[jira] [Created] (VCL-707) Improve ability to parse vcld.log
Andy Kurth created VCL-707:
------------------------------
Summary: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira