.Net Core and Serilog. Error from client. Strange formatting of Error

[Almenit]

Fatal exception from client gets strange formatting using Serielog and .Net Core.

Request payload from client:
{"lg":[{"l":6000,"m":"{\"stack\":\"Error: Server internal error\\n at XMLHttpRequest.req.onreadystatechange (webpack-internal:///./C/Content/Scripts/data/AjaxCaller.ts:58:24)\",\"message\":\"Server internal error\",\"name\":\"Error\",\"logData\":\"Server internal error\"}","n":"Reflect Client","t":1525702860451,"u":1}]}

Log in console:

[mperdeck]

Sorry for the late reply. I vaguely remember fixing this a while ago in a previous version of JSNLog.

Which version of JSNLog do you use? If it is not the latest, please upgrade to the latest version.
Do you use .Net Core or .Net Framework (the version of .Net before Core)?
If the problem persists, please publish a small test project on Github that allows me to reproduce the problem.

[ckosti]

I have the same issue. I'm using .NET Core 2.1 with Serilog.AspNetCore version 2.1.1 and JSNLog version 2.29.0 on the server and the client.

I put an example project together at https://github.com/ckosti/jsnlog-serilog-test

[ckarcz]

bump. still getting this as of 2021!!! using .net core/standard.

[ckarcz]

by the way, i've narrowed this down to only happening with

"ServerSideMessageFormat": "%message"

but when I do

"ServerSideMessageFormat": "[Browser] %message"

the object is log as expected:

[22:03:43.486 FTL]: [Browser] {"e":{"headers":{"normalizedNames":{},"lazyUpdate":null},"status":401,"statusText":"OK","url":"https://e550c3e88f89.ngrok.io/api/auth/session/1cd5a4f6-253a-4737-b1da-745e34eabb25/app-token/refresh","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://e550c3e88f89.ngrok.io/api/auth/session/1cd5a4f6-253a-4737-b1da-745e34eabb25/app-token/refresh: 401 OK","error":null},"message":"Http failure response for https://e550c3e88f89.ngrok.io/api/auth/session/1cd5a4f6-253a-4737-b1da-745e34eabb25/app-token/refresh: 401 OK","name":"HttpErrorResponse","logData":"An unhandled error has occured."}

hope this helps in fixing this! thanks.

[dgoldm]

but when I do

"ServerSideMessageFormat": "[Browser] %message"

the object is log as expected:

Thanks for the workaround. I do hope that the issue gets fixed ASAP