[LOG4NET-380] LoggingEvents received from RemoteAppender are UTC, but TimeStamp.Kind is "Local" and not "Utc"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.2.11
• Component/s: Appenders
• Labels: remote timestamp timezone
• Environment: .NET 4 application on RaspberryPi (Arch Linux) with Mono 2.10.9, logging with RemoteAppender to an application on Windows 7, which uses a custom appender to add the received LoggingEvents to a collection.
• Assignee: Unassigned
• Reporter: Steve Ziuchkovski
• Created: 31/May/13 02:40
• Updated: 01/Jun/13 17:30
• Resolved: 31/May/13 18:23

Description

The timestamps from RemoteAppender are UTC, but the TimeStamp.Kind property is "Local".

Both the Windows and Linux machines have their system time set to local time.

The LoggingEvent TimeStamps that are received from the Windows machine (not going through RemoteAppender) contain local timestamps, and the LoggingEvent.TimeStamp.Kind is "Local".

The LoggingEvent TimeSTamps that are received from the Linux machine (going through RemoteAppender) contain UTC timestamps, but the TimeStamp.Kind is "Local", not "Utc".

If the Kind property was UTC, I could adjust the timestamps from both log event sources to match (both UTC/both Local). Unfortunately, I cannot tell the difference using just the TimeStamp field itself.