12.3 Handling Time Zones  Handling time zones can become very
complex in a distributed environment. For example, you might
have an event source in one time zone, the Collector Manager in
another, the back-end Sentinel server in another, and the client
viewing the data in yet another. When you add concerns such as
daylight saving time and the many event sources that don't
report what time zone they are set to (such as all syslog
sources), there are many possible problems that need to be
handled. Sentinel is flexible so that you can properly represent
the time when events actually occur, and compare those events to
other events from other sources in the same or different time
zones.  In general, there are three different scenarios for how
event sources report time stamps:  For the first scenario, you
can always calculate the absolute UTC time that an event
occurred (assuming that a time sync protocol is in use), so you
can easily compare the timing of that event to any other event
source in the world. However,