woodchipper
woodchipper copied to clipboard
An interactive command-line log processor
This adds a native Kubernetes client to replace the kubectl proxy subprocess. That is, a kubeconfig parser with some integration with reqwest to configure proxies and auth, or the rust...
Would be nice to include some optional filter flag to include context messages like `grep -C$N` to include messages before/after the match
If a single log message is larger than the viewport it causes problems: * page up/down get stuck on the message before the large one and the viewport won't move...
ANSI formatting characters in ingested messages can cause overflow and other formatting weirdness: 
This adds a new option for users to override the default refresh rate cap (previously 40hz). Users of slower terminals may see excessive flickering at this refresh rate, so now...
logrus seems to use a variant of rfc1123: `2014-03-10 19:57:38.562500591 -0400 EDT` these are all pretty common and should be supported
Mouse selections in the interactive viewer are cleared on redraw in some terminals. We should avoid this if possible. If we solve #41 by only redrawing dirty sections + shifting...
It would be nice to have some ability to view or at least copy actual raw output without having to drop to the json renderer. Needs to work in the...
Look into improving redraw performance. A few possible leads: * only redraw dirty components rather than the whole screen * is shifting supported + faster? e.g. move the whole term...
Woodchipper uses a hardcoded screen refresh delay that was assumed to leave plenty of time. Unfortunately some terminals (e.g. xterm) are really painfully slow and can't fully complete a redraw...