Logging output tweaks | Dagger | Page 1

proven jungle Feb 3, 2023, 12:26 AM

#

I'm used to controlling my log output very directly with Mage (using pterm) so it's really clean and easy to diagnose stuff. I find that the buildkit style logs are decent from docker buildx as it helps collapse all the steps (though error logging can be tricky). I tried export DAGGER_LOG_FORMAT="plain" with auto, tty, and plain but it's not replicating the buildkit style output I get with docker, so not sure if that's currently possible.

Any notes or examples on this or is this a future thing, not adjustable right now?

fervent kite Feb 3, 2023, 12:28 AM

#

Currently not adjustable, but we plan to improve it. The tty output in 0.2 was actually better, so it's a regression of 0.3

proven jungle Feb 3, 2023, 1:38 AM

#

I can live with that 🙂 The noise reduction in my build logs by being so intentional with Go was a really nice plus of adopting mage.

I think the c.Pipeline("tacos") will be useful beyond the github action stuff I'm guessing as we'll get better control of how things are grouped and collapsed. Or at least I put it on the wishlist 😉

fervent kite Feb 3, 2023, 1:46 AM

#

btw you can disable log output in the client. You can also override by wrapping with dagger run

proven jungle Feb 3, 2023, 2:48 AM

#

Right now I'm using go and set to stdout by default. It's not the logging just the default buildkit verbose nature and no color/collapsing. 1st world problems 😁

proven jungle Feb 3, 2023, 7:44 PM

#

Rather than logging everything to stdout, is there any examples of trimmed down log output that only outputs the detail when an error happens and otherwise just lets me use my Go logging in between steps or such? Like 4-5 chained methods on the container, can I just output the step, without the streaming logoutut and buildkit progress output on the copying into container?

#Logging output tweaks