You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@vcl.apache.org by "Josh Thompson (JIRA)" <ji...@apache.org> on 2019/01/30 16:16:01 UTC

[jira] [Commented] (VCL-1091) Add Log4Perl as a option for producing vcld logs

    [ https://issues.apache.org/jira/browse/VCL-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756270#comment-16756270 ] 

Josh Thompson commented on VCL-1091:
------------------------------------

I'm untagging this as 2.5.1. We can look at incorporating it in a later release.

> Add Log4Perl as a option for producing vcld logs
> ------------------------------------------------
>
>                 Key: VCL-1091
>                 URL: https://issues.apache.org/jira/browse/VCL-1091
>             Project: VCL
>          Issue Type: Improvement
>          Components: vcld (backend)
>            Reporter: Mike Jennings
>            Priority: Minor
>
> It would be beneficial to use the Log4Perl module as a option for generating output logs from the vcld daemon.
> The idea would be to change the notify subroutine to call two new subroutines and pass the current inputs to them.  One subroutine will be for the new Log4Perl module output, the other subroutine will be for the original logging.
> The user should be able to enable or disable the logging of either one of these methods by setting values in the vcld.conf file.
> The reason to create a new method for logging will be that this will provide the administrator with a flexible way to customize the output pattern of the log, location, and logging level of the output in a centralized configuration file.  This will come in handy when pushing data to a centralized logging server where information is parsed out based on patterns.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)