Logging and Monitoring

1. Types of logs in Anypoint Platform
Logging plays an inseparable parts in software engineering & it guides system administrator, support
engineers & developers to troubleshoot an issue as quickly as possible, different types of logs in Anypoint
platform below:
• System Log: It is specific to MuleSoft runtime & “log4j.xml” configuration file is not accessible to an user.
System logs contains log messages about the MuleSoft runtime life cycle (startup and shutdown) & status
messages about MuleSoft application.
• Application Log: It is specific to MuleSoft application & “log4j.xml” configuration file is packaged inside
MuleSoft application. It contains all log messages generated inside the Mule application, including
System.Out messages. We can configure custom log file appender to send application log data outside of
cloudhub to external log file appender like Splunk.
• Audit Log: It logs user interactions within Anypoint Platform, including logins, business groups creation,
and environments creation. Only the organization owner can access all the audit logs data. It is useful to
detect the access violations.

2. JSON Logger Configuration
This configuration allows you to seamlessly
forward log entries to the following supported
destinations: Anypoint MQ, JMS and AMQP

3. • Log levels monitors the logging in Anypoint platform. An inadequate
logging level will lead either to missing significant messages or to
flood the logs with a lot of less important records.
• Find out the different log levels & the guidelines for its usage :
• DEBUG level logs messages which could be useful in debugging an
issue
• INFO level is designated for information related messages which
tracks the progress of the mule flow
• WARN level is best suited for temporary problems or unexpected
behaviour
• ERROR level should contain technical issues that need to be resolved
for proper functioning of the application
• Log level order/priority : DEBUG < INFO < WARN < ERROR
Log levels
Log level order

4. • Message logging policy in API Manager enables to log custom messages between policies & flow. This policy
is capable of logging messages like incoming request payload, outgoing response payload, request attributes,
response attributes etc. It is listed under “Troubleshooting” category
https://docs.mulesoft.com/policies/policies-included-message-logging
• Log point (also known as codeless logging) features in Anypoint platform allows to generate logs for apps and
APIs in real-time and without writing any code [Titanium subscription & Manage setting permission in runtime
manager is required to use log points]. It monitors & logs API request attributes such as path, host, method,
request body etc. It also logs API response attributes such as status code, connection, response body etc.
https://docs.mulesoft.com/monitoring/log-points
Message logging policy & Log point

5. • Best practices for application logging is:
• To capture contextual, relevant & meaningful information which doesn’t add any overhead
• To provide log category in logging component because it will classify the log message & helps to determine
whether to log the category/package in production or not
• To use JSON logger to standardize the logging format in JSON structure. It comes with a lot of advantages. Find
the details in the following reference :
• https://blogs.mulesoft.com/dev/anypoint-platform-dev/json-logging-mule-4/
Best Practices for application logs