Since landing T113085: Support event logging propagation from target to deployment host and T113779: Limit structured logging output for now we've lost output from the deploy targets.
@thcipriani and I came up with a decent idea for logging in today's meeting that should be simple enough to implement by mid next week and seems modular (bingo!) enough to plugin to a more sophisticated iscap/tmux once that lands.
- Main deploy process initializes a new log file (under scap/log/ perhaps?) for the current revision and sets up the default log handler to write all deploy-local events to it.
- Implement a deploy-log command that can tail/parse the structured log (ala varnishlog) in a separate terminal. We should try to keep this component's implementation general (outside of the cli.Application subclass) so it can later be utilized by an iscap/tmux wrapper.