Stack trace

[arins]

Shouldn't the stacktrace be outputed within a key?

stacktrace=some stacktrace

Serilog.Logfmt/Serilog.Logfmt/LogfmtFormatter.cs

Line 96 in e157ce6

output.Write(exception.StackTrace.Replace("\n", "").Replace("\r",""));

currently it is just printed out is that really valid logfmt? Grafana cloud skips it what I can see.

[wavedeck]

As of my comment, the logfmt serialization format does not have an official specification or RFC available to describe how the format has to be structured. So printing out stack traces without a key, regardless if on a single or multiple lines technically does not go against the logfmt structure.

I do not believe that Heroku (who is said to have brought this format to public attention) is coming up with an official specification any time soon, so this decision of format will be a community effort until logfmt gets more popular.

I also agree that stack traces should get their own key assigned, which in turn reduces complexity and improves compatibility with many log parsers. So in my opinion, adding keyed single line stack traces should be a configuration option in Serilog.Logfmt.

Something like adding .LogStackTrace(LogfmtStackTraceFormat.Keyed) could improve this library further while keeping backwards compatibility with already existing implementations and applications.

Should this be a considered PR?