Skip to content

Runtime

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"]
    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 four 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.

Pages in this group

  • Host

    SystemMetricsSnapshot + SystemMetricsTimeSeries (parallel pipeline). JVM heap / GC / threads / classes, OS CPU / load / uptime, disk, file descriptors.

  • Web Application

    MeterRegistry HTTP + Tomcat + Logback + Spring AI active gauges. HTTP traffic, Tomcat session state, logback level counts, in-flight LLM operations.

  • Logs

    Live tail of the application log with structured MDC extraction. Regex / level / follow-tail filters; click row → jump to trace.

  • Traces

    ObservabilityRingBuffer.liveStream() + snapshot(). Raw trace rows; click row → Trace Detail dialog with span timeline.

Cross-references

Was this page helpful? Ask on Discussions · Report a docs issue