In today’s API-driven world, observability is critical. While MuleSoft provides rich logging capabilities out of the box, organizations often need centralized log management to monitor performance, detect issues faster, and improve troubleshooting.

Dynatrace is a powerful observability platform that offers log ingestion, monitoring, and AI-powered anomaly detection. By integrating MuleSoft 4 logs with Dynatrace, we can achieve end-to-end visibility of APIs, integrations, and system flows.

This blog will walk through the steps to configure MuleSoft 4 logging with Log4j2 and send logs directly to Dynatrace Logs Ingest API.

2. Prerequisites

Before getting started, ensure you have:

• MuleSoft Runtime 4.x

• Dynatrace SaaS or Managed instance

• An API Token in Dynatrace with the scope: logs.ingest

• Basic knowledge of Log4j2 configuration

3. Why Integrate MuleSoft Logs with Dynatrace?

• ✅ Centralized logging and monitoring

• ✅ Real-time troubleshooting with Dynatrace dashboards

• ✅ AI-based anomaly detection on MuleSoft flows

• ✅ Unified observability across microservices, APIs, and Mule apps

• ✅ Faster root cause analysis by correlating logs, traces, and metrics

4. Creating a Dynatrace API Token

1. Log in to Dynatrace

2. Navigate to Apps > Access Token

3. Click on Generate Access Token

4. Name the Token, Slect the expiration date

5. Select the scope → ingest logs

5. Copy the generated token → You’ll need it in your Log4j2 config

Configuring Log4j2 in MuleSoft

MuleSoft uses Log4j2 as its logging framework. We can configure a custom HTTP Appender to send logs directly to Dynatrace.

Appender for Dyantrace

        <Http name="DynatraceAppender"
            url="https://qru64311.live.dynatrace.com/api/v2/logs/ingest"
            method="POST">
            <Property name="Authorization">Api-Token XXXXXXXXXXX</Property>
            <Property name="Content-Type">application/json</Property>
            <JsonLayout compact="true" eventEol="true" />
        </Http>

AsyncRoot:

<AppenderRef ref="DynatraceAppender" />

Example log4j2.xml:

<?xml version="1.0" encoding="utf-8"?>
<Configuration>

    <!--These are some of the loggers you can enable. There are several more 
        you can find in the documentation. Besides this log4j configuration, you 
        can also use Java VM environment variables to enable other logs like network 
        (-Djavax.net.debug=ssl or all) and Garbage Collector (-XX:+PrintGC). These 
        will be append to the console, so you will see them in the mule_ee.log file. -->

    <Appenders>
        <RollingFile name="file"
            fileName="${sys:mule.home}${sys:file.separator}logs${sys:file.separator}test.log"
            filePattern="${sys:mule.home}${sys:file.separator}logs${sys:file.separator}test-%i.log">
            <PatternLayout
                pattern="%-5p %d [%t] [processor: %X{processorPath}; event: %X{correlationId}] %c: %m%n" />
            <SizeBasedTriggeringPolicy size="10 MB" />
            <DefaultRolloverStrategy max="10" />
        </RollingFile>
        <Http name="DynatraceAppender"
            url="https://qru64311.live.dynatrace.com/api/v2/logs/ingest"
            method="POST">
            <Property name="Authorization">Api-Token XXXXXXXXXXX</Property>
            <Property name="Content-Type">application/json</Property>
            <JsonLayout compact="true" eventEol="true" />
        </Http>
    </Appenders>

    <Loggers>
        <!-- Http Logger shows wire traffic on DEBUG -->
        <!--AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" 
            level="DEBUG"/ -->
        <AsyncLogger name="org.mule.service.http" level="WARN" />
        <AsyncLogger name="org.mule.extension.http" level="WARN" />

        <!-- Mule logger -->
        <AsyncLogger
            name="org.mule.runtime.core.internal.processor.LoggerMessageProcessor"
            level="INFO" />

        <AsyncRoot level="INFO">
            <AppenderRef ref="file" />
            <AppenderRef ref="DynatraceAppender" />
        </AsyncRoot>


    </Loggers>

</Configuration>

Testing the Integration

1. Deploy a MuleSoft application

