Serilog is logging type rather than object content

Question

I'm new to Serilog - trying it out to see if it will help. I'm using Serilog v2 and Serilog.Sinks.MsSqlServer v5

I have the following console app code:

static void Main(string[] args)
    {
        var logger = CreateLogger();

        var employee = new Person()
        {
            Name = "Rob",
            Age = 45
        };

        logger.Debug("Employee details {Employee}", employee);

        Console.ReadKey();

    }

private static ILogger CreateLogger()
    {

        string levelString = SSOSettingsFileManager.SSOSettingsFileReader.ReadString(
                            "LCC.Common", "Serilog.MinimumLevel");

        SerilogLevel level = (SerilogLevel)Enum.Parse(typeof(SerilogLevel), levelString);

        string conString = SSOSettingsFileManager.SSOSettingsFileReader.ReadString(
                            "LCC.Common", "Serilog.ConnectionString");

        var levelSwitch = new LoggingLevelSwitch();
        levelSwitch.MinimumLevel = (Serilog.Events.LogEventLevel)level;

        return new LoggerConfiguration()
            .MinimumLevel.ControlledBy(levelSwitch)
            .WriteTo.MSSqlServer(connectionString: conString, tableName: "Logs", autoCreateSqlTable: true)
            .CreateLogger();
    }

I would have expected the details of Person to be logged i.e. Name Rob and Age 45. However, I find the following logged to the Properties column on my Sql Server Sink:

<properties><property key='Employee'>ConsoleApplication1.Person</property></properties>

Where did I go wrong?

oleksa · Accepted Answer · 2017-10-05 13:45:57Z

33

here is Serilog documentation

For this task, Serilog provides the @ destructuring operator.

var sensorInput = new { Latitude = 25, Longitude = 134 };
Log.Information("Processing {@SensorInput}", sensorInput);

as you can see to do destructuring you have to set @ before key name. This is missed in your sample code

logger.Debug("Employee details {Employee}", employee);

answered Oct 5, 2017 at 13:45

oleksa

4,0761 gold badge37 silver badges59 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Mycah · Accepted Answer · 2022-08-06 00:18:23Z

0

@oleksa's answer worked for me and helped me realize what I needed to do in my case of trying to log some info from a controller using the Log.ForContext(...) approach. Here are a couple examples:

Option 1:

I prefer this approach since it keeps the view cleaner in the log aggregator (Seq in my case).

// Inside controller GET method

Employee employee = await myService.GetData();

// Need to set the `destructureObjects` flag to `true`
Log.ForContext<Employee>(Serilog.Events.LogEventLevel.Information, "Employee", employee, true)
   .Information("Employee Information");

Option 2:

// Inside controller GET method

Employee employee = await myService.GetData();

Log.Information("Employee Information {@Employee}", employee);

.NET 6 & Serilog 5.0

edited Aug 6, 2022 at 0:18

answered Aug 6, 2022 at 0:12

Mycah

5,0026 gold badges27 silver badges32 bronze badges

Comments

Kyle Burns · Accepted Answer · 2017-10-05 10:58:32Z

-4

The logging framework is going to call ToString on the object passed to it. If you want the details logged, one option would be to override the ToString method to serialize the object (assumes reference to Newtonsoft.JSON library):

// in Person.cs
public override string ToString()
{
    return JsonConvert.SerializeObject(this);
}

answered Oct 5, 2017 at 10:58

Kyle Burns

1,2449 silver badges17 bronze badges

1 Comment

Rob Bowman Over a year ago

I thought the idea of serilog was to avoid the need for such explicit serialisation - it is a structured logging framework

Collectives™ on Stack Overflow

Serilog is logging type rather than object content

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related