Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More

What Information to Collect for a MuleSoft Runtime Fabric (RTF) Support Case

Publish Date: Mar 14, 2026
Task

GOAL

When you are reporting a MuleSoft RTF (Runtime Fabric) related case, please follow the procedure to collect the logs. This will expedite the troubleshooting process.

Steps

For MuleSoft Runtime Fabric, please collect "Required Logs" per each "Issue Category"
 

IndexIssue CategoryNoteRequired Logs
A-1Application issues(1)All applications issues except for A-2Lite report (2) 
A-2Request routing issues via the Edge 1. Issues sending a request via the Edge
2. (Optional) Enable DEBUG level log
"curl -v" + Lite report (3)
A-3RTF components (Agent) upgradeUpgrade Runtime Fabric ComponentsLite report (2) 
B-1"gravity status" degradedRuntime Fabric Cluster UpgradesFull report 
C-1InstallationRuntime Fabric InstallationInstall Logs
D-1Errors of Anypoint consoleErrors from the Anypoint ConsoleHAR package + screenshots
E-1Maven deployment errorsErrors by executing "mvn deploy" command"mvn -X -e" deploy logs 
F-1Deploy via the API directly   API request and response
  1. Some complex application issues may need a heap dump or app package. You can get it following Take a Heap Dump of an Application in RTF

 

  1. Enable DEBUG level log in Inbound Traffic, referring to Configure Inbound Traffic Using Runtime Manager, and reproduce the issue to generate logs

Lite report

For MuleSoft RTF, the Lite report is mostly required. It's an archive containing only Kubernetes objects and logs. The lite report is part of the full report but much smaller, which makes it easy to upload to or download from a case. 

NOTE: For RTF clusters running in self-managed kubernetes environments, only a lite report is required. The rtfctl utility reads the kubeconfig file to interact with your cluster. Please see the following article for more information: How to Run Rtfctl and Kubectl on RTF Self-Managed Kubernetes (BYOK) From a Different Machine Than Original

To generate a lite report, it's recommended to use the rtfctl (version 0.2.95+) tool. Always download the latest version before executing. 

> sudo curl -L https://anypoint.mulesoft.com/runtimefabric/api/download/rtfctl/latest -o /tmp/rtfctl

> sudo chmod +x /tmp/rtfctl

If you have a proxy in your environment, download with the "-x" option. 

> sudo curl -x http://<Proxy IP or domain>:<port) -L https://anypoint.mulesoft.com/runtimefabric/api/download/rtfctl/latest -o /tmp/rtfctl

(for example)
> sudo curl -x http://172.19.0.23:3128 -L https://anypoint.mulesoft.com/runtimefabric/api/download/rtfctl/latest -o /tmp/rtfctl

> chmod +x /tmp/rtfctl

Then create the lite report

sudo /tmp/rtfctl update
sudo /tmp/rtfctl report -n rtf --app-namespaces all

RTF Appliance(EOL)

You can get it through Ops Center as described in Download Debug Info. This gives you a full report (report.tar.gz). Unzip it and only take the file named with <host-name>-k8s-logs.tar, which is equivalent to the lite report. 

Full Report

A full report collects diagnostics from all cluster nodes. Use the rtfctl to get it

sudo /opt/anypoint/runtimefabric/rtfctl appliance report

Or get it through Ops Center as described in Download Debug Info

Install Logs

The Runtime Fabric installation generates logs locally. Get the logs from the failed node. 

  1. Change the line 2 of "/opt/anypoint/runtimefabric/init.sh" from "set -eo pipefail" to "set -exo pipefail". Rerun the script "/opt/anypoint/runtimefabric/init.sh" on the node that failed in installation
  2. Get the logs on the node
  • /var/log/rtf-init.log
  • (Optional) /var/log/gravity-install.log
  • (Optional) /var/log/gravity-system.log

Alternative, you can follow Runtime Fabric Basic Troubleshooting to collect all the logs

Knowledge Article Number

001116887

 
Loading
Salesforce Help | Article