Assigning timezone to the message
When AxoSyslog receives a message, it assigns timezone information to the message using the following algorithm.
The sender application or host specifies the timezone of the messages. If the incoming message includes a timezone it is associated with the message. Otherwise, the local timezone is assumed.
time-zone()parameter for the source driver that reads the message. This timezone will be associated with the messages only if no timezone is specified within the message itself. Each source defaults to the value of the
recv-time-zone()global option. It is not possible to override only the timezone information of the incoming message, but setting the
noallows AxoSyslog to replace the full timestamp (timezone included) with the time the message was received.
NoteWhen processing a message that does not contain timezone information, the AxoSyslog application will use the timezone and daylight-saving that was effective when the timestamp was generated. For example, the current time is
2011-03-11(March 11, 2011) in the
EU/Budapesttimezone. When daylight-saving is active (summertime), the offset is
+02:00. When daylight-saving is inactive (wintertime) the timezone offset is
+01:00. If the timestamp of an incoming message is
2011-01-01, the timezone associated with the message will be
+01:00, but the timestamp will be converted, because 2011-01-01 meant winter time when daylight saving is not active but the current timezone is
Specify the timezone in the destination driver using the
time-zone()parameter. Each destination driver might have an associated timezone value
: syslog-ngconverts message timestamps to this timezone before sending the message to its destination (file or network socket). Each destination defaults to the value of the
NoteA message can be sent to multiple destination zones. The AxoSyslog application converts the timezone information properly for every individual destination zone.
WarningIf AxoSyslog sends the message is to the destination using the legacy-syslog protocol (RFC3164) which does not support timezone information in its timestamps, the timezone information cannot be encapsulated into the sent timestamp, so AxoSyslog will convert the hour:min values based on the explicitly specified timezone.
If the timezone is not specified, local timezone is used.
When macro expansions are used in the destination filenames, the local timezone is used. (Also, if the timestamp of the received message does not contain the year of the message, AxoSyslog uses the local year.)
NoteYou can modify the timezone of the message using timezone-specific rewrite rules. For details, see Rewrite the timezone of a message.