2. Generate logs by sending requests to your Mule APIs

3. Go to Dynatrace > Logs

1. Filter by source="mule" or check for your MuleSoft application name

2. You should see real-time logs flowing into Dynatrace.

Conclusion

By integrating MuleSoft 4 logs with Dynatrace, you gain real-time visibility, centralized observability, and AI-powered insights into your APIs and integration flows. This setup helps developers and operations teams proactively monitor, detect issues.

With this integration, MuleSoft logs become a powerful observability signal in Dynatrace, allowing you to correlate logs with metrics and traces for full-stack monitoring.

Prerequisites:

• Bitbucket

• Anypoint Platform (Exchange Contributor, Runtime Access)

Mule API Project Structure:

Before you Deploy Mule Application to Cloudhub 2.0

Update Pom xml file with Distribution Management

<distributionManagement>
  <repository>
    <id>exchange-connected-app-v3</id>
    <name>Exchange Private Repository</name>
    <url>https://maven.anypoint.mulesoft.com/api/v3/organizations/${project.groupId}/maven</url>
    <layout>default</layout>
  </repository>
</distributionManagement>

Update Pom Xml with repositories

<repositories>
        <repository>
            <id>exchange-connected-app-v3</id>
            <name>Anypoint Exchange</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/maven</url>
            <layout>default</layout>
        </repository>
        <repository>
            <id>mulesoft-releases</id>
            <name>MuleSoft Releases Repository</name>
            <url>https://repository.mulesoft.org/releases/</url>
            <layout>default</layout>
        </repository>
        <repository>
            <id>anypoint-exchange-v3</id>
            <name>Anypoint Exchange V3</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/maven</url>
            <layout>default</layout>
        </repository>
</repositories>

For groupId please refer How to know my Organization ID (Org ID) on the Anypoint Platform

To deploy a Mule application to CloudHub 2.0, the application must first be published to Anypoint Exchange and then deployed.

To publish the application to Anypoint Exchange, create a file named settings.xml within it.

<?xml version="1.0"?>
<settings>

  <pluginGroups>
    <pluginGroup>org.mule.tools</pluginGroup>
  </pluginGroups>

  <servers>
    <server>
        <username>~~~Client~~~</username>
        <password>${CLOUDHUB_CLIENT_ID}~?~${CLOUDHUB_CLIENT_SECRET}</password>
        <id>exchange-connected-app-v3</id>
      </server>
  </servers>

  <profiles>
    <profile>    
        <properties>
          <org.id>ffb8acd1-c3ef-428d-8f40-b6e01fa634c2</org.id>
        </properties>
        <repositories>
          <repository>
            <id>exchange-connected-app-v3</id>
            <name>Corporate Repository</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/organizations/${org.id}/maven</url>
          </repository>
          <repository>
            <id>exchange-connected-app-v2</id>
            <name>Corporate Repository</name>
            <url>https://maven.anypoint.mulesoft.com/api/v2/organizations/${org.id}/maven</url>
          </repository>
        </repositories>
        <id>exchange-repos</id>
      </profile>
  </profiles>

    <activeProfiles>
    <activeProfile>exchange-repos</activeProfile>
  </activeProfiles>

</settings>

This repository will serve as an example. The code for your Mule application should be stored here.

After your code is uploaded to Bitbucket, create a new YAML file containing the pipeline's actual code.

image: maven:3.8.4-openjdk-8

pipelines:
    branches:
      develop:
        - step:
            name: Git Security Scan
            caches:
                - maven
            script:
                - pipe: atlassian/git-secrets-scan:0.5.1  
        - step:
            name: Validate & Compile
            caches:
                - maven 
            script:          
                - mvn -B clean -DskipTests package
          step:
            name: Publish to Exchange
            caches:
                - maven 
            script:
                - mvn deploy -s settings.xml
        - step:
            name: Deploy to dev cloudhub
            deployment: Sandbox
            caches:
                - maven
            script:  
                - mvn deploy -s settings.xml -DmuleDeploy -Denvironment=Sandbox -DtargetName=Cloudhub-US-East-2 -DmuleVersion=4.6.2 -Dworkers=1 -DworkerType=MICRO -DCLOUDHUB_CLIENT_ID=$CLOUDHUB_CLIENT_ID -DCLOUDHUB_CLIENT_SECRET=$CLOUDHUB_CLIENT_SECRET -DappName=mule-cloudhub2-deploy14

