Is it possible to disable dagger cli span logs?

[serene crest]

I have migrated to new dagger engine from 0.6.2 to 0.11.8 recently. But i see lot of logs due cli being generating addiitonal log.
We run our application using go cli and output logs to stdout. We have plan to move to dagger cli to run our application and use new logs but for now we just need same logs without dagger spna cli.
IIRC dagger cli now neing downloaded automatically and it calls go main function. can we somehow disable these new logs from engine?

[open atlas]

I think there's a dagger --silent flag, which disables all progress output, only the final result of the pipeline. Is that what you're looking for?

[serene crest]

actually, I am not using dagger cli directly, I checked the logs it is downloading the cli and creating a session, so looking for a way to pass from sdk side

[open atlas]

Ah I see. I believe there is an option to dagger.Connect

[serene crest]

could you please point me in docs how? my use case is to get same logs we are getting previously from app but no additional dagger span logs which are coming together, becasue i cannot find it

[open atlas]

which SDK are you using?

[serene crest]

0.11.8

[open atlas]

sorry I meant which language?

[serene crest]

go sdk

[open atlas]

dagger.Connect() accepts ClientOpt arguments https://pkg.go.dev/dagger.io/dagger#Connect

You can pass dagger.WithLogOutput(io.Discard) as one of those arguments https://pkg.go.dev/dagger.io/dagger#WithLogOutput

[serene crest]

yeah i checked that, we are using our own logger "dagger.Connect(ctx, dagger.WithLogOutput(logger)" this is brining all debug logs but now its including new span logs, not sure how these two can be saparated

[open atlas]

Ah, I see. Are you able to copy paste an example of the unwanted output you're getting?

[serene crest]

now i don't see, strange.... 😆 i will come again in case i see this