© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

How do caller information attributes fit into structured logging? - C#

C#•7mo ago•

15 replies

How do caller information attributes fit into structured logging?

It seems like the standard Microsoft

Ilogger

Ilogger

takes structured arguments with as

params object[]

params object[]

, making it hard to combine it with caller attributes such as

[CallerMemberName]

[CallerMemberName]

.
I know that caller information can be added for source-generated logging with

[LoggerMessage]

[LoggerMessage]

or

[LogProperties]

[LogProperties]

attributes on an ad-hoc basis, but I'm looking for an infrastructural solution.
How are you dealing with injecting caller information at scale in your code base?

I thought creating an interface

class ILogContext<T> {
    ILogger Ctx([CallerMemberName] string callerMemberName = "");
}

class ILogContext<T> {
    ILogger Ctx([CallerMemberName] string callerMemberName = "");
}

which is injected everywhere instead of a plain

ILogger

ILogger

and have the implementation be

class LogContext<T> {
    private readonly ILoggerFactory _factory;
    LogContext(ILoggerFactory factory){
       _factory = factory;
    }

    ILogger Ctx([CallerMemberName] string callerMemberName = ""){
        var logger =  _factory.CreateLogger<T>();
        logger.BeginScope("callerMemberName", callerMemberName);
        return logger;
    }
}

class LogContext<T> {
    private readonly ILoggerFactory _factory;
    LogContext(ILoggerFactory factory){
       _factory = factory;
    }

    ILogger Ctx([CallerMemberName] string callerMemberName = ""){
        var logger =  _factory.CreateLogger<T>();
        logger.BeginScope("callerMemberName", callerMemberName);
        return logger;
    }
}

but this approach seems subpar