> 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-management/reference/monitor/dashboards.md). # Dashboards This page provides a reference for the canned Grafana dashboards shipped with Rumi Monitor. ## Dashboard Inventory | Dashboard | File | Description | | ----------------- | ----------------- | ------------------------------------------------ | | Home | `home.json` | Overview and navigation dashboard | | Container Stats | `xvm-stats.json` | Per-container health and performance metrics | | Application Stats | `app-stats.json` | Per-application messaging and processing metrics | | Host Stats | `host-stats.json` | Per-host resource utilization metrics | ## Template Variables All dashboards use template variables for dynamic filtering. Variables are populated from InfluxDB tag values. ### Container Stats Variables | Variable | Query | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | `system_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."application" WITH KEY = "system_name"` | | `vm_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."application" WITH KEY = "vm_name" WHERE "system_name" =~ /^$system_name$/` | | `app_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."application" WITH KEY = "app_name" WHERE "vm_name" =~ /^$vm_name$/ AND "system_name" =~ /^$system_name$/` | ### Application Stats Variables Same as Container Stats, plus: | Variable | Query | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | `bus_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."application.bus" WITH KEY = "bus_name" WHERE app_name =~ /^$app_name$/ AND "vm_name" =~ /^$vm_name$/` | ### Host Stats Variables | Variable | Query | | ------------- | --------------------------------------------------------------------------------------------------------------------- | | `host_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."application" WITH KEY = "host_name"` | | `system_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."application" WITH KEY = "system_name" WHERE "host_name" =~ /^$host_name$/` | | `vm_name` | `SHOW TAG VALUES FROM "rumi_heartbeat_rp"."system" WITH KEY = "vm_name" WHERE host_name =~ /^$host_name$/` | ## Container Stats Dashboard ### Panels | Panel | Measurements | Key Fields | | ------------------ | ----------------------- | ------------------------------------------- | | Apps Summary | `application` | App state, role, HA policy, loaded time | | Process CPU Load | `application` | `process_cpu_load` | | Host CPU Load | `application` | `system_cpu_load` | | Threads | `application` | `threads_count`, `processors` | | Heap Memory | `application` | `memory_heap_used` | | Non-Heap Memory | `application` | `memory_non_heap_used` | | Host Memory | `application` | `memory_physical_size` | | Garbage Collection | `system.gc` | GC counts and durations by `collector_name` | | JIT Compiler | `application` | JIT compilation time by `jit_name` | | Heartbeat Logger | `xvm.heartbeats.logger` | Logging stats | | Admin Client | `client.admin` | Admin connection stats | | Trace Log | `trace` | Trace entries | ## Application Stats Dashboard ### Panels | Panel | Measurements | Key Fields | | ---------------------------- | ------------------------------------- | ------------------------------------------------------- | | Store Operations | `application.store` | `hit_rate`, `miss_rate`, `eviction_rate`, `num_entries` | | Message Throughput | `application.messages` | Inbound/outbound counts | | Per-Type Messages | `application.messages.type` | Counts per message type | | Per-Type Latencies | `application.messages.type.latencies` | Latency stats per message type | | Disruptor Stats | `application.disruptor` | Ring buffer utilization | | Disruptor Latencies | `application.disruptor.latencies` | Processing latencies | | Transaction Stats | `application.transaction` | Transaction counts | | Transaction Latencies | `application.transaction.latencies` | Latency percentiles | | Store Commit Latencies | `app.store.c.latencies` | Store commit latency stats | | Message Processing Latencies | `app.mpproc.latencies` | Processing latency stats | | Custom Gauges | `application.user.gauge` | User-defined gauges | | Custom Counters | `application.user.counter` | User-defined counters | | Bus Statistics | `application.bus` | Per-bus messaging metrics | ## Host Stats Dashboard ### Panels | Panel | Measurements | Key Fields | | ------------- | ---------------- | --------------------------- | | Disk Usage | `system.disk` | Disk space and I/O | | CPU Usage | `system` | System CPU load | | Memory Usage | `system` | Memory utilization | | Thread Counts | `system.threads` | Per-container thread counts | | Trace Log | `trace` | Host-level trace entries | ## Data Source All dashboards expect an InfluxDB data source configured with: * The database where the Rumi Agent writes heartbeat data. * The `rumi_heartbeat_rp` retention policy. See the [InfluxDB Measurements Reference](/rumi-management/reference/agent/influxdb-measurements.md) for the complete measurement schema. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.rumi.systems/rumi-management/reference/monitor/dashboards.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.