Question
LTIMindtree
SA
Last activity: 20 Sep 2022 6:11 EDT
How to amend the Application Logs Logging Format from .gz to .zip file
In the Provided Helm Charts by Pega, Default Compression format goes with .gz for all the Logs. However, Most of the cases, Application Logs downloaded in .gz format are not readable in the Pega Tools. To Resolve the Issue, We have to list the files in .gz format and Unzip it with Command: gzip -d <file-name> and proceed further to download the logs.
This post is to find the alternate way to address the concern.
Accepted Solution
Updated: 20 Sep 2022 6:11 EDT
LTIMindtree
SA
Root Cause Identified:
It has been identified that, In our cluster configurations, Log file encoding format which was in practice already was UTF-16 however Pega recomendation is to follow UTF-8 encoding format is the reason for downloaded files are not readable from .gz and had to manually unzip the files in the POD shell itself and perform the download.
Note: Checking internally on possibility to amend the Log file encoding format.
Updated: 23 Aug 2022 8:44 EDT
LTIMindtree
SA
Found a way to achieve the Log files Compression format.
In the Provided Helm Charts, \config\deploy and identify prlog4j2.xml file.
In the File compression format once you edit the file, Please change the .gz to .zip whereever it's necessary. Sample updated file (pdf format of prlog4j2.xml) attached here for your reference.
Going to Test it in our PP environment soon. Will post the updates again upon verifying the changes.
Updated: 20 Sep 2022 6:11 EDT
LTIMindtree
SA
Upon following the above steps, Zip file format is changed successfully. However, Upon downloading the .zip files, Files are not being extracted due to In-sufficient packages support in the Image.
It's indeed required to add the Zip and Unzip packages while Building the Pega Image along with necessary permissions to support my requirement. Added the necessary screenshots for reference.
I'll Post the Detailed steps (end - to - end) on how to achieve this eventually.
Accepted Solution
Updated: 20 Sep 2022 6:11 EDT
LTIMindtree
SA
Root Cause Identified:
It has been identified that, In our cluster configurations, Log file encoding format which was in practice already was UTF-16 however Pega recomendation is to follow UTF-8 encoding format is the reason for downloaded files are not readable from .gz and had to manually unzip the files in the POD shell itself and perform the download.
Note: Checking internally on possibility to amend the Log file encoding format.