> For the complete documentation index, see [llms.txt](https://docs.rumi.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rumi.systems/rumi-core/guides/developing-applications/configuring-the-runtime/monitoring.md).

# Monitoring

Configure statistics collection and heartbeat emission for monitoring your Rumi microservices.

## Overview

Rumi automatically collects extensive statistics about message processing, transactions, and system resources. Configuration controls what statistics are collected, how frequently they're emitted, and the performance trade-offs.

Statistics must be balanced against performance impact. Many are enabled by default with minimal overhead, while detailed latency and per-transaction statistics can impact performance and require explicit enablement.

## Topics

* [**Container Heartbeats**](/rumi-core/guides/developing-applications/configuring-the-runtime/monitoring/xvm-heartbeats.md) - Configure periodic container-level statistics emission
* [**Engine Statistics**](/rumi-core/guides/developing-applications/configuring-the-runtime/monitoring/engine-statistics.md) - Configure AEP engine metrics collection
* [**Memory Statistics**](/rumi-core/guides/developing-applications/configuring-the-runtime/monitoring/memory-statistics.md) - Configure memory statistics collection
* [**Per-Transaction Statistics**](/rumi-core/guides/developing-applications/configuring-the-runtime/monitoring/per-transaction-statistics.md) - Configure detailed transaction-level metrics (experimental)

## Related Topics

* [Operating Model](/rumi-core/concepts/operating-model.md) - Monitoring architecture
* [Monitoring](/rumi-core/guides/operating-applications/monitoring.md) - Viewing and interpreting statistics at runtime
* [Exposing Application Stats](/rumi-core/guides/developing-applications/authoring-user-code/monitoring/exposing-application-statistics.md) - Define custom application metrics