No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I'm using `config.Development.yml` to configure logging:
```Serilog:
  MinimumLevel:
    Override:
      Microsoft: Information
      Microsoft.Hosting.Lifetime: Warning
  WriteTo:
    - Name: Seq
      Args:
        serverUrl: <http://localhost:5341>```
But I can't control the dotnet automation api logging without a source context

This should be a matter of using `ILogger&lt;T&gt;` instead of `ILogger` where type `T` becomes the source context

```public sealed partial class DeployCommand : AsyncCommandBase&lt;DeployCommand.Settings&gt;
{
    public DeployCommand(IOptions&lt;Config&gt; options, ILogger&lt;DeployCommand&gt; logger, IServiceProvider serviceProvider) : base(options, logger)
    {
    }

    protected override async Task&lt;int&gt; OnExecuteAsync(CommandContext context, Settings settings)
    {
        Logger.LogInformation("Deploying resources...");
        using var totalTimeLogger = new ElapsedTimeLogger(Logger, "Deployed resources");
        ...
    }
}

public abstract class AsyncCommandBase&lt;TSettings&gt; : AsyncCommand&lt;TSettings&gt; where TSettings : CommandSettings
{
    protected AsyncCommandBase(IOptions&lt;Config&gt; options, ILogger logger)
    {
        Config = options.Value;
        Logger = logger;
    }

    protected Config Config { get; }
    protected ILogger Logger { get; }
}```

This makes sense to me. Open an issue? (PR?)

<https://github.com/pulumi/pulumi/issues/7093> (looking at PR too)

AFAIK this is not an automation API thing. The core lib uses serilog so that is what you are seeing.

Also it doesn’t use Microsoft.Extensions.Logging.ILogger. It uses a home rolled ILogger where the implementation is in Pulumi.Deployment.Logger which calls out to some static serilog methods.

Yeah I was just looking through the code and that's exactly right.
Using the global shared serilog logger is messy but I can hack it to use a static `Serilog.Log.ForContext&lt;Deployment&gt;()`. It gets ugly when `PULUMI_DOTNET_LOG_VERBOSE` is defined as this creates a new logger which wipes my sinks.

<https://github.com/pulumi/pulumi/pull/7095>

Normally configuration of logging levels would be done via host configuration.
I wire up everything in my generic host, so if pulumi interacted with that it wouldn't need to recreate the logger.

Meanwhile the quick fix in my PR will inject a source context of `Pulumi.Deployment` so I can control it with say:
```Serilog:
  MinimumLevel:
    Override:
      Pulumi.Deployment: Debug```

(In this case I'll actually silence it by default because it makes my logs unreadable)

See the logging from a deploy is 99% noise from `Pulumi.Deployment`