How about the timesamps of events generated by multiple processes across multiple hosts (possibly across multiple timezones)?
The timestamp is created when the logging event is created. That is so say, when the debug, info, warn, error or fatal method is invoked. Thus, the timestamp is unaffected by the time at which event arrive at a remote socket server. Timestamps are stored in UTC format inside the event. Consequently, when displayed or written to a log file, timestamps appear in the same timezone as the host displaying or creating the logfile. Note that because the clocks of various machines may not be synchronized, there may be timestamp inconsistencies between events generated on different hosts. The EnhancedPatternLayout in the extras companion supports explicit specification of the timezone using a pattern like “%d{HH:mm}{GMT}”.
Related Questions
- If I have many processes across multiple hosts (possibly across multiple timezones) logging to the same file using the method above, what happens to timestamps?
- What are the relationships of geologic, vegetative, and fluvial processes to natural events and land use history?
- Why not use a product like Eventbrite meant for Indian events and which processes Indian rupees?
