Customization of the timestamp format

[rdewaele]

Is your feature request related to a problem? Please describe.
The current timestamp format (e.g. [2022-05-17 00:08:36Z]) does not have sub-second timing information, which limits the diagnostic potential of the timestamp.

Describe the solution you'd like
If customization of the log format is currently possible, I missed it.
In this event, I would like to both apologize and suggest adding an example describing this use-case.

The following solutions have crossed my mind:

• The problem is my ignorance, in which case I refer to the statement above.
• A hard-coded format change seems adequate, but perhaps a missed opportunity.
• Customization of the timestamp format, either through code or configuration.
• Customization of the log format as a whole sounds like a nice bonus.

Describe alternatives you've considered
Adding timestamps to the log messages themselves is of course functional, but rather inelegant.
( Okay, I'll admit that this issue is hardly a blocker, but ... elegance! 😅 . )

Thank you for your consideration, and this very useful library.

[martincostello]

Thanks for your suggestion @rdewaele! I've opened a PR to implement this in #313.

Could you take a look and see if it would work as you'd envisioned? You'd be able to configure a different format for the timestamps like this:

xunit-logging/tests/Logging.XUnit.Tests/IntegrationTests.cs

Lines 177 to 183 in e8c828a

	var options = new XUnitLoggerOptions()
	{
	Filter = (_, level) => level >= LogLevel.Error,
	TimestampFormat = "yyyy-MM-dd HH:mm:ss.fff",
	};
	var logger = BootstrapFactory((builder) => builder.AddXUnit(mock.Object, () => options));

The default behaviour would be the same as it is in the existing versions, which is to use the "u" format string.

[rdewaele]

Thanks a lot for the incredibly quick implementation. I will be experimenting with it today.

Thanks!

[rdewaele]

This implementation covers all my (current ;-)) use-cases, so I am a happy camper. 👍

Thanks again. :-)

[martincostello]

Great thanks, I'll release this to NuGet later on today.