Can't figure out BeginScope? about serilog-extensions-logging

[nblumhardt]

Howdy! To add any output to the console you'll need to specify an outputTemplate argument to LiterateConsole():

    .WriteTo.LiterateConsole(outputTemplate:
        "{Timestamp:o} [{Level:u3}] {Scope} {Message}{NewLine}{Exception}")

The Scope property will show if there are text scope names like yours above; alternatively you can use {threadId} and so-on to show individual values.

Check out: https://nblumhardt.com/2016/11/ilogger-beginscope/

Thread ids are probably better added with: https://github.com/serilog/serilog-enrichers-thread

HTH!

[Capsup]

Thanks alot. I'm sorry it took me this long to respond, but yes, you're right, I did notice that outputTemplate but didn't consider that it had something to do with it. Thanks alot for your help.

[Porges]

Just ran into this myself. It's a little unexpected that the default behaviour doesn't include {Scope} anywhere. Would it make sense to include it?

[nblumhardt]

@Porges thanks for the feedback.

The Serilog.Extensions.Logging.File package does, because it assumes MEL is on the front-end, but other parts of Serilog are independent of MEL and so scope doesn't really make sense for them.

In the future, more packages like the aforementioned one might help simplify the experience, but we're still in the exploratory phase.

[Porges]

@nblumhardt That makes sense, thanks 👍