and more in a single search tool across platforms. Read the announcement here. |
04/12/2022 12:57 PM
Currently the logs are written to different debug files(IP specific) randomly which makes it difficult to troubleshoot issues as we have to check where the logs are written.
In one of the environment, we have 4 different debug files and their corresponding rotated files(log.1, log.2 etc.):
1. debugLog.log
2. debugLog-10.x.x.37.log
3. debugLog-10.x.x.39.log
4. debugLog-10.x.x.41.log
Firstly, what is the purpose of multiple debug files with different IP addresses?
Secondly, is there any way to always write logs in only ONE debug file. For example debugLog-10.x.x.37.log, so that if we want to check historic logs, we can just see that files and rotated logs files for 10.x.x.37?
Solved! Go to Solution.
04/12/2022 01:59 PM
Greetings!
1. In a multiple server environment, logs get added with IP postfixed with server IP of the server that processes the request
2. When file size becomes greater, it would be tougher to debug information, so we leverage javas logging mechanism (log4j) to log and rotate the older files once it reaches the limit set in configurations as per best practice standard
3. With newer release slated soon, we also have search and download feature which would enable you to search for a specific text and download only those files which have matching text
Hope above explanation clarifies
04/12/2022 01:59 PM
Hi Aarthi,
Regarding #1 - Thank you
Regarding #2 - Completely understand
Regarding #3 - Perfect. Is it planned to be available from v6.0 or v5.x service packs too?
04/12/2022 01:59 PM
Hi Ramanpreet,