Level casing when length set to 5 and more

[JethroCZ]

A few questions before you begin:

Is this an issue related to the Serilog core project or one of the sinks or community projects. This issue list is intended for Serilog core issues. If this issue relates to a sink or related project, please log on the related repository. Please use Gitter chat and Stack Overflow for discussions and questons.

It is related to this sink (console).

Does this issue relate to a new feature or an existing bug?

• Bug
• New Feature

What version of Serilog Console Sink is affected by this issue? Please list the related NuGet package.
NuGet version 3.1.1.

What is the target framework and operating system affected by this issue? Please see target frameworks & net standard matrix.

• netCore 2.0
• netCore 1.0
• 4.7
• 4.6.x
• 4.5.x

Please describe the current behaviour you are experiencing?
When I set "Level" in "outputTemplate" argument to five letter or more, it doesnt format it to provided case. Setting "{Level:u5}" and "{Level:w5}" always format all levels in CamelCase: "Debug", "Infor", etc.

Please describe the expected behaviour if the ?
In case of "{Level:u5}" it should be all upper case and in case of "{Level:w5}" it should be all lower case.

If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem
In JSON configuration

"WriteTo": [
      {
        "Name": "Console",
        "Args": {
          "outputTemplate": "{Timestamp:yyyy-MM-dd HH:mm:ss,fff} [{ThreadId}] {Level:u5} [{ndc:u8}] usr:{LoggedUser:u10} {Message:lj}{NewLine}{Exception}"
        }
      }
]

NOTE: A small code sample goes a long way in expediting bug fixes or illustrating an enhancement you are proposing.

[nblumhardt]

Thanks for the note; this rings a bell - needs some investigation to see what the trade-offs are, but on the surface it looks like a simple bug fix is needed, here.

[pietrodicaprio]

Hello there, I'm sorry to resume such old issue but I'm currently facing it using Serilog.AspNetCore 6.1.0. Should it be already fixed or any possibility to have it fixed in next update(s)?

[nblumhardt]

@pietrodicaprio thanks for the nudge.

The Serilog.Sinks.Console level output format only covers up to four characters:

https://github.com/serilog/serilog-sinks-console/blob/dev/src/Serilog.Sinks.Console/Sinks/SystemConsole/Output/LevelOutputFormat.cs

While the Serilog default one covers any length:

https://github.com/serilog/serilog/blob/dev/src/Serilog/Formatting/Display/LevelOutputFormat.cs

I'm not sure if it's as simple as copying a few lines of code across (Console does some things slightly differently in order to support theming) but it does look like a relatively straightforward one to tackle. I'll have a look now.

[nblumhardt]

Ah I see @sungam3r has beaten me to it :-)