In the Alarms view, new alarms that originate from servers in different times zones are converted to display a time stamp using the local time zone. For example, a new alarm arriving on a computer in New York displays a time stamp of 12 noon, but the same alarm displays as 9 a.m. in San Diego.
A timeskew is the difference between the current time on the server and client, regardless of their time zones. For example, the current time on the server is 8:05 a.m. while the current time on the client in the same time zone displays 8:07 a.m. By default, Operations Center automatically detects timeskews and adjusts the displayed time stamp to be the time of the client. The overall effect is to adjust new alarms so they display using the local current time of the client, adjusting for differences in time zones and absolute time differences between the server and client. The time skew occurs for both real-time and historical alarms displayed in the Operations Center console and dashboard.
In some situations, you might want to disable timeskewing. When you disable timeskewing, the time stamp is based on the time on the server, both for local time and time zone conversions.
By default, timeskewing in enabled.
To disable timeskewing:
From the console toolbar, select Format > Use Timeskew.
The check mark next to the option disappears.
After selecting this option, either to enable or disable timeskewing, restart the console in order to see changes in all places.