capprofile(4)

DESCRIPTION

Defines the file format used when importing and exporting data for Capacity Advisor.

The data for the specified profile is imported and exported as a series of lines containing the following:

The collection period is 5 minutes. Each data line is called a sample.

The first eight lines of the import file are format headers that define the profile characteristics. This information is used to normalize the utilization data when it is saved in the Capacity Advisor database. The information includes a profile name, hostname, CPU count and speed, memory size, OS platform or type, model information, and product version number. These are followed by date and metric labels.

The format header is:

#Profile: name

#Host: hostname

#CPU: CPU_count@CPU_speedGHz

#Memory: MEM_sizeMB

#OS: platform

#Model: model

#Version: version_number

[YYYYMMDDhhmm,] UTIS, metric [, metric, ...]

The fields of the profile header format are the following:

name: Name of the profile.

hostname: Fully-qualified name of the system. For example, node05.company.com.

CPU_count: Number of CPUs for which data is gathered in the file. For example, 1 means data was gathered for 1 CPU. Only integer values are valid. Note that CPU_count includes iCAP processors that are not enabled. This reflects the number of cores when dual-core processors are in use, and the number of hardware threads when hyperthreaded processors are in use.

CPU_speed: Speed in GHz (gigahertz); all CPUs have the same speed.

MEM_size: Memory size in MB (megabytes).

platform: Name of operating system, HP-UX or Linux.

model: The string representing the model of hostname as output by the model command.

version_number: Capacity Advisor version number.

metric: One of the following: CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL, NET_UTIL, PHYS_CPUS, PHYS_MEM.

The last header line contains the comma-separated list of labels for the date and gathered metrics, with or without spaces, where the fields are defined as:

YYYYMMDDhhmm: Timestamp in local time, given in units of YYYY (year), MM (month, as 01 to 12), DD (day, as 01 to 31), hh (hours, as 00 to 23), and mm (minutes, as 00 to 59). This format is also used to specify the begin and end times for the capprofile(1m) command. This field is optional when importing data.

UTIS: Universal Time (GMT) in seconds (standard UNIX time in seconds since 1 January 1970).

CPU_ALLOC: Number of CPUs allocated (active CPUs only; cores or hardware threads on multicore or hyperthreaded processors).

CPU_UTIL: CPU utilization expressed as the number of CPUs used (5 minute average).

DISK_UTIL: Disk bandwidth utilization in MB/s (10^6 bytes, megabytes per second) (5 minute average).

MEM_ALLOC: Memory allocation in GB (gigabytes).

MEM_UTIL: Memory utilization or amount of memory used in gigabytes (at end of interval reading).

NET_UTIL: Network bandwidth utilization, in Mb/s (10^6 bits, megabits per second) (5 minute average).

PHYS_CPUS: Number of physical CPUs (at end of interval reading).

PHYS_MEM: Physical memory available, in GB (gigabytes).

The last line of the import file header must include at least one metric column label and may have any combination of the eight existing metric column labels, in any order. It must have the UTIS timestamp column label in position 1 or, if the YYYYMMDDhhmm column label is present, in position 2. A metric label can appear only once in the header. UTIS timestamps must increment in a consistent order for each row; YYYYMMDDhhmm values are provided for readability.

To import a subset of metrics, specify only those metrics in the header. For example, to import only the CPU_UTIL metric, the last header line should contain “YYYYMMDDhhmm, UTIS, CPU_UTIL” or “ UTIS, CPU_UTIL.”

Each subsequent line after the header contains utilization values for a specified moment in time. Each data line, called a sample, has a timestamp followed by the values as designated in the header. Utilization values for a sample are separated by a specified delimiter character or by a comma (default). The UTIL seconds must be in 5-minute intervals (increments of 300 seconds).

For example, a file could contain the following profile format headers followed by the date and the labels for each metric:

#Profile: node05

#Host: node05.company.com

#CPU: 4@1.3GHz

#Memory: 4084MB

#OS: HPUX

#Model: ia64 hp server rx5670

#Version:A.02.50.00

YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL, NET_UTIL, PHYS_CPUS, PHYS_MEM

EXAMPLES

The following example shows utilization data in compressed format created using the following command:

#Profile: node05 #Host: node05.company.com #CPU: 1 @ 1 GHz #Memory: 2024MB #OS: HPUX #Model: ia64 hp server rx5670 #Version:A.02.50.00 YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL, NET_UTIL, PHYS_CPUS, PHYS_MEM

200509120000,11264184,0.02443,2.139648,0.003,0.0117,4.0,3.98,4.0,3.9 200509120005,11264187,0.02283,2.150390,0.005,0.0146,4.0,3.98,4.0,3.9 200509120010,11264190,0.05073,2.142578,0.009,0.0234,4.0,3.98,4.0,3.9 200509120015,11264193,0.04072,2.139648,0.006,0.0185,4.0,3.98,4.0,3.9 200509120020,11264196,0.01854,2.145507,0.003,0.0205,4.0,3.98,4.0,3.9 200509120025,11264199,0.03128,2.139648,0.005,0.0146,4.0,3.98,4.0,3.9 200509120030,11264202,0.02075,2.154296,0.003,0.0117,4.0,3.98,4.0,3.9 200509120035,11264205,0.02101,2.155273,0.004,0.0166,4.0,3.98,4.0,3.9 200509120040,11264208,0.01960,2.139648,0.004,0.0195,4.0,3.98,4.0,3.9 200509120045,11264211,0.02391,2.140625,0.003,0.0166,4.0,3.98,4.0,3.9 200509120050,11264214,0.02387,2.140625,0.003,0.0205,4.0,3.98,4.0,3.9

# Host: node05 HP-UX B.11.23 #CPU: 1 @ 1.0 GHz #Version:A.02.50.00 YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL, DISK_UTIL, MEM_ALLOC, MEM_UTIL, NET_UTIL, PHYS_CPUS, PHYS_MEM 200509120020, 11264196, 0.01, 2.14, 0.003, 0.02, 4.0, 3.98, 4.0, 3.98 200509120025, 11264199, 0.03, 2.13, 0.005, 0.01, 4.0, 3.98, 4.0, 3.98 200509120030, 11264202, 0.02, 2.15, 0.003, 0.01, 4.0, 3.98, 4.0, 3.98 200509120035, 11264205, 0.02, 2.15, 0.004, 0.01, 4.0, 3.98, 4.0, 3.98 200509120040, 11264208, 0.01, 2.13, 0.004, 0.01, 4.0, 3.98, 4.0, 3.98 200509120045, 11264211, 0.02, 2.14, 0.003, 0.01, 4.0, 3.98, 4.0, 3.98 200509120050, 11264214, 0.02, 2.14, 0.003, 0.02, 4.0, 3.98, 4.0, 3.98

YYYYMMDDhhmm, UTIS, CPU_ALLOC, CPU_UTIL 200605250020, 11264196, 0.01854, 2.14 200605250025, 11264199, 0.03128, 2.13 200605250030, 11264202, 0.02075, 2.15 200605250035, 11264205, 0.02101, 2.15 200605250040, 11264208, 0.01960, 2.13 200605250045, 11264211, 0.02391, 2.14 200605250050, 11264214, 0.02387, 2.14

SEE ALSO

capprofile(1M), capcollect(1M)