Live Logs
The Live Logs page is the primary evidence surface for execution.
Operators should not have to guess what a model or runtime did. This page keeps the log stream and the higher-level summary view in the same surface so you can move between evidence and interpretation without switching tools.
What Lives Here
Section titled “What Lives Here”- raw stream inspection
- filtered activity summaries
- workflow-scoped diagnostics
- role, actor, and operation filters
What It Is Good For
Section titled “What It Is Good For”Use this page when a workflow appears stalled, suspicious, or simply needs a concrete explanation. It is especially useful when the workflow board tells you that something changed, but not why it changed.
Why It Matters
Section titled “Why It Matters”Agirunner is designed so that the operator-facing story can be backed by actual execution output. The live logs page is one of the clearest examples of that principle.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Live Logs is the evidence layer for almost every other dashboard surface:
- Workflows tells you where activity is happening
- Workflow Detail adds workflow-specific context, artifacts, and operator actions
- Approvals And Needs Action becomes easier to trust when you can inspect the underlying execution trail
- Diagnostics groups logs together with live container evidence for deeper operational triage
This page answers the question the board cannot: what did the system actually do, in what order, and with which actor, tool, or failure?