Create Deployment enveironment:

create a environment in bitbucket Named as per the deployment environment added in the Deploy to dev cloudhub step.

Update Repository Variables:

For connected app credentials refer Connected App functionality

update connected app secrets in repository settings as below

In the above bibucket yaml is written to run manually, In Pipelines select branch and step to run the pipeline as below.

once the pipeline is triggered application will be published to Anypoint Exchange and deployed.

Application deployed to Cloudhub 2.0.

Prerequisites:

• Github

• Anypoint Platform (Exchange Contributor, Runtime Access)

Mule API Project Structure:

Before you Deploy Mule Application to Cloudhub 2.0

Update Pom xml file with Distribution Management

<distributionManagement>
  <repository>
    <id>exchange-connected-app-v3</id>
    <name>Exchange Private Repository</name>
    <url>https://maven.anypoint.mulesoft.com/api/v3/organizations/${project.groupId}/maven</url>
    <layout>default</layout>
  </repository>
</distributionManagement>

Update Pom Xml with repositories

<repositories>
        <repository>
            <id>exchange-connected-app-v3</id>
            <name>Anypoint Exchange</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/maven</url>
            <layout>default</layout>
        </repository>
        <repository>
            <id>mulesoft-releases</id>
            <name>MuleSoft Releases Repository</name>
            <url>https://repository.mulesoft.org/releases/</url>
            <layout>default</layout>
        </repository>
        <repository>
            <id>anypoint-exchange-v3</id>
            <name>Anypoint Exchange V3</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/maven</url>
            <layout>default</layout>
        </repository>
</repositories>

For groupId please refer How to know my Organization ID (Org ID) on the Anypoint Platform

For the deployment of Mule application to Cloudhub 2.0 , application has to be published to exchange and then the deployment.

To publish the application to Anypoint Exchange create folder .maven and make file settings.xml.

<?xml version="1.0"?>
<settings>

  <pluginGroups>
    <pluginGroup>org.mule.tools</pluginGroup>
  </pluginGroups>

  <servers>
    <server>
        <username>~~~Client~~~</username>
        <password>${CONNECTED_APP_CLIENT_ID}~?~${CONNECTED_APP_CLIENT_SECRET}</password>
        <id>exchange-connected-app-v3</id>
      </server>
  </servers>

  <profiles>
    <profile>    
        <properties>
          <org.id>${ORGANIZATION_ID}</org.id>
        </properties>
        <repositories>
          <repository>
            <id>exchange-connected-app-v3</id>
            <name>Corporate Repository</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/organizations/${org.id}/maven</url>
          </repository>
          <repository>
            <id>exchange-connected-app-v2</id>
            <name>Corporate Repository</name>
            <url>https://maven.anypoint.mulesoft.com/api/v2/organizations/${org.id}/maven</url>
          </repository>
        </repositories>
        <id>exchange-repos</id>
      </profile>
  </profiles>

    <activeProfiles>
    <activeProfile>exchange-repos</activeProfile>
  </activeProfiles>

</settings>

This repository will serve as an example. The code for your Mule application should be stored here.

When your code is uploaded to GitHub, create a new folder named .github. Inside this folder, create another folder named workflows. This is where the YAML file containing the pipeline's actual code should be created.

In the YAML script below, the Git reference points to the develop branch, and the pipeline starts running only in the develop branch. Similarly, you can create jobs for multiple environments for each branch.

# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the workflow will run
on:
  # Triggers the workflow on push or pull request events for all branches

 push:
  branches: ["develop","main"]
 pull_request:
  branches: ["develop","main"]


