Use Structured Logging

[michaelmairegger]

The messages in the logging screen are currently simple concatenated strings. As a result, they do not take advantage of structured logging. With parameterized log entries, logging tools like Seq can filter by properties and effectively use log templates.

Why it matters

Structured/parameterized logging solves several drawbacks of string concatenation and interpolation:

• Concatenated or interpolated logs become one big string, which can't be queried for individual fields like UserId.
• String formatting is done even if the log level is disabled.
• Parameterized logs keep data machine‑readable for indexing and searching

[robinrodricks]

You'll have to show samples of the level of detail you want. Take an example FluentFTP log output from your program, and show the structured version you expect. Then we can think on it and plan it.

[michaelmairegger]

@robinrodricks

As you can see in the screenshot, the last 3 lines comes from FluentFTP logging, and they are plain strings. The first 3 are logs that follow the structured logging style. Therefore I can filter for e.g. year > 2025. To follow strucuted logging the call to logging should NOT use concatenated string, but parameterized templates. e.g.

instead of
Log(FtpTraceLevel.Info, "Response: " + reply.Code + " " + maskedReply + " [" + duration.ToShortString() + "]");

use
_logger.Log(Level.Info, "Response: {ReplyCode} {Duration}", reply.Code, duration);

then i am able to filter for Duration > 1 sec

[robinrodricks]

Ok that seems doable.