The field FTimestamp using the DateToISO8601 function is set to UTC timezone. In certain circumstances this leads to log entries in the future. For example a Graylog input and the server are set to UTC, as recommended by Graylog. The local time of the source (our application) runs on UTC+02:00 we end up logging 2 hours in the future. I think a public property like "UseLocalTimezone" or something might be a solution. The Field FTimestamp is strict private so I don't know a clean solution for an inherited class without patching the original file TLoggerProUDPSyslogAppender.pas, what I actually do in the moment.
Will there be a chance to change this in future releases?
The field FTimestamp using the DateToISO8601 function is set to UTC timezone. In certain circumstances this leads to log entries in the future. For example a Graylog input and the server are set to UTC, as recommended by Graylog. The local time of the source (our application) runs on UTC+02:00 we end up logging 2 hours in the future. I think a public property like "UseLocalTimezone" or something might be a solution. The Field FTimestamp is strict private so I don't know a clean solution for an inherited class without patching the original file TLoggerProUDPSyslogAppender.pas, what I actually do in the moment. Will there be a chance to change this in future releases?