#Do we have a way to control what we're
light marsh
There's a --progress=report you can use which will just tell the CLI to be quiet and print a final report of what happened:
Does that help? Or are you looking for more control? What kind of logs are you hoping to show - is it plain old fmt.Println? I'm actively working in the area right now so any details or mockups you can give for what you want to do / see could have a big impact!
vale oyster
We have 1000+ lines similar to these logs and actual log for the job is less than 200 line. I want to have more control over this. Not just printing result.
I guess, I'm looking for previous focus function like an aproach to tell dagger, which function executions needs to show in logs/ui which to hide
it could be similar to current trace span usage in dagger's it's own ci files
light marsh
Understood - did you try --progress=report? Or your point is that you need to see the logs live as they're printed, not just at the end?
Is your end goal that you simply want the logs of your function printed, and nothing else?
vale oyster
Understood - did you try `--progress=report`? Or your point is that you need to ...
Exactly, I want to simplify logs on live.
The devs using CI doesn’t always understand dagger logs. In those scenarios these logs create noise