I'm thinking through logging for my | Dagger | Page 1

cold geyser Aug 5, 2024, 9:05 PM

#

I am not 100% sure but looking at the docs it seems that the verbosity is based off of internal and encapsulated spans and things that took less than 100ms

So seems to be less of a "log level" thing and more around the relationship of the spans and how long they took to run.

https://docs.dagger.io/manuals/user/tui/

Dagger TUI | Dagger

The Dagger CLI includes a real-time visualization feature, also called the terminal UI (TUI). It shows a full-blown DAG in a style similar to git log --graph, with the current state of your DAG's evaluation and a full snapshot of all output at the end.

fluid creek Aug 5, 2024, 9:35 PM

#

Right, I'm technically more interested in figuring out what verbosity of the UI is set to and adjusting my functions verbosity to match.

#

This is mostly in the service of not needing to add yet another flag and maybe some consistency

cold geyser Aug 5, 2024, 9:38 PM

#

UI being Dagger Cloud or TUI?

fluid creek Aug 5, 2024, 10:14 PM

#

Sorry, TUI

cold geyser Aug 5, 2024, 10:55 PM

#

Yep got it, I am not 100% sure but I hope that @patent timber has the answer whenever he gets a chance 😄

patent timber Aug 6, 2024, 1:54 PM

#

@fluid creek There's no way at the moment, but I've thought about passing --debug to modules somehow (DEBUG=1?). Except --debug also implies -vvv which is maybe not what you want. Maybe we should just decouple those. You can already do -dvvv for the current behavior. We could also add a --log-level flag and pass it along, but that seems more complicated for module authors to deal with (what is the value? strings? numbers? how do numbers map? what if a level is unsupported? etc.). A single "debug mode" flag seems simpler for all intents and purposes.

I don't think we should pass along the verbosity level; it's solely tuned for the CLI, and it's hard enough to balance as it is, without having it permeate into modules.

#I'm thinking through logging for my