You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a set of tasks simultaneously, sometimes I only care about the logs of a specific task.
For instance, in Argo Workflows, if I'm working on the Server, the logs of the Controller are usually not relevant to me.
Right now you can only see all logs at once and only filter by debug/info/warn/error log levels.
Notably, I actually thought that's what the number input controlled when I first used Kit, because Workflows's make start UI=true runs exactly 4 processes.
When running a set of tasks simultaneously, sometimes I only care about the logs of a specific task.
For instance, in Argo Workflows, if I'm working on the Server, the logs of the Controller are usually not relevant to me.
Right now you can only see all logs at once and only filter by debug/info/warn/error log levels.
Notably, I actually thought that's what the number input controlled when I first used Kit, because Workflows's
make start UI=true
runs exactly 4 processes.Related to #54, a k9s-style terminal UI with
gocui
,tview
, or similar would make this UX fairly straightforwardThe text was updated successfully, but these errors were encountered: