Last updated
This section covers receiving and viewing telemetry (statistics) from running Rumi applications.
Rumi automatically collects and reports statistics at multiple levels:
Container (Server) Statistics: Load average, memory usage, per-thread CPU utilization
AEP Engine Statistics: Message throughput, object pool usage, transaction statistics
Per-Transaction Statistics: Detailed performance metrics at the transaction level
By default, statistics reporting is conservative to minimize overhead. You can configure the level of detail based on your monitoring needs.
Container Heartbeats - Server-level statistics and health monitoring
Memory Statistics - Detailed memory usage statistics (heap, off-heap, IOBuffer, entity memory)
Engine Stats - Message processing and engine metrics reference
Per Transaction Stats - Transaction-level performance metrics
Exposing Application Stats - Define custom telemetry in your microservices
Configuring Monitoring - Configure statistics collection
Administration - Manage running applications
Analysis & Troubleshooting - Analyze collected telemetry
Last updated