使用log4net的ApplicationInsightsAppender遇问题，封装后日志不显示

Hey there, let's dig into why your wrapped log4net setup isn't sending logs to Application Insights. I've run into similar gotchas before, so here are the most likely culprits and fixes to try:

1. Log4net isn't being properly initialized in your wrapper #

When you use log4net directly, you might have set up initialization via an assembly attribute (like [assembly: log4net.Config.XmlConfigurator(Watch=true)] in AssemblyInfo.cs), but your wrapper class might not be triggering that setup correctly. If log4net doesn't load its configuration, the ApplicationInsightsAppender won't be registered at all.

Fix: Add explicit configuration loading in your Initialize method:

public static void Initialize(bool useAIApennder = false)
{
    // Load log4net config explicitly (point to your config file if needed)
    log4net.Config.XmlConfigurator.Configure(new FileInfo("log4net.config"));
    _logger = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);
    // ... rest of your logic
}

Also, double-check that your log4net.config file has its Copy to Output Directory property set to "Copy if newer" or "Always copy"—otherwise the wrapper won't find it at runtime.

2. You're using the wrong logger type #

Right now, your wrapper is creating a logger tied to the Logger class itself (via MethodBase.GetCurrentMethod().DeclaringType). If your ApplicationInsightsAppender has filtering rules (e.g., only logs from specific namespaces/classes), this generic wrapper type might be excluded from those rules.

Fix: Add methods to let callers pass in their own type, so logs are associated with the correct class:

public static class Logger
{
    private static ILog _defaultLogger;

    public static void Initialize(bool useAIApennder = false)
    {
        log4net.Config.XmlConfigurator.Configure();
        _defaultLogger = LogManager.GetLogger(typeof(Logger));
    }

    // Generic method for type-specific logging
    public static ILog GetLogger<T>()
    {
        return LogManager.GetLogger(typeof(T));
    }

    // Or accept a Type parameter directly
    public static ILog GetLogger(Type callerType)
    {
        return LogManager.GetLogger(callerType);
    }

    // Wrapped log methods (optional, for default logger)
    public static void Info(string message)
    {
        _defaultLogger?.Info(message);
    }
}

Then in your business code, use it like this:

// Logs will be tied to MyService, matching your AI appender's filters
var logger = Logger.GetLogger<MyService>();
logger.Info("This log should show up in Application Insights!");

3. Application Insights isn't initialized before logging #

If your wrapper initializes log4net before Application Insights sets up its telemetry configuration, the Appender won't have a valid instrumentation key to send logs.

Fix: Ensure AI is initialized first. For example, in an ASP.NET Core app:

• In Program.cs or Startup.cs, add AI telemetry before calling your logger's Initialize method:

// ASP.NET Core example
builder.Services.AddApplicationInsightsTelemetry();
// Now initialize your logger
Logger.Initialize(useAIApennder: true);

Double-check that your instrumentation key is correctly set in appsettings.json or via environment variables—typos here are a common silent failure.

4. Log level mismatches between wrapper and appender #

If your wrapper is only logging at Error level but your AI appender is configured to accept Info and above (or vice versa), logs will be filtered out before reaching Application Insights.

Fix: Verify your log4net config's level settings. For example:

<root>
    <!-- Make sure this level matches what your wrapper is using -->
    <level value="INFO" />
    <appender-ref ref="ApplicationInsightsAppender" />
</root>

Also confirm that your wrapper isn't swallowing lower-level logs (e.g., not calling _logger.Debug() when you expect debug logs to be sent).

5. Debug log4net's internal behavior #

If you're still stuck, enable log4net's internal debugging to see exactly what's happening under the hood. This will show you if the ApplicationInsightsAppender is being loaded, if logs are being filtered, or if there are permission/configuration errors.

Fix: Add this to your appsettings.json or web.config:

<appSettings>
    <add key="log4net.Internal.Debug" value="true" />
</appSettings>

Then check your application's debug output (Visual Studio Output window) for log4net's internal messages—this will often point you directly to the issue.

内容的提问来源于stack exchange，提问作者Matthew The Terrible