You can use Splunk, or any log aggregation tool of choice, to parse through Pega logs across all your applications. In this video, Pawel Szewczul will show you how Pega IT leverages Splunk across multiple Pega Infinity applications.
To see our complete collection of videos, refer to this Support Video search link, which picks up all new Support Videos as they are posted.
Did you find this content helpful?
Want to help us improve this content?
@MarcDumas : How are Pega Logs sent to Splunk in JSON format , does all OOTB logs generated by Pega go to Splunk in JSON format ?
@Adithya_Acharya we have checked with the SME who provided this content.
The answer to your question is "yes".
"Pega Platform log appender sends in JSON format. We believe that this change was made a few revisions back. It’s all based on the pattern in log4j.
Our checks of our Splunk logs reveal that everything comes in as JSON.
Splunk will create what it thinks might be “interesting” and you can also create your own fields by parsing the raw message".
@MarijeSchillern/ @MarcDumas : Can you please let me know the configuration that needs to be done in Log4j to send all Pega OOTB logs in JSON format
Also one question on below statement , Does this mean that in PegaRules.log we see raw logs (i.e non-JSON format) , but while sending it to splunk its sends in JSON ?
"Pega Platform log appender sends in JSON format. We believe that this change was made a few revisions back. It’s all based on the pattern in log4j.
@Adithya_Acharya our SME @NASEB is unavailable to answer but we will chase up your question for you next week.
@MarijeSchillern We are looking for this config too, we are on-premise. Can you please share the changes made in prlog4j2.xml file to print the logs in JSON format?
@Sandeep_Ghosh @Adithya_Acharya the SME has passed on the following information:
"
The configuration really depends on whether or not the user is using PegaCloud or not.
In PegaCloud, the formatting is already set to json in most cases (but not all).
For on-prem or self-managed platform deployment, the pattern is configured in the prlog4j2.xml (embedded in the prweb.war file. ( /prweb/WEB-INF/classes). The current format is raw text.
However it is not recommended to change the prlog4j2.xml file. Log aggregation tools such as Splunk can easily parse PegaRules.logs or the use of RegEx can assist in the parsing.
"
you can clone PegaRules Log appender and add below code , this will log all pega OOTB logs in JSON format
@Adithya_Acharya This is what I was looking for, Thank you for sharing! It's working now. :)
