Time Zone Handling in the eG Monitoring Console
By default, the eG manager time zone is displayed in the eG monitoring console. The same time zone applies to metrics collection and alarm generation also. When creating a user profile using the eG admin interface, an administrator can associate a different time zone with the user. When this user logs in, then the time zone assigned to his/her profile automatically applies to all time displays and time-related computations in the eG monitoring console.
Users to the console may sometimes notice discrepancies in how time zones are handled by the console. These caveats have been discussed hereunder:
- Assume that the eG manager’s time zone and the current user’s time zone are different. If DST (Daylight Savings Time) sets in for the user time zone and the clock is reset to one hour ahead or behind, the user will notice the wrong time being displayed in the console for the next hour. For example, if the user time is actually 2 pm but gets reset to 1 pm owing to DST, the console will show the wrong start time and end time, particularly in graphs, for 1 hour, until the user time under DST becomes 2 pm.
- If DST sets in for the eG manager’s time zone, the eG management console will not show the time correctly. The console time may be 1 hour ahead or behind (depending upon whether the clock was reset forward or backward) the actual time in DST. This issue however is resolvable. You can opt for one of the following workarounds:
- Change the JDK of the eG manager to v18.104.22.168 or higher, (OR)
Use the tzupdater tool to update the installed JDK and JRE images with the most recent time zone data to accommodate the US, Asia, Europe, and other locations’ DST changes. For this, download the tzupdater.jar from the web to any location on the eG manager host. Open the command prompt, go to the copied folder, set the Java path, and run the following command:
java -jar tzupdater.jar –u
- Finally, restart the manager to get the correct timeline.