Pushing Mule Application Logs to Splunk

Introduction

Logging is an essential part of monitoring and troubleshooting issues and any production errors or visualizing the data. Logging must be consistent and reliable so we can use that information for discovering relevant data. Some external logging tools, including ELK and Splunk
MuleSoft, provide its logging mechanism for storing application logs. Although CloudHub has a limitation of 100 MB of logs or 30 days of logs. The blog typically talks MuleSoft Splunk Integration.

For a robust logging mechanism, it is essential to have an external log analytic tool to further monitor the application. Today we will be using Splunk as an external logging tool and integrating it with MuleSoft using Log4j2 HTTP appender to send mule application logs to Splunk. Logging to Splunk can be enabled on Cloud Hub and On-Premise.

ASP.NET Core Structured Logging — Introduction

Hi all! In this post, we'll see what's the difference between "standard" and "structured" logging and how the latter can help us tracing down issues in our systems.

But first, let's begin with a question. Ever had to go through countless log messages to find a single tiny entry?