Timestamp on Dashboard Application Services Hub widgets

This section explains on how the timestamp are displayed on Dashboard Application Services Hub widgets according to the Resource and User time zone settings.

On Tivoli® Netcool® Performance Manager Wireline component, each resource group belongs to an aggregation set that corresponds to a time zone. This defines the hour at which daily aggregations are computed for resources or groups within the aggregation set. For more information on aggregation sets, see Configuring and Operating DataMart Guide.

Tivoli Netcool Performance Manager DataView Defined Resource Views displays the date or timestamp values as the resource group’s aggregation set time zone. A separate Calendar Table on the reports displays the offset between the aggregation set time zone and GMT.

The DataView's date or duration inputs that is selected by using Report Viewer toolbar are always considered as resource’s time zone. The dataset date input parameters are interpreted in a similar manner and considered as resource aggregation set’s time zone. However, the data displays between Dashboard Application Services Hub widgets and DataView reports are different when the resource and browser timezone settings are different.

Dashboard Application Services Hub widgets display timestamps in the browser’s local time zone. When the browser’s time zone is different from the resource’s time zone, which results in a shift in the timestamps that are displayed on Dashboard Application Services Hub widgets. The shift depends on the differences between user’s local browser time zone and the resource time zone.

The following scenarios describe the possible time zone differences that are displayed on the Dashboard Application Services Hub widgets:

Timezone Settings	Timestamp Display
Browser time zone and Resource time zone are same	No shift is observed in the timestamps that are displayed on Dashboard Application Services Hub widgets.
Browser time zone is ahead of resource time zone	In this case, `12:00 AM` on the start date for the resource’s time zone is a later time for the browser time zone on the same date. For example, if you are using a browser of a Malaysian time zone (GMT +8), and looking at a resource in a GMT time zone, the data display starts from `8:00 AM`, which is equivalent to `12:00 AM` of the same date for the resource.
Browser time zone is behind resource time zone	In this case, `12:00 AM` on the start date for the resource’s time zone is the previous date timestamp for the browser's time zone. For example, if you are using a GMT time zone to look for a resource in a Malaysian time zone (GMT +8), the data display starts from `4:00 PM` of the previous date. This is equivalent to `12:00 AM` for the next day’s date for the resource. The user can opt to select the next date as the date input since the date is interpreted for the resource time zone.

Timezone Settings

Timestamp Display

Browser time zone and Resource time zone are same

No shift is observed in the timestamps that are displayed on Dashboard Application Services Hub widgets.

Browser time zone is ahead of resource time zone

In this case, 12:00 AM on the start date for the resource’s time zone is a later time for the browser time zone on the same date.

For example, if you are using a browser of a Malaysian time zone (GMT +8), and looking at a resource in a GMT time zone, the data display starts from 8:00 AM, which is equivalent to 12:00 AM of the same date for the resource.

Browser time zone is behind resource time zone

In this case, 12:00 AM on the start date for the resource’s time zone is the previous date timestamp for the browser's time zone.

For example, if you are using a GMT time zone to look for a resource in a Malaysian time zone (GMT +8), the data display starts from 4:00 PM of the previous date. This is equivalent to 12:00 AM for the next day’s date for the resource. The user can opt to select the next date as the date input since the date is interpreted for the resource time zone.