Repository navigation
feat(ui): show the log of an agent at a level - #177
Merged
Merged
Conversation
ingvarch
force-pushed
the
feat/agent-logs
branch
from
November 4, 2026 00:49
ed98651 to
841c42b
Compare
…es of its log file
…or a client or server
ingvarch
force-pushed
the
feat/agent-logs
branch
from
November 4, 2026 00:55
841c42b to
9b10edb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
urga shows what a Nomad agent logs, at a level, following new lines: the agent urga talks to with
:agentlogs(alias:monitor), and any client or server withctrl-lon its list or its screen. Debugging a cluster no longer needs a shell on the machine./,f,n,wandctrl-swork as on a task log.vsteps through the levels (info, debug, trace, error, warn) and opens the stream again at the new one; the title names the level.MonitorExport(Nomad 1.10.4), filtered to the level, then the live lines fromMonitor. An older cluster, an agent withoutlog_fileor a refused export gives no past and no error. A server named through the cluster is not asked for its past, because Nomad answers that export with a live monitor that never ends.ctrl-lon servers shows only when urga talks to a server agent: a client agent ignores the server it is asked about and would answer with its own log.agent:readsees the cluster's refusal.Left for later: file streams can still lose their error the same way (older than this branch, #176).
Closes #155
Checklist
make checkis greenfeat(ui): ...,fix(nomad): ...