Logging full stdout in cli and gui

[borestad]

Hi. First - fantastic piece of software!

Question/Feature request?

When invoked via cli, I'd like to see the output of the steps. Succesful or failed. Can't seem to find anything. Now I have to run the dag via cli and then manually look in the log files. Is there something I've misesd?

Also, is it possible to add a full output to the gui? Now I have to click the respective step to see the output

My plan is to essentially replace github actions with dagu (but locally) 🍺

All the best
Johan

[yottahmd]

Hi @borestad, thank you for your kind words!

When invoked via CLI, I'd like to see the output of the steps

Do you mean you’d like all step logs to appear directly in stdout and stderr? That’s possible, though if multiple steps run in parallel, the output may become difficult to read. If you have any ideas or preferred approaches, I’d be happy to hear them.

Also, is it possible to add a full output to the GUI? Now I have to click each step to see the output

When you mention “output,” are you referring to stdout, or the captured stdout stored in a named output variable? An example would be very helpful.

My plan is to essentially replace GitHub Actions with Dagu (but locally) 🍺

That sounds very interesting! What motivated you to switch from GitHub Actions to a local Dagu setup?

[borestad]

Regarding the cli. I'd like to somehow at least be able to catch the logs visually. In the case of async/parallel logs, it would be totally fine to just wait until the entire run is finished. Just lacking some output here (stdout/stderr, maybe both)

The same essentially goes for the UI. I'd like to read a summary of all steps. Similar to how I'd look for the result/outcome if using i.e Github Action.
Regarding if it should capture whats in stdout. I think I'd like that PLUS a raw mode - similar to Github's raw output logs :-)

The reason for using Dagu conceptually as a local Github Action is due to certain companies/private projects I work for can't use external cloud services. And also the ability to easily spin up a single binary service locally when needed is great!
I see dagu as a one swiss army knife binary for tasks/crons - And with the portability of the yaml tasks files, it is a gold mine! 🍺

Sure there are other/multiple ways of running tasks locally, but most of them lack the ability to also run cron/scheduled tasks. And to have a cleaned standardise way of running DAG's is great for reusability.

The cli ux is also great for some of my non-techy collagues, and to also have a web ui is just sugar on top!

[yottahmd]

Thanks for the explanation! Everything you mentioned makes sense.

I have a few questions about "summary of all steps". I might be mistaken, but it seems that the GitHub Action results don’t include a summary of the logs. Could you clarify this a bit more?

Here’s an example GitHub Actions result for reference:

[borestad]

Ah...of course, I'll try to explain :-)

I think it might be ux related - but I can easily expand all jobs on the same page without loosing context.

What I actually want to achieve is to quickly get a high level understanding of what actually happened on the respective task that has been run. Similar to tailing a log. Just a lot of output without too much clicks. I rather scroll to find what I'm after 🙂

Compared to the dagu webui where I have to click on stdout/stderr. A popups opens, then click on close.

And then the ability to look at the raw logs if needed:

[ghansham]

@yottahmd github actions look more like subdags with steps.

[yottahmd]

Thanks for the clarification and for the great idea! It seems the Web UI part would be fairly straightforward, while the CLI might need a bit more thinking and research (e.g., handling a large log file, mixing stderr and stdout, etc). Let's start by improving the Web UI first.

[codinggeeks06]

hi @yottahmd,
in cli logs I guess we can do it using bubbletea TUI ig. What do you think?

[yottahmd]

Hi @codinggeeks06
Yes, I agree. We could use bubble tea to implement useful navigation between steps and logs (perhaps switch to less or something?) inside the CLI. Even if the experience isn’t exactly like GitHub Actions, it would be very useful.

[codinggeeks06]

ill try to implement this if possible. if possible please assign this to @kriyanshii .

[borestad]

Wow! You guys are great! ❤️