{"id":42988,"date":"2022-05-06T15:58:44","date_gmt":"2022-05-06T15:58:44","guid":{"rendered":"https:\/\/polarising.com\/techinside\/?p=42988"},"modified":"2022-08-29T16:08:01","modified_gmt":"2022-08-29T16:08:01","slug":"mulesoft-log4j2-vs-json-logger","status":"publish","type":"post","link":"https:\/\/polarising.com\/techinside\/mulesoft-log4j2-vs-json-logger\/","title":{"rendered":"Mulesoft: Log4j2 Vs JSON Logger"},"content":{"rendered":"\n
<\/div>\n\n\n\n
<\/span>
\n

<\/p>\n<\/div><\/div>\n\n\n\n

<\/div>\n\n\n\n

Polarising\u2019s Mulesoft CoE t<\/a>eam has been exploring Mulesoft technology almost a year from now. One of our first findings is related to the importance of logs in the analysis and tracking of requests, and this article is dedicated to this subject and to understand where the transactions are.<\/p>\n\n\n\n

As a log utility we discovered that Apache Log4j2<\/a> Mulesoft plugin provides a set of features to facilitate the publication of messages to the queueing system used, Apache ActiveMQ<\/a>. That information will then be the source data for analytical purpose and that will feed external tools like ELK Stack<\/a> (ElasticSearch, Logstash and Kibana).<\/p>\n\n\n\n

<\/div>\n\n\n\n
<\/span>\"mulesoft
\n

<\/p>\n<\/div><\/div>\n\n\n\n

Image: Solution architecture for the case study with Log4J2.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Log4j2 default in Mulesoft<\/h2>\n\n\n\n
<\/div>\n\n\n\n
\"\"
Image: Mulesoft and Log4j2 logos.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Log4j2 in Mulesoft is generic, meaning, for those who\u2019ve worked with logging technology you will see the same configuration patterns. By default, logs in Mulesoft are written to a file on the application server, but these artifacts can be sent to other destinations such as Database, SMTP or even JMS Queue.<\/p>\n\n\n\n

This last was the one chosen to perform the proof of concept. Challenging, don’t you think?<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"
Image: Example of a default log4j2.xml file.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n
\"\"
Image: Example of a log generated by the Mulesoft application.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

In the world of technology, it is said: \u201cCome and do what has not yet been done.\u201d And in this case, it was no different. We had several difficulties, but always with a clear goal of the final solution.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"
Image: JMS Configuration in log4j2.xml.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n
\"\"
Image: Example of a log message in a Queue in Apache ActiveMQ.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

To this implementation, we have considered the following features of JMS in Log4j2:<\/p>\n\n\n\n