title: Runtime description: Five dashboards covering JVM/OS health, Ollama runtime monitoring, HTTP and Tomcat instrumentation, live log tail with MDC-extracted trace correlation, and the raw trace stream.
The Runtime group is the operational view - JVM and OS health, HTTP and session instrumentation, log search, and the raw trace stream. Where AI Usage and AI Stack answer “what did the agent do,” Runtime answers “is the process itself healthy” and “give me the unfiltered evidence.”
flowchart LR
MR["MeterRegistry"]
SMC["SystemMetrics<br/>Collector"]
SMR["SystemMetrics<br/>RingBuffer"]
SMT["SystemMetrics<br/>TimeSeries"]
MR --> SMC --> SMR --> SMT
SMT --> HO["Host"]
OllamaApi["Ollama<br/>/api/ps · /api/tags"] --> OL["Ollama"]
MR -. live read .-> WA["Web Application"]
LogStream["Rolling<br/>app log"] --> LG["Logs"]
Coll["Observability<br/>Collector"] --> Buf["Observability<br/>RingBuffer"]
Buf --> TR["Traces"]
TR -. row click .-> TD["Trace Detail"]
LG -. traceId match .-> TR
The five tabs are independent - Logs and Traces share an MDC traceId so an operator can drill from a log line to the trace it came from (and vice versa), but otherwise each tab pulls from its own source. The Host and Web Application tabs both read MeterRegistry, but Host historizes it through the dedicated SystemMetricsCollector parallel pipeline while Web Application reads live values directly. Ollama is separate again - it polls the local Ollama server’s own HTTP API.