Logz.io Logging for MuleSoft using HTTP Appender

Note: While copy/paste the code snippet from blog please covert quotes and double quotes.

In this blog we will try to learn how we can send logs to Logz.io from Mulesoft using HTTP Appender.

What is Logz.io?

• Logz.io provides log management and log analysis services.
• The platform combines ELK as a cloud service and machine learning to derive new insights from machine data.

Register with Logz.io:

• Go to https://logz.io/
• Click on Free Trial if not already have account

Logz.io

Generate Token:

• Go to https://logz.io/
• Click On Login
• Provide credentials
• Go to Gear Button -> Settings -> General

Settings -> General

• Copy Token

Token

Enable Custom Logging For On Premise MuleSoft Runtime:

• Go to Project
• Open src/main/resoruces/log4j2.xml
• Add below xml tag in Configuration/Appenders

<Http name=”Logzio” url=”http://listener.logz.io:8070/?token=kILyrCdlJyvKFeCtSyuQMgSFkCACtWdd&amp;type=MuleSoft">
 <PatternLayout pattern=”{&quot;message&quot;:&quot;%-5p %d [%t] %c: %m&quot;}%n” />
</Http>

• URL follow below format

http://<logzio-server>:<port>/?token=<token>&type=<log-type>

• Add below xml tag in Configuration/Loggers/AsyncRoot

<AppenderRef ref=”Logzio” />

• Run Application
• See the Console Log

Application Logger Console

• Go to https://logz.io/
• Kibana
• Click on Refresh

Kibana -> Logs

Enable Custom Logging For CloudHub Application:

Before enabling the logging for cloudhub application, you need Disable CloudHub logs. By default this option is not available and you need to raise a ticket with MuleSoft for providing this option.

Anypoint Settins

Once you disabled cloudhub logs, MuleSoft is not responsible for below things

• MuleSoft is not responsible for lost logging data due to misconfiguration of your own log4j appender.
• MuleSoft is also not responsible for misconfigurations that result in performance degradation, running out of disk space, or other side effects.
• When you disable the default CloudHub application logs, then only the system logs are available. For application worker logs, please check your own application’s logging system. Downloading logs is not an option in this scenario.
• Only Asynchronous log appenders can be used, Synchronous appenders should not be used.
• Use asynchronous loggers and not synchronous ones is to avoid threading issues. Synchronous loggers can lock threads waiting for responses.

You need to create log4j2.xml at location src/main/resources.

MuleSoft Application Folder Structure

You need to add a Http appender inlog4j.xml. Provide url to connect Logz.io with token and type of logger, source, pattern layout etc.

<Http name=”Logzio” url=”http://listener.logz.io:8070/?token=kILyrCdlJyvKFeCtSyuQMgSFkCACtWdd&amp;type=MuleSoft">
 <PatternLayout pattern=”{&quot;message&quot;:&quot;%-5p %d [%t] %c: %m&quot;}%n” />
</Http>

You can add more loggers like Log4J2CloudhubLogAppender into your log4j2.xml to enable logging on the cloudhub log console of your application.

<Log4J2CloudhubLogAppender name=”CLOUDHUB”
 addressProvider=”com.mulesoft.ch.logging.DefaultAggregatorAddressProvider”
 applicationContext=”com.mulesoft.ch.logging.DefaultApplicationContext”
 appendRetryIntervalMs=”${sys:logging.appendRetryInterval}”
 appendMaxAttempts=”${sys:logging.appendMaxAttempts}”
 batchSendIntervalMs=”${sys:logging.batchSendInterval}”
 batchMaxRecords=”${sys:logging.batchMaxRecords}” memBufferMaxSize=”${sys:logging.memBufferMaxSize}”
 journalMaxWriteBatchSize=”${sys:logging.journalMaxBatchSize}”
 journalMaxFileSize=”${sys:logging.journalMaxFileSize}”
 clientMaxPacketSize=”${sys:logging.clientMaxPacketSize}”
 clientConnectTimeoutMs=”${sys:logging.clientConnectTimeout}”
 clientSocketTimeoutMs=”${sys:logging.clientSocketTimeout}”
 serverAddressPollIntervalMs=”${sys:logging.serverAddressPollInterval}”
 serverHeartbeatSendIntervalMs=”${sys:logging.serverHeartbeatSendIntervalMs}”
 statisticsPrintIntervalMs=”${sys:logging.statisticsPrintIntervalMs}”>
 <PatternLayout pattern=”[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]: %m%n” />
</Log4J2CloudhubLogAppender>

Below is full log4j2.xml which can be used for your application for enabling custom logging on cloudhub and http appender for logz.io.

