# Monitoring applications and Mule runtimes

*MuleSoft Developer II Study Guide · Implement monitorable Mule applications · Last updated November 7, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer-ii/implement-monitorable-mule-applications/monitoring-applications-and-mule-runtimes*

Interpret resource dashboards and alert evidence using the correct metric scope, then select additional JVM and operating-system diagnostics for the actual investigation.

- Certification: Salesforce MuleSoft Developer II
- Exam section: Implement monitorable Mule applications
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer-ii

**Official exam objective:**

> Monitor Mule applications and Mule runtimes using Anypoint Platform or external tools.

## What the exam expects

- Monitor applications and runtimes with platform dashboards and external tools.
- Read memory and CPU quantities using their documented definitions.
- Distinguish a threshold result from absent data and collection offsets.
- Choose JVM or operating-system evidence for the suspected resource problem.

A **metric** measures a defined quantity over a scope; a **threshold** defines an alert condition; a **collection interval** describes sampling; **heap** stores Java objects; **non-heap** covers other JVM memory areas. This lesson combines Mule4.6 performance guidance with the corresponding platform metric definitions; current Insights labels help locate charts.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Dashboard access | Read Applications and Read Servers govern their corresponding resources. | [Runtime Manager dashboards](https://docs.mulesoft.com/runtime-manager/monitoring-dashboards) |
| Windows server CPU | This Runtime Manager metric is unavailable. | [Runtime Manager dashboards](https://docs.mulesoft.com/runtime-manager/monitoring-dashboards) |
| Classic worker history | Preserve statistics before restarts with `dashboardStats`. | [Runtime Manager dashboards](https://docs.mulesoft.com/runtime-manager/monitoring-dashboards) |
| Memory labels | Usage, Committed and Total have different meanings. | [Runtime Manager dashboards](https://docs.mulesoft.com/runtime-manager/monitoring-dashboards) |
| Runtime Fabric JVM CPU | Uses node capacity rather than the pod limit as its reference. | [Insights metrics](https://docs.mulesoft.com/monitoring/anypoint-insights) |
| Missing series | No data is not an evaluated OK result. | [Alert statuses](https://docs.mulesoft.com/monitoring/alerts-hf) |
| Disk await | Includes queueing and device service time. | [Performance monitoring](https://docs.mulesoft.com/mule-runtime/4.6/tuning-monitoring) |
| Heap dynamics | GC logs reveal allocation and object-growth activity. | [Performance monitoring](https://docs.mulesoft.com/mule-runtime/4.6/tuning-monitoring) |

## Check yourself

- Why is Metaspace distinct from an Old Gen object pool?
- When does an object belong in the dashboard's Survivor concept?
- What application scope does the JVM Class Loading view cover?

## Sources

- [Runtime Manager monitoring dashboards](https://docs.mulesoft.com/runtime-manager/monitoring-dashboards)
- [Configuring Anypoint Monitoring alerts](https://docs.mulesoft.com/monitoring/alerts-hf)
- [Anypoint Insights metrics](https://docs.mulesoft.com/monitoring/anypoint-insights)
- [Performance monitoring, Mule4.6](https://docs.mulesoft.com/mule-runtime/4.6/tuning-monitoring)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 10 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Developer II pack (USD $19): https://www.certifyforce.com/practice-exams