Platform Analytics 7 Dataflow

Hourly Core Utilization datamart

Main ETL XML file

hardwarewithcoreutilHourly-sp006.xml

Output CSV files

hardwareCoreUtilHourly-sp006.csv

Record sample

DATE,HOUR,WEEKDAY,COREHOUR,SHIFT,SERVER,VENDOR,FEATURE,USERNAME,HOSTNAME,DENIALS

"2005-11-07",14,2,1,"Shift 2","ib04b12","lsf_ld","myjob1","dazhang","ib04b12",1.0

"2005-11-07",22,2,0,"Shift 3","ib04b12","lsf_ld","myjob1","dazhang","ib04b12",1.0

Column description

The Hourly Core Utilizationl datamart gets its information from the WI_COREUTILHOURLY table.

The following table briefly describes each column and its source:
Column name
Source and description
DATE
This is the date portion of the localized time_stamp column in the WI_COREUTILHOURLY table, and the format is "YYYY-MM-DD".
HOUR
This is the hour portion of the localized time_stamp column in the WI_COREUTILHOURLY table.
WEEKDAY
This is the weekday number from the localized time_stamp column in the WI_COREUTILHOURLY table, where "1" is Sunday, "2" is Monday, etc.
COREHOUR
The source is the localized time_stamp in the WI_COREUTILHOURLY table. If the time_stamp is within the range of 9am to 5pm on Monday to Friday, this field returns 1, otherwise, it returns 0.
A value of 1 means that the data in this record is aggregated from the core_hour portion of the day (9am to 5pm, Monday to Friday).
SHIFT
This is based on the localized time_stamp in the WI_COREUTILHOURLY table. The shifts transformer maps the localized time_stamp based on shift mapping and returns the user-defined shift.
CLUSTERNAME

The cluster name comes from the lookup of the name in the wi_clustercode table with cluster_code which comes in the WI_COREUTILHOURLY table.
HOSTNAME
The source is host_name in the wi_hostcode table, which is based on host_code in the WI_COREUTILHOURLY table.
SAMPLINGCOUNT This is the sampling_counter column in the WI_COREUTILHOURLY table.
COREID This is the core's id. To identify the core.
CORE_UTIL

This is the sum utilization of the core during one hour.