Logging configuration hard coded in code, should be in appsettings.json #10377

3 Answer(s)

• 

  0

  improwise created yesterday

  static async Task Main(string[] args)
  {
      Log.Logger = new LoggerConfiguration()
          .MinimumLevel.Information()
          .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
          .MinimumLevel.Override("Volo.Abp", LogEventLevel.Warning)
  

  #if DEBUG .MinimumLevel.Override("Malerifakta.CustomerPortal", LogEventLevel.Debug) #else .MinimumLevel.Override("Malerifakta.CustomerPortal", LogEventLevel.Information) #endif .Enrich.FromLogContext() .WriteTo.Async(c => c.File("Logs/logs.txt")) .WriteTo.Async(c => c.Console()) .CreateLogger();

      await CreateHostBuilder(args).RunConsoleAsync();
  }
  

  Save Cancel
• 

  0

  AI-Bot created yesterday

  Support Team ABP Agent

  • In ABP startup templates, logging is typically configured in Program.cs on purpose because the host needs a logger before the DI container and modules are built, so startup/bootstrapping errors are captured reliably (including failures that happen while reading configuration, building the app, running migrations, initializing modules, etc.). ABP also ships templates with Serilog pre-wired and a few “baseline” enrichers/sinks so you immediately get useful logs during development without extra setup.
  • That said, ABP does not prevent configuring logging from appsettings*.json. You can (and in production usually should) move almost all Serilog configuration into configuration files and let different environments override it using appsettings.Development.json, appsettings.Production.json, environment variables, etc.

  Concrete approach (template-friendly):

  1. Put Serilog settings into appsettings.json (and overrides into appsettings.{Environment}.json).
  2. In Program.cs, keep only the minimal bootstrap code and load Serilog from configuration:

  using Serilog;
  
     var builder = WebApplication.CreateBuilder(args);
  
     builder.Host.UseSerilog((context, services, loggerConfiguration) =>
     {
         loggerConfiguration
             .ReadFrom.Configuration(context.Configuration)   // <-- appsettings.json
             .ReadFrom.Services(services);                   // <-- DI-based enrichers if any
     });
  
     await builder.AddApplicationAsync<MyHttpApiHostModule>();
     var app = builder.Build();
     await app.InitializeApplicationAsync();
     await app.RunAsync();
  

  3. Use environment-specific configuration normally:
     • appsettings.Development.json -> verbose logs
     • appsettings.Production.json -> warning/error + production sinks (Elastic/AppInsights/etc.)

  What about “hardcoded minimum level” / WASM scenarios?

  • In Blazor WebAssembly, configuration and logging are constrained by the client-side hosting model; the template may set a default minimum level in code to ensure sane defaults and avoid shipping overly-verbose client logs unintentionally. You can still drive this via configuration, but you must ensure your WASM config files are actually loaded/selected per environment (WASM uses wwwroot/appsettings*.json).

  Links you referenced

  • ABP support thread (reachable): https://abp.io/support/questions/1496/ABPIO-WASM---Log-level-configuration
  • GitHub issue link you provided is not reachable from my URL check right now, so I’m not including it as a verified source.

  (If you want the “official ABP template” exact file/method name where Serilog is configured—e.g., a shared helper in *.Shared.Hosting—tell me your ABP version/template type and I can point to the exact implementation.)

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  improwise created yesterday

  real answer please

  Save Cancel