All, I am looking for some feedback on my implementation of log4perl into the vcl management node code. The reason for this implementation was to provide a logging system that can be configured and maintained outside of the vcl code base. This now allows us to output a logging format, define outside of the vcld code base, that can be easily ingested into a logging management system like Splunk.
The log4perl api is based on the widely popular (Java-based) log4j package. They system is configured by editing the log.conf file located in the management nodes bin directory. In this file you are able to set the Logging Level, log output destination, the output pattern of the logs, and much more. Currently I have setup log4perl to run alongside the native logging provided by VCL. Currently the log4perl code is turned off by default, if you would like to enable it you will need to add the following line to your vcld.conf file. # log4perl: use the log4perl logging or not. # 1 = true # 0 = false (default) log4perl=1 You will also need to update the output location in the log.conf file located in the management nodes bin directory. Documentation can be found here at https://metacpan.org/pod/Log::Log4perl. Documentation associated with the pattern layouts here https://metacpan.org/pod/Log::Log4perl::Layout::PatternLayout Thanks again and any feedback or suggestion on how this could be enhanced would be greatly appreciated. Mike Jennings
