Incorrectly encoded logger output

[cezarypiatekGC]

Describe the bug

The Wiremock console logger does not encode newline characters in the output. This causes problems with the log shipping mechanisms.

Expected behaviour:

I am using the WireMock.Net docker image to test my services within the K8s cluster. Because the output is formatted incorrectly, the log shipping mechanism treats each line as a separate log entry, resulting in a huge amount of log entries that are completely corrupted.

Below is the output from the Rancher console. As you can see, each line of formatted json is treated as a separate log entry:

[StefH]

#1063

[StefH]

Hello @cezarypiatekGC,

To be backwards compatible, I've added a boolean param to the WireMockConsoleLogger.

And I've updated the testcontainers nuget to use this logger WireMockNoNewLinesConsoleLogger.

And I'll also update the docker project to use this logger by default.

[cezarypiatekGC]

Looks like the PR pipeline failed, please let me know when the new image is released.

[StefH]

Looks like the PR pipeline failed, please let me know when the new image is released.

Should be fixed now, you can try the latests preview version.

[StefH]

@cezarypiatekGC
Did you try the latest preview version?

[cezarypiatekGC]

What's the tag for preview?

[StefH]

1.5.47-ci-18350

[cezarypiatekGC]

Can't download it from docker hub. Is it publish via different channel?

[StefH]

Can't download it from docker hub. Is it publish via different channel?

Sorry. I understand now. I did only update the NuGet and the TestContainer NuGet.

If you can review the PR? And if the PR looks good, I'll merge to main and create new official Nuget and create new Docker.

[cezarypiatekGC]

Not sure if removing line-endings is a solution here. After shipping logs to store like ElasticSearch they will be unreadable. How do the professional loggers like NLog and SeriLog handle such case?