Last updated
Configure statistics collection and heartbeat emission for monitoring your Rumi microservices.
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.
Container Heartbeats - Configure periodic container-level statistics emission
Engine Statistics - Configure AEP engine metrics collection
Memory Statistics - Configure memory statistics collection
Per-Transaction Statistics - Configure detailed transaction-level metrics (experimental)
Operating Model - Monitoring architecture
Monitoring - Viewing and interpreting statistics at runtime
Exposing Application Stats - Define custom application metrics
Last updated