jobs:
 build:
  if: ${{ contains(github.ref, 'dev') ||contains(github.ref, 'release') }}
  runs-on: ubuntu-latest
  steps:
    - run: echo 'MULE CONNECTED APP USER--${{vars.MULE_CONNECT_APP_USER}}'
    - run: echo 'MULE CONNECTED APP PASSWORD--${{vars.MULE_CONNECT_APP_PWD}}'
    - run: echo 'Eventname-- ${{ github.event_name  }}'
    - run: echo 'event-- ${{ github.event  }}'
    - run: echo 'Ref-- ${{ github.ref  }}'
    - run: echo 'RefName-- ${{ github.refname  }}'
    - run: echo 'github head ref-- ${{   github.head_ref }}'
    - name: Checkout this repo
      uses: actions/checkout@v3
    - name: Cache dependencies
      uses: actions/cache@v3
      with:
        path: ~/.m2/repository
        key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
        restore-keys: |
          ${{ runner.os }}-maven-
    - name: Set up JDK 1.8
      uses: actions/setup-java@v3
      with:
        distribution: 'zulu'
        java-version: 8
    - name: Build with Maven
      env:
        USERNAME: ${{ secrets.CONNECTED_APP_CLIENT_ID }}
        PASSWORD: ${{ secrets.CONNECTED_APP_CLIENT_SECRET }}
        KEY: ${{ secrets.decryption_key }}    
      #run: mvn --settings .maven/settings.xml clean install -e -X --file pom.xml
      run: mvn -B  package --file pom.xml --settings .maven/settings.xml -DskipMunitTests

    - name: Stamp artifact file name with commit hash
      run: |
        artifactName1=$(ls target/*.jar | head -1)
        commitHash=$(git rev-parse --short "$GITHUB_SHA")
        artifactName2=$(ls target/*.jar | head -1 | sed "s/.jar/-$commitHash.jar/g")
        mv $artifactName1 $artifactName2
    - name: Upload artifact 
      uses: actions/upload-artifact@v3
      with:
          name: artifacts
          path: target/*.jar

 deploy_to_dev:
    environment:
      name: Dev
    if: ${{ contains(github.ref, 'dev') }}
    needs: build
    runs-on: ubuntu-latest
    steps:  
    - run: echo 'PROVIDER***--${{vars.DEPLOY_PROVIDER}}'
    - run: echo 'REPLICA COUNT***--${{vars.REPLICA_COUNT}}'

    - name: Checkout this repo
      uses: actions/checkout@v3
    - name: Cache dependencies
      uses: actions/cache@v3
      with:
        path: ~/.m2/repository
        key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
        restore-keys: |
          ${{ runner.os }}-maven-
    - uses: actions/download-artifact@v3
      with:
        name: artifacts
    - name: Deploy to dev
      env:
        CONNECTED_APP_CLIENT_ID: ${{ secrets.CONNECTED_APP_CLIENT_ID }}
        CONNECTED_APP_CLIENT_SECRET: ${{ secrets.CONNECTED_APP_CLIENT_SECRET }}
        KEY: ${{ secrets.decryption_key }}
      run: |
        mvn deploy --settings .maven/settings.xml  -DskipMunitTests -Dappname_env='dev' -Denvironment=Sandbox -DMULE_ENV=dev -DDEPLOY_TARGET=Cloudhub-US-East-2 -DMULE_PROVIDER=MC -DDEPLOY_MULE_VERSION=4.6.2  -DDEPLOY_VCORE=1 -DDEPLOY_FORWARD_SSL_SESSION=true -DDEPLOY_LAST_MILE_SECURITY=true -DCONNECTED_APP_CLIENT_ID="$CONNECTED_APP_CLIENT_ID" -DCONNECTED_APP_CLIENT_SECRET="$CONNECTED_APP_CLIENT_SECRET"

Update Connected App Secrets:

For connected app credentials refer Connected App functionality

update connected app secrets in repository settings as below

If you are following any branching strategy, raise a pull request to the develop branch. As per the above script, the Git reference is pointed to the develop branch, so the pipeline will get triggered accordingly.

• Docker

• SonarQube

• Anypoint Studio

Installation of Docker:

• Installation on Windows

• Installation on Mac

Installation of mule sonar plugin:

• mule-sonar Repository link

https://github.com/mulesoft-catalyst/mule-sonarqube-plugin#server

• On successful installation of docker run the below command to install mule sonar plugin

               docker pull fperezpa/mulesonarqube:7.7.3

• On successful installation of sonar run the following command to start the sonar.

docker run -d --name sonarqube -p 9000:9000 -p 9092:9092 fperezpa/mulesonarqube:7.7.3

• On Docker, screen sonar status can be seen

• On a Successful run and once the Sonar is Up.

• Call http://localhost:9000 on the browser.

• Pass credentials below

  username: admin

  Password: admin

  Static Code Check:

• Update the properties with

                <sonar.sources>src/</sonar.sources>

• Update profiles to connect with sonar.

        <profiles>
                <profile>
                    <id>sonar</id>
                    <activation>
                        <activeByDefault>true</activeByDefault>
                    </activation>
                    <properties>
                        <sonar.host.url>
                            http://localhost:9000
                        </sonar.host.url>
                    </properties>
                </profile>
        </profiles>

• Run the following command at project exists where pom.xml exists.

                mvn sonar:sonar

• On successful build at http://lolcahost:9000/projects, you can see the project got created with static code check.

• Splunk is a tool used for logging, analysing, reporting, visualising, monitoring or searching the machine data in real time.
• HEC offers an experience on Splunk Cloud deployments that Splunk manages that is similar to the experience on self-service Splunk Cloud. The following exceptions apply, you cannot make changes to configuration files, because Splunk Cloud does not provide that access.

Creating HTTP Event Collector Token: The HTTP Event Collector (HEC) lets you send data and application events to a Splunk deployment over the HTTP and Secure HTTP (HTTPS) protocols. HEC uses a token-based authentication model. For creating token, navigate to Settings → Data inputs → HTTP Event Collector

Once you click on New Token button, it will navigate to form, and start filling details like Name and click on Next at top of web page for filling further details.

On the next screen you can select SourceType as log4j as we will be using log4j as source for sending data to Splunk from MuleSoft application.

Now configure the index and make sure main index as Default. And then Click Next à Submit

Once you clicked on Submit button, it will create a token and that we will be using for authentication purpose.

Here in Anypoint studio configure Log4j Appender to send log data to Splunk instance.

Procedure: One can configure log4j2.xml file inside application configuration on src/main/resources and use specific Splunk appender. below are the configuration details for Splunk appender approach.

                            Splunk appender

            <SplunkHttp name="Splunk"
                 url="https://ped-p-fn3wj.splunkcloud.com:8088/"
                 token="460fedc3-702b-487d-afaa-7997ccdce793"
                 batch_size_count="1"
                 disableCertificateValidation="true">
                 <PatternLayout pattern="[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]:      %m%n" />
             </SplunkHttp>

The standard form for the URI in managed Splunk Cloud is as follows:

              <protocol>://http-inputs-<host>:<port>/<endpoint>

While using SplunkHttp, you need to add the following dependency in pom.xml of your application.

               <dependency>
                  <groupId>com.splunk.logging</groupId>
                  <artifactId>splunk-library-javalogging</artifactId>
                  <version>1.7.3</version>
               </dependency>
             < --------------------------------------------- >
                <repository>
                  <id>splunk-artifactory</id>
                  <name>Splunk Releases</name>
                  <url>http://splunk.jfrog.io/splunk/ext-releases-local</url>
                </repository>

You may need to add below two additional dependencies.

                 <dependency>
                    <groupId>org.apache.logging.log4j</groupId>
                    <artifactId>log4j-core</artifactId>
                    <version>2.10.0</version>
                 </dependency>
                 <dependency>
                     <groupId>org.apache.logging.log4j</groupId>
                     <artifactId>log4j-api</artifactId>
                     <version>2.10.0</version>
                 </dependency>

Note: We need to define loggers in log4j2.xml. make sure AppenderRef is match with name of SplunkHttp Appender.

   <AsyncRoot level=”INFO”> <AppenderRef ref=”Splunk”/></AsyncRoot>

Enable Custom Logging for CloudHub Application: 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.

<?xml version="1.0" encoding="UTF-8"?>
<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>

make sure AppenderRef is match with name of cloudhub Appender.

<AsyncRoot     level=”INFO”>   <AppenderRef ref=”cloudhub”    /></AsyncRoot>

Below is full log4j2.xml which can be used for your application for enabling custom logging

<?xml version="1.0"encoding="UTF-8"?>
<Configuration status="INFO" name="cloudhub"
 packages="com.mulesoft.ch.logging.appender,com.splunk.logging,org.apache.logging.log4j">
 <Appenders>
 <Log4J2CloudhubLogAppendername="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}">
 <PatternLayoutpattern="[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]:     %m%n" />
 </Log4J2CloudhubLogAppender>
 <SplunkHttpname="Splunk" 
 url="https://prd-p-fn3wj.splunkcloud.com:8088/"
 token="538feb69-9f16-4bd6-a0e1-ec7d0f71242b"
 batch_size_count="1"
 disableCertificateValidation="true">
 <PatternLayoutpattern="[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]:     %m%n" />
</SplunkHttp>
 </Appenders>
 <Loggers>
 <AsyncLogger
 name="org.mule.runtime.core.internal.processor.LoggerMessageProcessor"
 level="INFO" />
 <AsyncLoggername="com.mulesoft.agent" level="INFO" />
 <AsyncRootlevel="INFO">
  <AppenderRefref="Splunk" />
 <AppenderRef ref="CLOUDHUB"/>
 </AsyncRoot>
 <AsyncLoggername="com.gigaspaces" level="ERROR" />
 <AsyncLoggername="com.j_spaces" level="ERROR" />
 <AsyncLoggername="com.sun.jini" level="ERROR" />
 <AsyncLoggername="net.jini" level="ERROR" />
 <AsyncLoggername="org.apache" level="WARN" />
 <AsyncLoggername="org.apache.cxf" level="WARN" />
 <AsyncLoggername="org.springframework.beans.factory"
 level="WARN" />
 <AsyncLoggername="org.mule" level="INFO" />
 <AsyncLoggername="com.mulesoft" level="INFO" />
 <AsyncLoggername="org.jetel" level="WARN" />
 <AsyncLoggername="Tracking" level="WARN" />
 <AsyncLoggername="org.mule" level="INFO" />
 <AsyncLoggername="com.mulesoft" level="INFO" />
 <AsyncLoggername="org.mule.extensions.jms" level="INFO" />
 <AsyncLoggername="org.mule.service.http.impl.service.HttpMessageLogger"
 level="INFO" />
 <AsyncLoggername="org.mule.extension.salesforce" level="INFO" />
  <AsyncLogger name="org.mule.extension.ftp"level="INFO" />
 <AsyncLoggername="org.mule.extension.sftp" level="INFO" />
 <AsyncLoggername="com.mulesoft.extension.ftps" level="INFO" />
 <AsyncLoggername="org.mule.modules.sap" level="INFO" />
 <AsyncLoggername="com.mulesoft.extension.mq" level="INFO" />
 <AsyncLoggername="com.mulesoft.mq" level="INFO" />
 <AsyncLoggername="org.mule.extension.db" level="INFO" />
 <AsyncLoggername="httpclient.wire" level="DEBUG" />
 <AsyncLoggername="org.mule.transport.email" level="DEBUG" />
 </Loggers>
</Configuration>

JSON Logger: JSON Logger is a component for logging the information, warning, errors. It logs the data in the form of JSON. It is recommended to use JSON Logger for your application and it logs the data.

• Now deploy the API to cloud hub and you can see the logs in splunk cloud Now, you can verify the logs in Splunk, and it will be in JSON format.

Conclusion: Splunk is a very useful and powerful tool for logging, analysing, reporting, searching, and visualizing the events and data. MuleSoft provide capability to easily integrate Splunk using Anypoint Studio

Prerequisites:

• Installing Zuora connector (by login into Anypoint exchange from studio you can install the Salesforce connector)
• Zuora developer account
• Anypoint Studio

Process

• Create an Mule Applicatio
• If Zuora connecter is already present drag the Query Operation or else add the Zuora Module from Exchange
• Configure the connection details with Zuora API Credentials and use the Basic Username and Password connection (Username, Password).
• Get the details of the Zuora object and configure the listener to trigger the request

• Provide the Query string to retrieve the records as shown in the picture below
• Deploy / Run the application and trigger the endpoint using postman