Feature request: jhack etail

[taurus-forever]

Hi,

I am constantly using jhack tail to understand the deployment progress and monitor the internal charm activities.

Example:

I have to constantly open several tmux windows to monitor: 1) jhack tail # to see juju events 2) juju status --watch 1s 3) juju debug-log --tail # overall charm progress / stuck 4) juju debug-log --tail | grep ERROR # errors only to do not miss some in endless flying debug-log

It is a feature request to create high-level jhack etail to speed up initial setup. The etail could be an enhanced tail which will show the last errors and the last debug-log...

P.S. Is it a time for some nice-aligned default tmux config for juju? jhack tmux???

[PietroPasotti]

funny enough I'd considered this in the past but I encountered a couple of issues:

• tmux is hard to script: I'm using tmux-resurrect to autoload the layout, but I couldn't yet find a way to save/load what commands are running on each pane
• I found it hard to generalize, as everyone likes their terminals :)

[taurus-forever]

My tmux oneliner:

ubuntu@juju342:~$ cat ./new_model_tmux.sh 
#/bin/bash

juju add-model "test$(date +%s)" && tmux new-session '' \; \
  split-window -v \; \
  send-keys "echo 'Type your Juju commands here... '" C-m \; \
  split-window -h \; \
  send-keys 'juju status --watch 1s' C-m \; \
  split-window -v \; \
  send-keys 'juju model-config "logging-config=<root>=INFO;unit=DEBUG" ' C-m \; \
  send-keys 'juju debug-log --tail' C-m \; \
  split-window -v \; \
  send-keys 'juju debug-log --tail | grep ERROR' C-m \; \
  split-window -v \; \
  send-keys 'jhack tail' C-m \; \

tmux -2 attach-session -d

ubuntu@juju342:~$ ./new_model_tmux.sh 

As I am bored to type the same commands many times...

I agree, all pencils have different colors and flavors, but we have no recommendation/best-practices for newbies (which are comfortable to use AS IS).

[PietroPasotti]

I think a better place for this would be the charm-dev multipass blueprint