<?xml version=”1.0" encoding=”UTF-8"?>
<Configuration status=”INFO” name=”cloudhub”
 packages=”com.mulesoft.ch.logging.appender,org.apache.logging.log4j”>
 <Appenders>
 <Log4J2CloudhubLogAppender name=”CLOUDHUB”
 addressProvider=”com.mulesoft.ch.logging.DefaultAggregatorAddressProvider”
 applicationContext=”com.mulesoft.ch.logging.DefaultApplicationContext”
 appendRetryIntervalMs=”${sys:logging.appendRetryInterval}”
 appendMaxAttempts=”${sys:logging.appendMaxAttempts}”
 batchSendIntervalMs=”${sys:logging.batchSendInterval}”
 batchMaxRecords=”${sys:logging.batchMaxRecords}” memBufferMaxSize=”${sys:logging.memBufferMaxSize}”
 journalMaxWriteBatchSize=”${sys:logging.journalMaxBatchSize}”
 journalMaxFileSize=”${sys:logging.journalMaxFileSize}”
 clientMaxPacketSize=”${sys:logging.clientMaxPacketSize}”
 clientConnectTimeoutMs=”${sys:logging.clientConnectTimeout}”
 clientSocketTimeoutMs=”${sys:logging.clientSocketTimeout}”
 serverAddressPollIntervalMs=”${sys:logging.serverAddressPollInterval}”
 serverHeartbeatSendIntervalMs=”${sys:logging.serverHeartbeatSendIntervalMs}”
 statisticsPrintIntervalMs=”${sys:logging.statisticsPrintIntervalMs}”>
 <PatternLayout pattern=”[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]: %m%n” />
 </Log4J2CloudhubLogAppender>
 <Http name=”Logzio” url=”http://listener.logz.io:8070/?token=kILyrCdlJyvKFeCtSyuQMgSFkCACtWdd&amp;type=MuleSoft">
 <PatternLayout pattern=”{&quot;message&quot;:&quot;%-5p %d [%t] %c: %m&quot;}%n” />
 </Http>
 </Appenders>
 <Loggers>
 <AsyncLogger name=”org.mule.runtime.core.internal.processor.LoggerMessageProcessor” level=”INFO” />
 <AsyncLogger name=”com.mulesoft.agent” level=”INFO” />
 <AsyncRoot level=”INFO”>
 <AppenderRef ref=”CLOUDHUB” />
 <AppenderRef ref=”Logzio” />
 </AsyncRoot>
 <AsyncLogger name=”com.gigaspaces” level=”ERROR” />
 <AsyncLogger name=”com.j_spaces” level=”ERROR” />
 <AsyncLogger name=”com.sun.jini” level=”ERROR” />
 <AsyncLogger name=”net.jini” level=”ERROR” />
 <AsyncLogger name=”org.apache” level=”WARN” />
 <AsyncLogger name=”org.apache.cxf” level=”WARN” />
 <AsyncLogger name=”org.springframework.beans.factory” level=”WARN” />
 <AsyncLogger name=”org.mule” level=”INFO” />
 <AsyncLogger name=”com.mulesoft” level=”INFO” />
 <AsyncLogger name=”org.jetel” level=”WARN” />
 <AsyncLogger name=”Tracking” level=”WARN” />
 <AsyncLogger name=”org.mule” level=”INFO” />
 <AsyncLogger name=”com.mulesoft” level=”INFO” />
 <AsyncLogger name=”org.mule.extensions.jms” level=”INFO” />
 <AsyncLogger name=”org.mule.service.http.impl.service.HttpMessageLogger” level=”INFO” />
 <AsyncLogger name=”org.mule.extension.salesforce” level=”INFO” />
 <AsyncLogger name=”org.mule.extension.ftp” level=”INFO” />
 <AsyncLogger name=”org.mule.extension.sftp” level=”INFO” />
 <AsyncLogger name=”com.mulesoft.extension.ftps” level=”INFO” />
 <AsyncLogger name=”org.mule.modules.sap” level=”INFO” />
 <AsyncLogger name=”com.mulesoft.extension.mq” level=”INFO” />
 <AsyncLogger name=”com.mulesoft.mq” level=”INFO” />
 <AsyncLogger name=”org.mule.extension.db” level=”INFO” />
 <AsyncLogger name=”httpclient.wire” level=”DEBUG” />
 <AsyncLogger name=”org.mule.transport.email” level=”DEBUG” />
 </Loggers>
</Configuration>

This is how you can enable Log.io logging using HTTP Appender for MuleSoft applications.