HP Operations Agent - Performance Collection Component Dictionary of Operating System Performance Metrics Print Date November 2011 Performance Collection Component for Release 11.02 ************************************************************* Legal Notices ============= Warranty -------- The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend ------------------------ Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notices ----------------- ©Copyright 2011 Hewlett-Packard Development Company, L.P. All rights reserved. ***************************************************************** Introduction ============ This dictionary contains definitions of the operating system performance metrics for the Performance Collection Component. This document is divided into the following sections: * "Metric Names by Data Class," which lists the metrics alphabetically by data class. Use these metric names for exporting data with the extract utility. You can also use these metric names in defining alarm conditions in your alarmdef file. * "Metric Definitions," which describes each metric in alphabetical order. This section contains the list of platforms on which a particular metric is supported. Note that whenever 'Linux' is included the metrics is available on vMA and when 'Windows' is included the metrics is available on Hyper-V. Please note that the metric help has been put in a more generic format and references are made to the other platforms that also support each of the metrics. Metric Names by Data Class ========================== All Global Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR GBL_ACTIVE_CPU GBL_ACTIVE_PROC GBL_ALIVE_PROC GBL_ALIVE_THREAD GBL_BLOCKED_IO_QUEUE GBL_BYDSK_THRESHOLD GBL_COMPLETED_PROC GBL_CPU_CLOCK GBL_CPU_CSWITCH_TIME GBL_CPU_CSWITCH_UTIL GBL_CPU_ENTL GBL_CPU_ENTL_UTIL GBL_CPU_HISTOGRAM GBL_CPU_IDLE_TIME GBL_CPU_IDLE_UTIL GBL_CPU_INTERRUPT_TIME GBL_CPU_INTERRUPT_UTIL GBL_CPU_MT_ENABLED GBL_CPU_NICE_TIME GBL_CPU_NICE_UTIL GBL_CPU_NORMAL_TIME GBL_CPU_NORMAL_UTIL GBL_CPU_NUM_THREADS GBL_CPU_PHYSC GBL_CPU_PHYS_SYS_MODE_UTIL GBL_CPU_PHYS_TOTAL_UTIL GBL_CPU_PHYS_USER_MODE_UTIL GBL_CPU_QUEUE GBL_CPU_REALTIME_TIME GBL_CPU_REALTIME_UTIL GBL_CPU_SYSCALL_TIME GBL_CPU_SYSCALL_UTIL GBL_CPU_SYS_MODE_TIME GBL_CPU_SYS_MODE_UTIL GBL_CPU_TOTAL_TIME GBL_CPU_TOTAL_UTIL GBL_CPU_USER_MODE_TIME GBL_CPU_USER_MODE_UTIL GBL_CPU_WAIT_TIME GBL_CPU_WAIT_UTIL GBL_CSWITCH_RATE GBL_DISK_BLOCK_IO GBL_DISK_BLOCK_IO_RATE GBL_DISK_BLOCK_READ GBL_DISK_BLOCK_READ_RATE GBL_DISK_BLOCK_WRITE GBL_DISK_BLOCK_WRITE_RATE GBL_DISK_CACHE_READ GBL_DISK_CACHE_READ_RATE GBL_DISK_FS_IO GBL_DISK_FS_IO_RATE GBL_DISK_FS_READ GBL_DISK_FS_READ_RATE GBL_DISK_FS_WRITE GBL_DISK_FS_WRITE_RATE GBL_DISK_HISTOGRAM GBL_DISK_LOGL_IO GBL_DISK_LOGL_IO_RATE GBL_DISK_LOGL_READ GBL_DISK_LOGL_READ_BYTE GBL_DISK_LOGL_READ_BYTE_RATE GBL_DISK_LOGL_READ_RATE GBL_DISK_LOGL_WRITE GBL_DISK_LOGL_WRITE_BYTE GBL_DISK_LOGL_WRITE_BYTE_RATE GBL_DISK_LOGL_WRITE_RATE GBL_DISK_PATH_COUNT GBL_DISK_PHYS_BYTE GBL_DISK_PHYS_BYTE_RATE GBL_DISK_PHYS_IO GBL_DISK_PHYS_IO_RATE GBL_DISK_PHYS_READ GBL_DISK_PHYS_READ_BYTE_RATE GBL_DISK_PHYS_READ_PCT GBL_DISK_PHYS_READ_RATE GBL_DISK_PHYS_WRITE GBL_DISK_PHYS_WRITE_BYTE_RATE GBL_DISK_PHYS_WRITE_RATE GBL_DISK_RAW_IO GBL_DISK_RAW_IO_RATE GBL_DISK_RAW_READ GBL_DISK_RAW_READ_RATE GBL_DISK_RAW_WRITE GBL_DISK_RAW_WRITE_RATE GBL_DISK_REQUEST_QUEUE GBL_DISK_SPACE GBL_DISK_SPACE_FREE GBL_DISK_SUBSYSTEM_QUEUE GBL_DISK_SYSTEM_IO GBL_DISK_SYSTEM_IO_RATE GBL_DISK_SYSTEM_READ GBL_DISK_SYSTEM_READ_RATE GBL_DISK_SYSTEM_WRITE GBL_DISK_SYSTEM_WRITE_RATE GBL_DISK_TIME_PEAK GBL_DISK_UTIL GBL_DISK_UTIL_PEAK GBL_DISK_VM_IO GBL_DISK_VM_IO_RATE GBL_DISK_VM_READ GBL_DISK_VM_READ_RATE GBL_DISK_VM_WRITE GBL_DISK_VM_WRITE_RATE GBL_FS_SPACE_UTIL_PEAK GBL_GUI_DELAY_INDEX GBL_GUI_INPUT_COUNT GBL_GUI_INPUT_DELAY GBL_GUI_INPUT_RATE GBL_GUI_KEYBOARD_COUNT GBL_GUI_KEYBOARD_RATE GBL_GUI_MOUSE_COUNT GBL_GUI_MOUSE_RATE GBL_HYP_UTIL GBL_INTERRUPT GBL_INTERRUPT_RATE GBL_INTERVAL GBL_IPC_SUBSYSTEM_QUEUE GBL_LOADAVG GBL_LOADAVG15 GBL_LOADAVG5 GBL_LOST_MI_TRACE_BUFFERS GBL_LS_CPU_NUM_DEDICATED GBL_LS_CPU_NUM_SHARED GBL_LS_NUM_CAPPED GBL_LS_NUM_DEDICATED GBL_LS_NUM_SHARED GBL_LS_NUM_UNCAPPED GBL_LS_PHYS_MEM_CONSUMED GBL_LS_PHYS_MEM_TOTAL GBL_MACHINE_MEM_USED GBL_MEM_ACTIVE_VIRT GBL_MEM_ACTIVE_VIRT_UTIL GBL_MEM_ARC_UTIL GBL_MEM_CACHE GBL_MEM_CACHE_FLUSH_RATE GBL_MEM_CACHE_HIT_PCT GBL_MEM_CACHE_UTIL GBL_MEM_CACHE_WRITE_HIT GBL_MEM_CACHE_WRITE_HIT_PCT GBL_MEM_COMMIT_PCT GBL_MEM_DATAMAP_HIT_PCT GBL_MEM_DISCARD GBL_MEM_DISCARD_RATE GBL_MEM_DNLC_HIT_PCT GBL_MEM_ENTL_UTIL GBL_MEM_FAULT_RATE GBL_MEM_FILE_PAGEIN_RATE GBL_MEM_FILE_PAGEOUT_RATE GBL_MEM_FILE_PAGE_CACHE GBL_MEM_FILE_PAGE_CACHE_UTIL GBL_MEM_FREE GBL_MEM_FREE_UTIL GBL_MEM_GDIRES_FREE GBL_MEM_LOAD_INDEX GBL_MEM_LOCKED GBL_MEM_LOCKED_UTIL GBL_MEM_OVERHEAD GBL_MEM_PAGEIN GBL_MEM_PAGEIN_BYTE GBL_MEM_PAGEIN_BYTE_RATE GBL_MEM_PAGEIN_RATE GBL_MEM_PAGEOUT GBL_MEM_PAGEOUT_BYTE GBL_MEM_PAGEOUT_BYTE_RATE GBL_MEM_PAGEOUT_RATE GBL_MEM_PAGE_FAULT GBL_MEM_PAGE_FAULT_RATE GBL_MEM_PAGE_REQUEST GBL_MEM_PAGE_REQUEST_RATE GBL_MEM_PG_SCAN GBL_MEM_PG_SCAN_RATE GBL_MEM_PG_STEAL_RATE GBL_MEM_PHYS GBL_MEM_PHYS_MB GBL_MEM_PHYS_SWAPPED GBL_MEM_QUEUE GBL_MEM_SWAP GBL_MEM_SWAPIN_BYTE GBL_MEM_SWAPIN_BYTE_RATE GBL_MEM_SWAPIN_RATE GBL_MEM_SWAPOUT_BYTE GBL_MEM_SWAPOUT_BYTE_RATE GBL_MEM_SWAPOUT_RATE GBL_MEM_SWAP_1_HR_RATE GBL_MEM_SWAP_QUEUE GBL_MEM_SYS GBL_MEM_SYSRES_FREE GBL_MEM_SYS_AND_CACHE_UTIL GBL_MEM_SYS_UTIL GBL_MEM_USER GBL_MEM_USERRES_FREE GBL_MEM_USER_REFERENCED_UTIL GBL_MEM_USER_UNREFERENCED_UTIL GBL_MEM_USER_UTIL GBL_MEM_UTIL GBL_MEM_VIRT GBL_NETWORK_SUBSYSTEM_QUEUE GBL_NET_BYTE_RATE GBL_NET_COLLISION GBL_NET_COLLISION_1_MIN_RATE GBL_NET_COLLISION_PCT GBL_NET_COLLISION_RATE GBL_NET_DEFERRED_PCT GBL_NET_ERROR GBL_NET_ERROR_1_MIN_RATE GBL_NET_ERROR_RATE GBL_NET_IN_ERROR_PCT GBL_NET_IN_ERROR_RATE GBL_NET_IN_PACKET GBL_NET_IN_PACKET_RATE GBL_NET_OUTQUEUE GBL_NET_OUT_ERROR_PCT GBL_NET_OUT_ERROR_RATE GBL_NET_OUT_PACKET GBL_NET_OUT_PACKET_RATE GBL_NET_PACKET_RATE GBL_NET_UTIL_PEAK GBL_NFS_CALL GBL_NFS_CALL_RATE GBL_NUM_DISK GBL_NUM_NETWORK GBL_NUM_ONLINE_VCPU GBL_NUM_USER GBL_NUM_VIRTUAL_TARGETS GBL_OTHER_QUEUE GBL_PARTITION_SPACE_MIN GBL_POOL_CPU_AVAIL GBL_POOL_TOTAL_UTIL GBL_PRI_QUEUE GBL_PROC_RUN_TIME GBL_PROC_SAMPLE GBL_QUEUE_HISTOGRAM GBL_RDR_BYTE_RATE GBL_RDR_REQUEST_RATE GBL_RUN_QUEUE GBL_SLEEP_QUEUE GBL_SRV_WRKITM_SHORTAGES GBL_STARTED_PROC GBL_STARTED_PROC_RATE GBL_STATTIME GBL_SUSPENDED_PROCS GBL_SVR_BYTE_RATE GBL_SWAP_SPACE_AVAIL GBL_SWAP_SPACE_DEVICE_AVAIL GBL_SWAP_SPACE_FREE GBL_SWAP_SPACE_MEM_AVAIL GBL_SWAP_SPACE_RESERVED GBL_SWAP_SPACE_USED GBL_SWAP_SPACE_USED_UTIL GBL_SWAP_SPACE_UTIL GBL_SYSCALL GBL_SYSCALL_RATE GBL_SYSCALL_READ_BYTE_RATE GBL_SYSCALL_WRITE_BYTE_RATE GBL_SYSTEM_UPTIME_HOURS GBL_SYSTEM_UPTIME_SECONDS GBL_TERM_FIRST_RESP_DIST_1 GBL_TERM_FIRST_RESP_DIST_10 GBL_TERM_FIRST_RESP_DIST_2 GBL_TERM_FIRST_RESP_DIST_3 GBL_TERM_FIRST_RESP_DIST_4 GBL_TERM_FIRST_RESP_DIST_5 GBL_TERM_FIRST_RESP_DIST_6 GBL_TERM_FIRST_RESP_DIST_7 GBL_TERM_FIRST_RESP_DIST_8 GBL_TERM_FIRST_RESP_DIST_9 GBL_TERM_IO_QUEUE GBL_TERM_RESP_DIST_1 GBL_TERM_RESP_DIST_10 GBL_TERM_RESP_DIST_2 GBL_TERM_RESP_DIST_3 GBL_TERM_RESP_DIST_4 GBL_TERM_RESP_DIST_5 GBL_TERM_RESP_DIST_6 GBL_TERM_RESP_DIST_7 GBL_TERM_RESP_DIST_8 GBL_TERM_RESP_DIST_9 GBL_TOTAL_DISPATCH_TIME GBL_TT_OVERFLOW_COUNT GBL_VCSWITCH_RATE GBL_WEB_CACHE_HIT_PCT GBL_WEB_CGI_REQUEST_RATE GBL_WEB_CONNECTION_RATE GBL_WEB_FILES_RECEIVED_RATE GBL_WEB_FILES_SENT_RATE GBL_WEB_FTP_READ_BYTE_RATE GBL_WEB_FTP_WRITE_BYTE_RATE GBL_WEB_GET_REQUEST_RATE GBL_WEB_GOPHER_READ_BYTE_RATE GBL_WEB_GOPHER_WRITE_BYTE_RATE GBL_WEB_HEAD_REQUEST_RATE GBL_WEB_HTTP_READ_BYTE_RATE GBL_WEB_HTTP_WRITE_BYTE_RATE GBL_WEB_ISAPI_REQUEST_RATE GBL_WEB_LOGON_FAILURES GBL_WEB_NOT_FOUND_ERRORS GBL_WEB_OTHER_REQUEST_RATE GBL_WEB_POST_REQUEST_RATE GBL_WEB_READ_BYTE_RATE GBL_WEB_WRITE_BYTE_RATE STATDATE STATTIME TBL_BUFFER_CACHE_AVAIL TBL_BUFFER_CACHE_USED TBL_FILE_LOCK_USED TBL_FILE_LOCK_UTIL TBL_FILE_TABLE_USED TBL_FILE_TABLE_UTIL TBL_INODE_CACHE_USED TBL_MSG_TABLE_USED TBL_MSG_TABLE_UTIL TBL_PROC_TABLE_USED TBL_PROC_TABLE_UTIL TBL_SEM_TABLE_USED TBL_SEM_TABLE_UTIL TBL_SHMEM_ACTIVE TBL_SHMEM_TABLE_USED TBL_SHMEM_TABLE_UTIL TBL_SHMEM_USED All Application Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR APP_ACTIVE_PCT APP_ACTIVE_PROC APP_ACTIVE_TIME APP_ALIVE_PROC APP_COMPLETED_PROC APP_CPU_NICE_TIME APP_CPU_NICE_UTIL APP_CPU_NORMAL_TIME APP_CPU_NORMAL_UTIL APP_CPU_REALTIME_TIME APP_CPU_REALTIME_UTIL APP_CPU_SYS_MODE_TIME APP_CPU_SYS_MODE_UTIL APP_CPU_TOTAL_TIME APP_CPU_TOTAL_UTIL APP_CPU_USER_MODE_TIME APP_CPU_USER_MODE_UTIL APP_DISK_BLOCK_IO APP_DISK_BLOCK_IO_RATE APP_DISK_BLOCK_READ APP_DISK_BLOCK_READ_RATE APP_DISK_BLOCK_WRITE APP_DISK_BLOCK_WRITE_RATE APP_DISK_FS_IO APP_DISK_FS_IO_RATE APP_DISK_LOGL_IO APP_DISK_LOGL_IO_RATE APP_DISK_LOGL_READ APP_DISK_LOGL_READ_RATE APP_DISK_LOGL_WRITE APP_DISK_LOGL_WRITE_RATE APP_DISK_PHYS_IO APP_DISK_PHYS_IO_RATE APP_DISK_PHYS_READ APP_DISK_PHYS_READ_RATE APP_DISK_PHYS_WRITE APP_DISK_PHYS_WRITE_RATE APP_DISK_RAW_IO APP_DISK_RAW_IO_RATE APP_DISK_SUBSYSTEM_WAIT_PCT APP_DISK_SYSTEM_IO APP_DISK_SYSTEM_IO_RATE APP_DISK_VM_IO APP_DISK_VM_IO_RATE APP_GUI_INPUT_COUNT APP_GUI_INPUT_RATE APP_GUI_KEYBOARD_COUNT APP_GUI_KEYBOARD_DELAY APP_GUI_KEYBOARD_RATE APP_GUI_MOUSE_COUNT APP_GUI_MOUSE_DELAY APP_GUI_MOUSE_RATE APP_IO_BYTE APP_IO_BYTE_RATE APP_IPC_SUBSYSTEM_WAIT_PCT APP_LS_ID APP_MAJOR_FAULT APP_MAJOR_FAULT_RATE APP_MEM_RES APP_MEM_UTIL APP_MEM_VIRT APP_MEM_WAIT_PCT APP_MINOR_FAULT APP_MINOR_FAULT_RATE APP_NAME APP_NETWORK_SUBSYSTEM_WAIT_PCT APP_NUM APP_OTHER_IO_WAIT_PCT APP_PRI APP_PRI_STD_DEV APP_PRI_WAIT_PCT APP_PRM_CPUCAP_MODE APP_PRM_CPU_ENTITLEMENT APP_PRM_LOGGING_MODE APP_PRM_MEM_AVAIL APP_PRM_MEM_ENTITLEMENT APP_PRM_MEM_STATE APP_PRM_MEM_UPPERBOUND APP_PRM_MEM_UTIL APP_PRM_STATE APP_PROC_RUN_TIME APP_REVERSE_PRI APP_REV_PRI_STD_DEV APP_SAMPLE APP_SEM_WAIT_PCT APP_SLEEP_WAIT_PCT APP_SUSPENDED_PROCS APP_TERM_IO_WAIT_PCT All Process Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR PROC_APP_ID PROC_CPU_ALIVE_SYS_MODE_UTIL PROC_CPU_ALIVE_TOTAL_UTIL PROC_CPU_ALIVE_USER_MODE_UTIL PROC_CPU_CSWITCH_TIME PROC_CPU_CSWITCH_UTIL PROC_CPU_INTERRUPT_TIME PROC_CPU_INTERRUPT_UTIL PROC_CPU_NICE_TIME PROC_CPU_NICE_UTIL PROC_CPU_NORMAL_TIME PROC_CPU_NORMAL_UTIL PROC_CPU_REALTIME_TIME PROC_CPU_REALTIME_UTIL PROC_CPU_SYSCALL_TIME PROC_CPU_SYSCALL_UTIL PROC_CPU_SYS_MODE_TIME PROC_CPU_SYS_MODE_UTIL PROC_CPU_TOTAL_TIME PROC_CPU_TOTAL_TIME_CUM PROC_CPU_TOTAL_UTIL PROC_CPU_TOTAL_UTIL_CUM PROC_CPU_USER_MODE_TIME PROC_CPU_USER_MODE_UTIL PROC_DISK_BLOCK_IO PROC_DISK_BLOCK_IO_CUM PROC_DISK_BLOCK_IO_RATE PROC_DISK_BLOCK_IO_RATE_CUM PROC_DISK_BLOCK_READ PROC_DISK_BLOCK_READ_RATE PROC_DISK_BLOCK_WRITE PROC_DISK_BLOCK_WRITE_RATE PROC_DISK_FS_IO PROC_DISK_FS_IO_RATE PROC_DISK_FS_READ PROC_DISK_FS_READ_RATE PROC_DISK_FS_WRITE PROC_DISK_FS_WRITE_RATE PROC_DISK_LOGL_IO_CUM PROC_DISK_LOGL_IO_RATE_CUM PROC_DISK_LOGL_READ PROC_DISK_LOGL_READ_RATE PROC_DISK_LOGL_WRITE PROC_DISK_LOGL_WRITE_RATE PROC_DISK_PHYS_IO PROC_DISK_PHYS_IO_CUM PROC_DISK_PHYS_IO_RATE PROC_DISK_PHYS_IO_RATE_CUM PROC_DISK_PHYS_READ PROC_DISK_PHYS_READ_RATE PROC_DISK_PHYS_WRITE PROC_DISK_PHYS_WRITE_RATE PROC_DISK_SUBSYSTEM_WAIT_PCT PROC_DISK_SUBSYSTEM_WAIT_TIME PROC_DISK_SYSTEM_IO PROC_DISK_SYSTEM_IO_RATE PROC_DISK_VM_IO PROC_DISK_VM_IO_RATE PROC_EUID PROC_FORCED_CSWITCH PROC_GROUP_ID PROC_INTEREST PROC_INTERVAL_ALIVE PROC_IO_BYTE PROC_IO_BYTE_CUM PROC_IO_BYTE_RATE PROC_IO_BYTE_RATE_CUM PROC_IPC_SUBSYSTEM_WAIT_PCT PROC_IPC_SUBSYSTEM_WAIT_TIME PROC_LAN_WAIT_PCT PROC_LAN_WAIT_TIME PROC_LS_ID PROC_MAJOR_FAULT PROC_MEM_LOCKED PROC_MEM_RES PROC_MEM_VIRT PROC_MEM_WAIT_PCT PROC_MEM_WAIT_TIME PROC_MINOR_FAULT PROC_NFS_WAIT_PCT PROC_NFS_WAIT_TIME PROC_OTHER_IO_WAIT_PCT PROC_OTHER_IO_WAIT_TIME PROC_OTHER_WAIT_PCT PROC_OTHER_WAIT_TIME PROC_PAGEFAULT PROC_PAGEFAULT_RATE PROC_PARENT_PROC_ID PROC_PRI PROC_PRI_WAIT_PCT PROC_PRI_WAIT_TIME PROC_PRMID PROC_PROC_ARGV1 PROC_PROC_CMD PROC_PROC_ID PROC_PROC_NAME PROC_REVERSE_PRI PROC_RUN_TIME PROC_SEM_WAIT_PCT PROC_SEM_WAIT_TIME PROC_SLEEP_WAIT_PCT PROC_SLEEP_WAIT_TIME PROC_STARTTIME PROC_STOP_HISTOGRAM PROC_STOP_REASON PROC_SYS_WAIT_PCT PROC_SYS_WAIT_TIME PROC_TERM_IO_WAIT_PCT PROC_TERM_IO_WAIT_TIME PROC_THREAD_COUNT PROC_TTY PROC_USER_NAME PROC_VOLUNTARY_CSWITCH All Transaction Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR TTBIN_TRANS_COUNT_1 TTBIN_TRANS_COUNT_10 TTBIN_TRANS_COUNT_2 TTBIN_TRANS_COUNT_3 TTBIN_TRANS_COUNT_4 TTBIN_TRANS_COUNT_5 TTBIN_TRANS_COUNT_6 TTBIN_TRANS_COUNT_7 TTBIN_TRANS_COUNT_8 TTBIN_TRANS_COUNT_9 TTBIN_UPPER_RANGE_1 TTBIN_UPPER_RANGE_10 TTBIN_UPPER_RANGE_2 TTBIN_UPPER_RANGE_3 TTBIN_UPPER_RANGE_4 TTBIN_UPPER_RANGE_5 TTBIN_UPPER_RANGE_6 TTBIN_UPPER_RANGE_7 TTBIN_UPPER_RANGE_8 TTBIN_UPPER_RANGE_9 TT_ABORT TT_ABORT_WALL_TIME_PER_TRAN TT_APP_NAME TT_APP_TRAN_NAME TT_CLIENT_ADDRESS TT_CLIENT_ADDRESS_FORMAT TT_CLIENT_TRAN_ID TT_COUNT TT_CPU_TOTAL_TIME_PER_TRAN TT_DISK_LOGL_IO_PER_TRAN TT_DISK_PHYS_IO_PER_TRAN TT_FAILED TT_INFO TT_NAME TT_NUM_BINS TT_SLO_COUNT TT_SLO_PERCENT TT_SLO_THRESHOLD TT_TERM_TRAN_1_HR_RATE TT_TRAN_1_MIN_RATE TT_TRAN_ID TT_UNAME TT_USER_MEASUREMENT_AVG TT_USER_MEASUREMENT_AVG_2 TT_USER_MEASUREMENT_AVG_3 TT_USER_MEASUREMENT_AVG_4 TT_USER_MEASUREMENT_AVG_5 TT_USER_MEASUREMENT_AVG_6 TT_USER_MEASUREMENT_COUNT TT_USER_MEASUREMENT_COUNT_2 TT_USER_MEASUREMENT_COUNT_3 TT_USER_MEASUREMENT_COUNT_4 TT_USER_MEASUREMENT_COUNT_5 TT_USER_MEASUREMENT_COUNT_6 TT_USER_MEASUREMENT_MAX TT_USER_MEASUREMENT_MAX_2 TT_USER_MEASUREMENT_MAX_3 TT_USER_MEASUREMENT_MAX_4 TT_USER_MEASUREMENT_MAX_5 TT_USER_MEASUREMENT_MAX_6 TT_USER_MEASUREMENT_MIN TT_USER_MEASUREMENT_MIN_2 TT_USER_MEASUREMENT_MIN_3 TT_USER_MEASUREMENT_MIN_4 TT_USER_MEASUREMENT_MIN_5 TT_USER_MEASUREMENT_MIN_6 TT_USER_MEASUREMENT_NAME TT_USER_MEASUREMENT_NAME_2 TT_USER_MEASUREMENT_NAME_3 TT_USER_MEASUREMENT_NAME_4 TT_USER_MEASUREMENT_NAME_5 TT_USER_MEASUREMENT_NAME_6 TT_WALL_TIME_PER_TRAN All Disk Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR BYDSK_AVG_QUEUE_TIME BYDSK_AVG_READ_QUEUE_TIME BYDSK_AVG_READ_SERVICE_TIME BYDSK_AVG_REQUEST_QUEUE BYDSK_AVG_SERVICE_TIME BYDSK_AVG_WRITE_QUEUE_TIME BYDSK_AVG_WRITE_SERVICE_TIME BYDSK_BUSY_TIME BYDSK_CURR_QUEUE_LENGTH BYDSK_DEVNAME BYDSK_DIRNAME BYDSK_DISKNAME BYDSK_FS_READ BYDSK_FS_READ_RATE BYDSK_FS_WRITE BYDSK_FS_WRITE_RATE BYDSK_HISTOGRAM BYDSK_ID BYDSK_LOGL_READ BYDSK_LOGL_READ_RATE BYDSK_LOGL_WRITE BYDSK_LOGL_WRITE_RATE BYDSK_PHYS_BYTE BYDSK_PHYS_BYTE_RATE BYDSK_PHYS_IO BYDSK_PHYS_IO_RATE BYDSK_PHYS_READ BYDSK_PHYS_READ_BYTE BYDSK_PHYS_READ_BYTE_RATE BYDSK_PHYS_READ_RATE BYDSK_PHYS_WRITE BYDSK_PHYS_WRITE_BYTE BYDSK_PHYS_WRITE_BYTE_RATE BYDSK_PHYS_WRITE_RATE BYDSK_RAW_READ BYDSK_RAW_READ_RATE BYDSK_RAW_WRITE BYDSK_RAW_WRITE_RATE BYDSK_REQUEST_QUEUE BYDSK_SYSTEM_IO BYDSK_SYSTEM_IO_RATE BYDSK_UTIL BYDSK_VM_IO BYDSK_VM_IO_RATE BYDSK_VM_READ_RATE BYDSK_VM_WRITE_RATE All Logical Volume Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR FS_DIRNAME LV_DEVNAME_ALIAS LV_DIRNAME LV_DIRNAME_ALIAS LV_GROUP_NAME LV_LOGL_READ LV_LOGL_WRITE LV_READ_BYTE_RATE LV_READ_RATE LV_SPACE_UTIL LV_WRITE_BYTE_RATE LV_WRITE_RATE All Network Interface Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR BYNETIF_COLLISION BYNETIF_COLLISION_1_MIN_RATE BYNETIF_COLLISION_RATE BYNETIF_ERROR BYNETIF_ERROR_1_MIN_RATE BYNETIF_ERROR_RATE BYNETIF_ID BYNETIF_IN_BYTE BYNETIF_IN_BYTE_RATE BYNETIF_IN_BYTE_RATE_CUM BYNETIF_IN_PACKET BYNETIF_IN_PACKET_RATE BYNETIF_NAME BYNETIF_NET_MTU BYNETIF_NET_SPEED BYNETIF_NET_TYPE BYNETIF_OUT_BYTE BYNETIF_OUT_BYTE_RATE BYNETIF_OUT_BYTE_RATE_CUM BYNETIF_OUT_PACKET BYNETIF_OUT_PACKET_RATE BYNETIF_PACKET_RATE BYNETIF_QUEUE BYNETIF_UTIL BYPROTOCOL_IN_PACKET BYPROTOCOL_IN_PACKET_RATE BYPROTOCOL_OUT_PACKET BYPROTOCOL_OUT_PACKET_RATE All CPU Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR BYCPU_CPU_CLOCK BYCPU_CPU_PHYSC BYCPU_CPU_SYS_MODE_TIME BYCPU_CPU_SYS_MODE_UTIL BYCPU_CPU_TOTAL_TIME BYCPU_CPU_TOTAL_UTIL BYCPU_CPU_USER_MODE_TIME BYCPU_CPU_USER_MODE_UTIL BYCPU_CSWITCH_RATE BYCPU_ID BYCPU_INTERRUPT BYCPU_INTERRUPT_RATE BYCPU_STATE All Filesystem Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR FS_BLOCK_SIZE FS_DEVNAME FS_DEVNAME_ALIAS FS_DEVNO FS_DIRNAME_ALIAS FS_FRAG_SIZE FS_INODE_UTIL FS_MAX_INODES FS_MAX_SIZE FS_REQUEST_QUEUE FS_SPACE_RESERVED FS_SPACE_USED FS_SPACE_UTIL FS_TYPE All Configuration Metrics ---------------------------------- BLANK BYLS_BOOT_TIME BYLS_CLUSTER_NAME BYLS_CPU_CLOCK BYLS_CPU_CYCLE_ENTL_MAX BYLS_CPU_CYCLE_ENTL_MIN BYLS_CPU_CYCLE_TOTAL_USED BYLS_CPU_ENTL BYLS_CPU_ENTL_EMIN BYLS_CPU_ENTL_MAX BYLS_CPU_ENTL_MIN BYLS_CPU_ENTL_UTIL BYLS_CPU_MT_ENABLED BYLS_CPU_PHYSC BYLS_CPU_PHYS_IDLE_MODE_UTIL BYLS_CPU_PHYS_READY_UTIL BYLS_CPU_PHYS_SYS_MODE_UTIL BYLS_CPU_PHYS_TOTAL_TIME BYLS_CPU_PHYS_TOTAL_UTIL BYLS_CPU_PHYS_USER_MODE_UTIL BYLS_CPU_PHYS_WAIT_MODE_UTIL BYLS_CPU_PHYS_WAIT_UTIL BYLS_CPU_SHARES_PRIO BYLS_CPU_SYS_MODE_UTIL BYLS_CPU_TOTAL_UTIL BYLS_CPU_UNRESERVED BYLS_CPU_USER_MODE_UTIL BYLS_DATACENTER_NAME BYLS_DISK_PHYS_BYTE BYLS_DISK_PHYS_BYTE_RATE BYLS_DISK_PHYS_READ BYLS_DISK_PHYS_READ_BYTE_RATE BYLS_DISK_PHYS_READ_RATE BYLS_DISK_PHYS_WRITE BYLS_DISK_PHYS_WRITE_BYTE_RATE BYLS_DISK_PHYS_WRITE_RATE BYLS_DISK_UTIL BYLS_DISK_UTIL_PEAK BYLS_DISPLAY_NAME BYLS_HYPCALL BYLS_HYP_UTIL BYLS_IP_ADDRESS BYLS_LS_HOSTNAME BYLS_LS_HOST_HOSTNAME BYLS_LS_ID BYLS_LS_MODE BYLS_LS_NAME BYLS_LS_OSTYPE BYLS_LS_PARENT_TYPE BYLS_LS_PARENT_UUID BYLS_LS_PATH BYLS_LS_PROC_ID BYLS_LS_ROLE BYLS_LS_SHARED BYLS_LS_STATE BYLS_LS_TYPE BYLS_LS_UUID BYLS_MACHINE_MODEL BYLS_MEM_ACTIVE BYLS_MEM_AVAIL BYLS_MEM_BALLOON_USED BYLS_MEM_BALLOON_UTIL BYLS_MEM_ENTL BYLS_MEM_ENTL_MAX BYLS_MEM_ENTL_MIN BYLS_MEM_ENTL_UTIL BYLS_MEM_FREE BYLS_MEM_FREE_UTIL BYLS_MEM_HEALTH BYLS_MEM_LOCKED BYLS_MEM_LOCKED_USED BYLS_MEM_LOCKED_UTIL BYLS_MEM_OVERHEAD BYLS_MEM_PHYS BYLS_MEM_PHYS_UTIL BYLS_MEM_SHARES_PRIO BYLS_MEM_SWAP BYLS_MEM_SWAPIN BYLS_MEM_SWAPOUT BYLS_MEM_SWAPPED BYLS_MEM_SWAPTARGET BYLS_MEM_SWAP_USED BYLS_MEM_SWAP_UTIL BYLS_MEM_SYS BYLS_MEM_UNRESERVED BYLS_MEM_USED BYLS_NET_BYTE_RATE BYLS_NET_IN_BYTE BYLS_NET_IN_PACKET BYLS_NET_IN_PACKET_RATE BYLS_NET_OUT_BYTE BYLS_NET_OUT_PACKET BYLS_NET_OUT_PACKET_RATE BYLS_NET_PACKET_RATE BYLS_NUM_ACTIVE_LS BYLS_NUM_CPU BYLS_NUM_CPU_CORE BYLS_NUM_DISK BYLS_NUM_LS BYLS_NUM_NETIF BYLS_NUM_SOCKET BYLS_PHANTOM_INTR BYLS_POOL_NAME BYLS_RUN_QUEUE BYLS_SCHEDULING_CLASS BYLS_UPTIME_HOURS BYLS_UPTIME_SECONDS BYLS_VCSWITCH_RATE BYLS_VC_IP_ADDRESS DATE DATE_SECONDS DAY INTERVAL RECORD_TYPE TIME YEAR GBL_ACTIVE_CPU_CORE GBL_APP_THRESHOLD GBL_BOOT_TIME GBL_BYCPU_THRESHOLD GBL_BYFS_THRESHOLD GBL_BYNETIF_THRESHOLD GBL_COLLECTOR GBL_COLLECT_INTERVAL GBL_COLLECT_INTERVAL_PROC GBL_CPU_CYCLE_ENTL_MAX GBL_CPU_CYCLE_ENTL_MIN GBL_CPU_ENTL_MAX GBL_CPU_ENTL_MIN GBL_CPU_SHARES_PRIO GBL_DISTRIBUTION GBL_FLUSH GBL_GMTOFFSET GBL_IGNORE_MT GBL_JAVAARG GBL_LOGFILE_VERSION GBL_LOGGING_TYPES GBL_LS_ID GBL_LS_MODE GBL_LS_ROLE GBL_LS_SHARED GBL_LS_TYPE GBL_LS_UUID GBL_LV_THRESHOLD GBL_MACHINE GBL_MACHINE_MODEL GBL_MEM_AVAIL GBL_MEM_ENTL_MAX GBL_MEM_ENTL_MIN GBL_MEM_ONLINE GBL_MEM_SHARES_PRIO GBL_NUM_ACTIVE_LS GBL_NUM_APP GBL_NUM_CPU GBL_NUM_CPU_CORE GBL_NUM_LS GBL_NUM_LV GBL_NUM_SOCKET GBL_NUM_VSWITCH GBL_OSKERNELTYPE_INT GBL_OSNAME GBL_OSRELEASE GBL_OSVERSION GBL_POOL_CPU_ENTL GBL_POOL_ID GBL_POOL_NUM_CPU GBL_SUBPROCSAMPLEINTERVAL GBL_SWAP_SPACE_AVAIL_KB GBL_SYSTEM_ID GBL_TERM_FIRST_RESP_RANGE_1 GBL_TERM_FIRST_RESP_RANGE_10 GBL_TERM_FIRST_RESP_RANGE_2 GBL_TERM_FIRST_RESP_RANGE_3 GBL_TERM_FIRST_RESP_RANGE_4 GBL_TERM_FIRST_RESP_RANGE_5 GBL_TERM_FIRST_RESP_RANGE_6 GBL_TERM_FIRST_RESP_RANGE_7 GBL_TERM_FIRST_RESP_RANGE_8 GBL_TERM_FIRST_RESP_RANGE_9 GBL_TERM_RESP_RANGE_1 GBL_TERM_RESP_RANGE_10 GBL_TERM_RESP_RANGE_2 GBL_TERM_RESP_RANGE_3 GBL_TERM_RESP_RANGE_4 GBL_TERM_RESP_RANGE_5 GBL_TERM_RESP_RANGE_6 GBL_TERM_RESP_RANGE_7 GBL_TERM_RESP_RANGE_8 GBL_TERM_RESP_RANGE_9 GBL_THRESHOLD_CPU GBL_THRESHOLD_DISK GBL_THRESHOLD_FIRSTRESP GBL_THRESHOLD_MAXTHINK GBL_THRESHOLD_MINTHINK GBL_THRESHOLD_NOKILLED GBL_THRESHOLD_NONEW GBL_THRESHOLD_PROCMEM GBL_THRESHOLD_RESPONSE GBL_THRESHOLD_SHORTLIVED GBL_THRESHOLD_TRANS GBL_THRESHOLD_WAIT_CPU GBL_THRESHOLD_WAIT_DISK GBL_THRESHOLD_WAIT_IMPEDE GBL_THRESHOLD_WAIT_MEMORY TBL_FILE_LOCK_AVAIL TBL_FILE_TABLE_AVAIL TBL_INODE_CACHE_AVAIL TBL_MSG_TABLE_AVAIL TBL_PROC_TABLE_AVAIL TBL_SEM_TABLE_AVAIL TBL_SHMEM_TABLE_AVAIL Metric Definitions ================== APP_ACTIVE_PCT ---------------------------------- The proportion of the interval that this APP_NAME has been active. An application is considered active if it has a window that is in the active state. Applications that do not display windows, or that perform processing activity while their windows are not in the active state are not considered active. APP_ACTIVE_PROC ---------------------------------- An active process is one that exists and consumes some CPU time. APP_ACTIVE_PROC is the sum of the alive-process-time/interval-time ratios of every process belonging to an application that is active (uses any CPU time) during an interval. The following diagram of a four second interval showing two processes, A and B, for an application should be used to understand the above definition. Note the difference between active processes, which consume CPU time, and alive processes which merely exist on the system. ----------- Seconds ----------- 1 2 3 4 Proc ---- ---- ---- ---- ---- A live live live live B live/CPU live/CPU live dead Process A is alive for the entire four second interval, but consumes no CPU. A’s contribution to APP_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to APP_ACTIVE_PROC. B’s contribution to APP_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to APP_ACTIVE_PROC. Thus, for this interval, APP_ACTIVE_PROC equals 0.5 and APP_ALIVE_PROC equals 1.75. Because a process may be alive but not active, APP_ACTIVE_PROC will always be less than or equal to APP_ALIVE_PROC. This metric indicates the number of processes in an application group that are competing for the CPU. This metric is useful, along with other metrics, for comparing loads placed on the system by different groups of processes. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. APP_ACTIVE_TIME ---------------------------------- The number of seconds during the interval that this application had windows in the active state. APP_ALIVE_PROC ---------------------------------- An alive process is one that exists on the system. APP_ALIVE_PROC is the sum of the alive-process-time/interval-time ratios for every process belonging to a given application. The following diagram of a four second interval showing two processes, A and B, for an application should be used to understand the above definition. Note the difference between active processes, which consume CPU time, and alive processes which merely exist on the system. ----------- Seconds ----------- 1 2 3 4 Proc ---- ---- ---- ---- ---- A live live live live B live/CPU live/CPU live dead Process A is alive for the entire four second interval but consumes no CPU. A’s contribution to APP_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to APP_ACTIVE_PROC. B’s contribution to APP_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to APP_ACTIVE_PROC. Thus, for this interval, APP_ACTIVE_PROC equals 0.5 and APP_ALIVE_PROC equals 1.75. Because a process may be alive but not active, APP_ACTIVE_PROC will always be less than or equal to APP_ALIVE_PROC. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. APP_COMPLETED_PROC ---------------------------------- The number of processes in this group that completed during the interval. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. APP_CPU_NICE_TIME ---------------------------------- The time, in seconds, that processes in this group were using the CPU in user mode at a nice priority during the interval. On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_NICE_UTIL ---------------------------------- The percentage of time that processes in this group were using the CPU in user mode at a nice priority during the interval. On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_NORMAL_TIME ---------------------------------- The time, in seconds, that processes in this group were in user mode at a normal priority during the interval. Normal priority user mode CPU excludes CPU used at real-time and nice priorities. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_NORMAL_UTIL ---------------------------------- The percentage of time that processes in this group were in user mode running at normal priority during the interval. Normal priority user mode CPU excludes CPU used at real-time and nice priorities. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_REALTIME_TIME ---------------------------------- The time, in seconds, that the processes in this group were in user mode at a “realtime” priority during the interval. “Realtime” priority is 0-127. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_REALTIME_UTIL ---------------------------------- The percentage of time that processes in this group were in user mode at a “realtime” priority during the interval. “Realtime” priority is 0-127. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_SYS_MODE_TIME ---------------------------------- The time, in seconds, during the interval that the CPU was in system mode for processes in this group. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_SYS_MODE_UTIL ---------------------------------- The percentage of time during the interval that the CPU was used in system mode for processes in this group. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. High system CPU utilizations are normal for IO intensive groups. Abnormally high system CPU utilization can indicate that a hardware problem is causing a high interrupt rate. It can also indicate programs that are not making efficient system calls. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_TOTAL_TIME ---------------------------------- The total CPU time, in seconds, devoted to processes in this group during the interval. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_TOTAL_UTIL ---------------------------------- The percentage of the total CPU time devoted to processes in this group during the interval. This indicates the relative CPU load placed on the system by processes in this group. AIX On AIX SPLPAR, this metric indicates the total physical processing units consumed by applications. Hence sum of the APP_CPU_TOTAL_UTIL for all applications must be compared with GBL_CPU_PHYS_TOTAL_UTIL. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. Large values for this metric may indicate that this group is causing a CPU bottleneck. This would be normal in a computation-bound workload, but might mean that processes are using excessive CPU time and perhaps looping. If the “other” application shows significant amounts of CPU, you may want to consider tuning your parm file so that process activity is accounted for in known applications. APP_CPU_TOTAL_UTIL = APP_CPU_SYS_MODE_UTIL + APP_CPU_USER_MODE_UTIL NOTE: On Windows, the sum of the APP_CPU_TOTAL_UTIL metrics may not equal GBL_CPU_TOTAL_UTIL. Microsoft states that “this is expected behavior” because the GBL_CPU_TOTAL_UTIL metric is taken from the NT performance library Processor objects while the APP_CPU_TOTAL_UTIL metrics are taken from the Process objects. Microsoft states that there can be CPU time accounted for in the Processor system objects that may not be seen in the Process objects. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_USER_MODE_TIME ---------------------------------- The time, in seconds, that processes in this group were in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_CPU_USER_MODE_UTIL ---------------------------------- The percentage of time that processes in this group were using the CPU in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. High user mode CPU percentages are normal for computation-intensive groups. Low values of user CPU utilization compared to relatively high values for APP_CPU_SYS_MODE_UTIL can indicate a hardware problem or improperly tuned programs in this group. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. APP_DISK_BLOCK_IO ---------------------------------- The number of block IOs to the file system buffer cache for processes in this group during the interval. On Sun 5.X (Solaris 2.X or later), these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, the traditional file system buffer cache is not normally used, since files are implicitly memory mapped and the access is through the virtual memory system rather than the buffer cache. However, if a file is read as a block device (e.g /dev/hdisk1), the file system buffer cache is used, making this metric meaningful in that situation. If no IO through the buffer cache occurs during the interval, this metric is 0. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. APP_DISK_BLOCK_IO_RATE ---------------------------------- The number of block IOs per second to the file system buffer cache for processes in this group during the interval. On Sun 5.X (Solaris 2.X or later), these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, the traditional file system buffer cache is not normally used, since files are implicitly memory mapped and the access is through the virtual memory system rather than the buffer cache. However, if a file is read as a block device (e.g /dev/hdisk1), the file system buffer cache is used, making this metric meaningful in that situation. If no IO through the buffer cache occurs during the interval, this metric is 0. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. APP_DISK_BLOCK_READ ---------------------------------- The number of block reads from the file system buffer cache for processes in this group during the interval. On Sun 5.X (Solaris 2.X or later), these are physical reads generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, the traditional file system buffer cache is not normally used, since files are implicitly memory mapped and the access is through the virtual memory system rather than the buffer cache. However, if a file is read as a block device (e.g /dev/hdisk1), the file system buffer cache is used, making this metric meaningful in that situation. If no IO through the buffer cache occurs during the interval, this metric is 0. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. APP_DISK_BLOCK_READ_RATE ---------------------------------- The number of block reads per second from the file system buffer cache for processes in this group during the interval. On Sun 5.X (Solaris 2.X or later), these are physical reads generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, the traditional file system buffer cache is not normally used, since files are implicitly memory mapped and the access is through the virtual memory system rather than the buffer cache. However, if a file is read as a block device (e.g /dev/hdisk1), the file system buffer cache is used, making this metric meaningful in that situation. If no IO through the buffer cache occurs during the interval, this metric is 0. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. APP_DISK_BLOCK_WRITE ---------------------------------- The number of block writes to the file system buffer cache for processes in this group during the interval. On Sun 5.X (Solaris 2.X or later), these are physical writes generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. APP_DISK_BLOCK_WRITE_RATE ---------------------------------- The number of block writes per second from the file system buffer cache for processes in this group during the interval. On Sun 5.X (Solaris 2.X or later), these are physical writes generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, the traditional file system buffer cache is not normally used, since files are implicitly memory mapped and the access is through the virtual memory system rather than the buffer cache. However, if a file is read as a block device (e.g /dev/hdisk1), the file system buffer cache is used, making this metric meaningful in that situation. If no IO through the buffer cache occurs during the interval, this metric is 0. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. APP_DISK_FS_IO ---------------------------------- The number of file system disk IOs for processes in this group during the interval. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access), or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical IOs in this category (they appear under virtual memory IOs). APP_DISK_FS_IO_RATE ---------------------------------- The number of file system disk IOs for processes in this group during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical IOs generated by user file system access and do not include virtual memory IOs, system IOs (inode updates), or IOs relating to raw disk access. An exception is user files accessed via the mmap(2) call, which will not show their physical IOs in this category. They appear under virtual memory IOs. APP_DISK_LOGL_IO ---------------------------------- The number of logical IOs for processes in this group during the interval. On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. APP_DISK_LOGL_IO_RATE ---------------------------------- The number of logical IOs per second for processes in this group during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. APP_DISK_LOGL_READ ---------------------------------- The number of logical reads for processes in this group during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. APP_DISK_LOGL_READ_RATE ---------------------------------- The number of logical reads per second for processes in this group during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. APP_DISK_LOGL_WRITE ---------------------------------- The number of logical writes for processes in this group during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. APP_DISK_LOGL_WRITE_RATE ---------------------------------- The number of logical writes per second for processes in this group during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. APP_DISK_PHYS_IO ---------------------------------- The number of physical IOs for processes in this group during the interval. On SUN systems, this metric is only available on Sun 5.X or later. APP_DISK_PHYS_IO_RATE ---------------------------------- The number of physical IOs per second for processes in this group during the interval. APP_DISK_PHYS_READ ---------------------------------- The number of physical reads for processes in this group during the interval. APP_DISK_PHYS_READ_RATE ---------------------------------- The number of physical reads per second for processes in this group during the interval. APP_DISK_PHYS_WRITE ---------------------------------- The number of physical writes for processes in this group during the interval. APP_DISK_PHYS_WRITE_RATE ---------------------------------- The number of physical writes per second for processes in this group during the interval. APP_DISK_RAW_IO ---------------------------------- The total number of raw IOs for processes in this group during the interval. Only accesses to local disk devices are counted. APP_DISK_RAW_IO_RATE ---------------------------------- The total number of raw IOs for processes in this group during the interval. Only accesses to local disk devices are counted. APP_DISK_SUBSYSTEM_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on the disk subsystem (waiting for their file system IOs to complete) during the interval. This is the sum of processes or kernel threads in the DISK, INODE, CACHE and CDFS wait states. It does not include processes or kernel threads doing raw IO to disk devices. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_DISK_SYSTEM_IO ---------------------------------- The number of physical IOs generated by the kernel for file system management (inode accesses or updates) for processes in this group during the interval APP_DISK_SYSTEM_IO_RATE ---------------------------------- The number of physical IOs per second generated by the kernel for file system management (inode accesses or updates) for processes in this group during the interval. APP_DISK_VM_IO ---------------------------------- The number of virtual memory IOs made on behalf of processes in this group during the interval. IOs to user file data are not included in this metric unless they were done via the mmap(2) system call. APP_DISK_VM_IO_RATE ---------------------------------- The number of virtual memory IOs per second made on behalf of processes in this group during the interval. IOs to user file data are not included in this metric unless they were done via the mmap(2) system call. APP_GUI_INPUT_COUNT ---------------------------------- The number of keyboard strokes and mouse clicks during the time the application was active. APP_GUI_INPUT_RATE ---------------------------------- The number of keyboard strokes and mouse clicks per minute during the time the application was active. APP_GUI_KEYBOARD_COUNT ---------------------------------- The number of keyboard depressions during the time the application was active. APP_GUI_KEYBOARD_DELAY ---------------------------------- The average delay in milliseconds between system receipt of a keyboard message and the delivery of that message to an application. APP_GUI_KEYBOARD_RATE ---------------------------------- The rate per minute of keyboard depressions during the time the application was active. APP_GUI_MOUSE_COUNT ---------------------------------- The number of mouse clicks during the time the application was active. APP_GUI_MOUSE_DELAY ---------------------------------- The average delay in milliseconds between system receipt of a mouse message and the delivery of that message to an application. APP_GUI_MOUSE_RATE ---------------------------------- The rate per minute of mouse clicks during the time the application was active. APP_IO_BYTE ---------------------------------- The number of characters (in KB) transferred for processes in this group to all devices during the interval. This includes IO to disk, terminal, tape and printers. APP_IO_BYTE_RATE ---------------------------------- The number of characters (in KB) per second transferred for processes in this group to all devices during the interval. This includes IO to disk, terminal, tape and printers. APP_IPC_SUBSYSTEM_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on the InterProcess Communication (IPC) subsystems (waiting for their interprocess communication activity to complete) during the interval. This is the sum of processes or kernel threads in the IPC, MSG, SEM, PIPE, SOCKT (that is, sockets) and STRMS (that is, streams IO) wait states. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_LS_ID ---------------------------------- APP_LS_ID represents the zone-id of the zone associated with this application. This metric is only available on Solaris 10 and above versions when the zone_app flag in parm file is set. APP_MAJOR_FAULT ---------------------------------- The number of major page faults that required a disk IO for processes in this group during the interval. APP_MAJOR_FAULT_RATE ---------------------------------- The number of major page faults per second that required a disk IO for processes in this group during the interval. APP_MEM_RES ---------------------------------- On Unix systems, this is the sum of the size (in MB) of resident memory for processes in this group that were alive at the end of the interval. This consists of text, data, stack, and shared memory regions. On HP-UX, since PROC_MEM_RES typically takes shared region references into account, this approximates the total resident (physical) memory consumed by all processes in this group. On all other Unix systems, this is the sum of the resident memory region sizes for all processes in this group. When the resident memory size for processes includes shared regions, such as shared memory and library text and data, the shared regions are counted multiple times in this sum. For example, if the application contains four processes that are attached to a 500MB shared memory region that is all resident in physical memory, then 2000MB is contributed towards the sum in this metric. As such, this metric can overestimate the resident memory being used by processes in this group when they share memory regions. Refer to the help text for PROC_MEM_RES for additional information. On Windows, this is the sum of the size (in MB) of the working sets for processes in this group during the interval. The working set counts memory pages referenced recently by the threads making up this group. Note that the size of the working set is often larger than the amount of pagefile space consumed. APP_MEM_UTIL ---------------------------------- On Unix systems, this is the approximate percentage of the system’s physical memory used as resident memory by processes in this group that were alive at the end of the interval. This metric summarizes process private and shared memory in each application. On Windows, this is an estimate of the percentage of the system’s physical memory allocated for working set memory by processes in this group during the interval. On HP-UX, this consists of text, data, stack, as well the process’ portion of shared memory regions (such as, shared libraries, text segments, and shared data). The sum of the shared region pages is typically divided by the number of references. APP_MEM_VIRT ---------------------------------- On Unix systems, this is the sum (in MB) of virtual memory for processes in this group that were alive at the end of the interval. This consists of text, data, stack, and shared memory regions. On HP-UX, since PROC_MEM_VIRT typically takes shared region references into account, this approximates the total virtual memory consumed by all processes in this group. On all other Unix systems, this is the sum of the virtual memory region sizes for all processes in this group. When the virtual memory size for processes includes shared regions, such as shared memory and library text and data, the shared regions are counted multiple times in this sum. For example, if the application contains four processes that are attached to a 500MB shared memory region, then 2000MB is reported in this metric. As such, this metric can overestimate the virtual memory being used by processes in this group when they share memory regions. On Windows, this is the sum (in MB) of paging file space used for all processes in this group during the interval. Groups of processes may have working set sizes (APP_MEM_RES) larger than the size of their pagefile space. APP_MEM_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on memory (waiting for virtual memory disk accesses to complete) during the interval. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_MINOR_FAULT ---------------------------------- The number of minor page faults satisfied in memory (a page was reclaimed from one of the free lists) for processes in this group during the interval. APP_MINOR_FAULT_RATE ---------------------------------- The number of minor page faults per second satisfied in memory (pages were reclaimed from one of the free lists) for processes in this group during the interval. APP_NAME ---------------------------------- The name of the application (up to 20 characters). This comes from the parm file where the applications are defined. The application called “other” captures all processes not aggregated into applications specifically defined in the parm file. In other words, if no applications are defined in the parm file, then all process data would be reflected in the “other” application. HP-UX If the parm file switch to log PRM group data, instead of application data, is in effect (indicated by APP_PRM_LOGGING_MODE = 1 and the log statement in the parm file includes application=prm), then this name is the PRM groupname defined in the HP-UX Process Resource Manager configuration file. WinNT The name of the Windows module for this application. APP_NETWORK_SUBSYSTEM_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on the network subsystem (waiting for their network activity to complete) during the interval. This is the sum of processes or kernel threads in the LAN, NFS, and RPC wait states. This does not include processes or kernel threads blocked on SOCKT (that is, socket) waits, as some processes or kernel threads sit idle in SOCKT waits for long periods. This is calculated as the accumulated time that all processes or kernel threads in this group spent blocked on (LAN + NFS + RPC) divided by the interval time. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_NUM ---------------------------------- The sequentially assigned number of this application or, on Solaris, the project ID when application grouping by project is enabled. APP_OTHER_IO_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on “other IO” during the interval. “Other IO” includes all IO directed at a device (connected to the local computer) which is not a terminal or LAN. Examples of “other IO” devices are local printers, tapes, instruments, and disks. Time waiting for character (raw) IO to disks is included in this measurement. Time waiting for file system buffered IO to disks will typically been seen as IO or CACHE wait. Time waiting for IO to NFS disks is reported as NFS wait. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_PRI ---------------------------------- On Unix systems, this is the average priority of the processes in this group during the interval. On Windows, this is the average base priority of the processes in this group during the interval. APP_PRI_STD_DEV ---------------------------------- The standard deviation of priorities of the processes in this group during the interval. This metric is available on HP-UX 10.20. APP_PRI_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on PRI (waiting for their priority to become high enough to get the CPU) during the interval. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_PRM_CPUCAP_MODE ---------------------------------- The PRM CPU Cap Mode state on this system: 0 = PRM is not installed or not configured. 1 = CPU Cap Mode is not enabled (PRM CPU entitlements are in effect) 2 = CPU Cap Mode is enabled (The PRM CPU entitlements behave as caps or limits) APP_PRM_CPU_ENTITLEMENT ---------------------------------- The PRM CPU entitlement for this PRM Group ID entry as defined in the PRM configuration file. APP_PRM_LOGGING_MODE ---------------------------------- The PRM logging mode will be 1 when PRM group data is being logged by the MeasureWare agent in place of parm file defined application data. By default, parm file application definitions are used and the PRM logging mode will be 0. A parm file setting read during MeasureWare Agent (scopeux) startup is used to override the default to log PRM group data. PRM group data logging is set in the parm file by specifying: application=prm in the log statement in versions of HP-UX MeasureWare which support this capability. See the MeasureWare Agent Release Notes file (located in /opt/perf/ReleaseNotes/Mwa) for more information. APP_PRM_MEM_AVAIL ---------------------------------- PRM available memory is the amount of physical memory less the amount of memory reserved for the kernel and system processes running in the PRM_SYS group 0. PRM available memory is a dynamic value that changes with system usage. APP_PRM_MEM_ENTITLEMENT ---------------------------------- The PRM MEM entitlement for this PRM Group ID entry as defined in the PRM configuration file. APP_PRM_MEM_STATE ---------------------------------- The PRM MEM state on this system: 0 = PRM is not installed or no memory specification 1 = reset (PRM is installed in reset condition or no memory specification) 2 = configured/disabled (The PRM memory scheduler is configured, but the standard HP-UX scheduler is in effect) 3 = enabled (The PRM memory scheduler is configured and in effect) APP_PRM_MEM_UPPERBOUND ---------------------------------- The PRM MEM upperbound for this PRM Group ID entry as defined in the PRM configuration file. APP_PRM_MEM_UTIL ---------------------------------- The percent of PRM memory used by processes (process private space plus a process’ portion of shared memory) within the PRM groups during the interval. PRM available memory is the amount of physical memory less the amount of memory reserved for the kernel and system processes running in the PRM_SYS group 0. PRM available memory is a dynamic value that changes with system usage. APP_PRM_STATE ---------------------------------- The PRM CPU state on this system: 0 = PRM is not installed 1 = reset (PRM is configured with only the system group. The standard HP-UX CPU scheduler is in effect) 2 = configured/disabled (the PRM CPU scheduler is configured, but the standard HP-UX scheduler is in effect) 3 = enabled (the PRM CPU scheduler is configured and in effect) APP_PROC_RUN_TIME ---------------------------------- The average run time for processes in this group that completed during the interval. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. APP_REVERSE_PRI ---------------------------------- The average priority of the processes in this group during the interval. Lower values for this metric always imply higher processing priority. The range is from 0 to 127. Since priority ranges can be customized on this OS, this metric provides a standardized way of interpreting priority that is consistent with other versions of Unix. See also the APP_PRI metric. This is derived from the PRI field of the ps command when the -c option is not used. APP_REV_PRI_STD_DEV ---------------------------------- The standard deviation of priorities of the processes in this group during the interval. Priorities are mapped into a traditional lower value implies higher priority scheme. APP_SAMPLE ---------------------------------- The number of samples of process data that have been averaged or accumulated during this sample. APP_SEM_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on semaphores (waiting for their semaphore operations to complete) during the interval. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_SLEEP_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on SLEEP (waiting to awaken from sleep system calls) during the interval. A process or kernel thread enters the SLEEP state by putting itself to sleep using system calls such as sleep, wait, pause, sigpause, sigsuspend, poll and select. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). The Application QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues, within the context of a specific application. The Application WAIT PCT metrics, which are also based on block states, represent the percentage of processes or kernel threads that were alive on the system within the context of a specific application. These values will vary greatly depending on the application. No direct comparison is reasonable with the Global Queue metrics since they represent the average number of all processes or kernel threads that were alive on the system. As such, the Application WAIT PCT metrics cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. APP_SUSPENDED_PROCS ---------------------------------- The average number of processes in this group which have been either marked as should be suspended (SGETOUT) or have been suspended (SSWAPPED) during the interval. Processes are suspended when the OS detects that memory thrashing is occurring. The scheduler looks for processes that have a high repage rate when compared with the number of major page faults the process has done and suspends these processes. If this metric is not zero, there is a memory bottleneck on the system. APP_TERM_IO_WAIT_PCT ---------------------------------- The percentage of time processes or kernel threads in this group were blocked on terminal IO (waiting for terminal IO to complete) during the interval. A percentage of time spent in a wait state is calculated as the accumulated time kernel threads belonging to processes in this group spent waiting in this state, divided by accumulated alive time of kernel threads belonging to processes in this group during the interval. For example, assume an application has 20 kernel threads. During the interval, ten kernel threads slept the entire time, while ten kernel threads waited on terminal input. As a result, the application wait percent values would be 50% for SLEEP and 50% for TERM (that is, terminal IO). This metric is available on HP-UX 10.20. BLANK ---------------------------------- An empty field used for spacing reports. For example, this field can be used to create a blank column in a spreadsheet that may be used to sum several items. BYCPU_CPU_CLOCK ---------------------------------- The clock speed of the CPU in the current slot. The clock speed is in MHz for the selected CPU. The Linux kernel currently doesn’t provide any metadata information for disabled CPUs. This means that there is no way to find out types, speeds, as well as hardware IDs or any other information that is used to determine the number of cores, the number of threads, the HyperThreading state, etc... If the agent (or Glance) is started while some of the CPUs are disabled, some of these metrics will be “na”, some will be based on what is visible at startup time. All information will be updated if/when additional CPUs are enabled and information about them becomes available. The configuration counts will remain at the highest discovered level (i.e. if CPUs are then disabled, the maximum number of CPUs/cores/etc... will remain at the highest observed level). It is recommended that the agent be started with all CPUs enabled. On Linux, this value is always rounded up to the next MHz. BYCPU_CPU_PHYSC ---------------------------------- The total processing units of physical CPU consumed by this logical CPU during this interval. BYCPU_CPU_SYS_MODE_TIME ---------------------------------- The time, in seconds, that this CPU (or logical processor) was in system mode during the interval. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. BYCPU_CPU_SYS_MODE_UTIL ---------------------------------- The percentage of time that this CPU (or logical processor) was in system mode during the interval. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. BYCPU_CPU_TOTAL_TIME ---------------------------------- The total time, in seconds, that this CPU (or logical processor) was not idle during the interval. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. BYCPU_CPU_TOTAL_UTIL ---------------------------------- The percentage of time that this CPU (or logical processor) was not idle during the interval. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. BYCPU_CPU_USER_MODE_TIME ---------------------------------- The time, in seconds, during the interval that this CPU (or logical processor) was in user mode. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. BYCPU_CPU_USER_MODE_UTIL ---------------------------------- The percentage of time that this CPU (or logical processor) was in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. BYCPU_CSWITCH_RATE ---------------------------------- The average number of context switches per second for this CPU during the interval. On HP-UX, this includes context switches that result in the execution of a different process and those caused by a process stopping, then resuming, with no other process running in the meantime. BYCPU_ID ---------------------------------- The ID number of this CPU. On some Unix systems, such as SUN, CPUs are not sequentially numbered. BYCPU_INTERRUPT ---------------------------------- The number of device interrupts for this CPU during the interval. On HP-UX, a value of “na” is displayed on a system with multiple CPUs. BYCPU_INTERRUPT_RATE ---------------------------------- The average number of device interrupts per second for this CPU during the interval. On HP-UX, a value of “na” is displayed on a system with multiple CPUs. BYCPU_STATE ---------------------------------- A text string indicating the current state of a processor. On HP-UX, this is either “Enabled”, “Disabled” or “Unknown”. On AIX, this is either “Idle/Offline” or “Online”. On all other systems, this is either “Offline”, “Online” or “Unknown”. BYDSK_AVG_QUEUE_TIME ---------------------------------- The average time, in milliseconds, that a disk request spent waiting in the queue during the interval. For example, a value of 1.14 would indicate that disk requests during the last interval spent on average slightly longer than one-thousandths of a second wating in the queue of this device. BYDSK_AVG_READ_QUEUE_TIME ---------------------------------- The average time, in milliseconds, that a disk read request spent waiting in the queue during the interval. For example, a value of 1.14 would indicate that disk read requests during the last interval spent on average slightly longer than one-thousandths of a second waiting in the queue of this device. BYDSK_AVG_READ_SERVICE_TIME ---------------------------------- The average time, in milliseconds, that this disk device spent processing each disk read request during the interval. For example, a value of 5.14 would indicate that disk read requests during the last interval took on average slightly longer than five one-thousandths of a second to complete for this device. This is a measure of the speed of the disk, because slower disk devices typically show a larger average read service time. Average read service time is also dependent on factors such as the distribution of I/O requests over the interval and their locality. It can also be influenced by disk driver and controller features such as I/O merging and command queueing. Note that this write service time is measured from the perspective of the kernel, not the disk device itself. For example, if a disk device can find the requested data in its cache, the average service time could be quicker than the speed of the physical disk hardware. This metric can be used to help determine which disk devices are taking more time than usual to process read requests. BYDSK_AVG_REQUEST_QUEUE ---------------------------------- The average number of IO requests that were in the wait and service queues for this disk device over the cumulative collection time. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. For example, if 4 intervals have passed with average queue lengths of 0, 2, 0, and 6, then the average number of IO requests over all intervals would be 2. Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. BYDSK_AVG_SERVICE_TIME ---------------------------------- The average time, in milliseconds, that this disk device spent processing each disk request during the interval. For example, a value of 5.14 would indicate that disk requests during the last interval took on average slightly longer than five one-thousandths of a second to complete for this device. Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. This is a measure of the speed of the disk, because slower disk devices typically show a larger average service time. Average service time is also dependent on factors such as the distribution of I/O requests over the interval and their locality. It can also be influenced by disk driver and controller features such as I/O merging and command queueing. Note that this service time is measured from the perspective of the kernel, not the disk device itself. For example, if a disk device can find the requested data in its cache, the average service time could be quicker than the speed of the physical disk hardware. This metric can be used to help determine which disk devices are taking more time than usual to process requests. BYDSK_AVG_WRITE_QUEUE_TIME ---------------------------------- The average time, in milliseconds, that a disk write request spent waiting in the queue during the interval. For example, a value of 1.14 would indicate that disk write requests during the last interval spent on average slightly longer than one-thousandths of a second waiting in the queue of this device. BYDSK_AVG_WRITE_SERVICE_TIME ---------------------------------- The average time, in milliseconds, that this disk device spent processing each disk write request during the interval. For example, a value of 5.14 would indicate that disk write requests during the last interval took on average slightly longer than five one-thousandths of a second to complete for this device. This is a measure of the speed of the disk, because slower disk devices typically show a larger average write service time. Average write service time is also dependent on factors such as the distribution of I/O requests over the interval and their locality. It can also be influenced by disk driver and controller features such as I/O merging and command queueing. Note that this write service time is measured from the perspective of the kernel, not the disk device itself. For example, if a disk device can find the requested data in its cache, the average service time could be quicker than the speed of the physical disk hardware. This metric can be used to help determine which disk devices are taking more time than usual to process write requests. BYDSK_BUSY_TIME ---------------------------------- The time, in seconds, that this disk device was busy transferring data during the interval. On HP-UX, this is the time, in seconds, during the interval that the disk device had IO in progress from the point of view of the Operating System. In other words, the time, in seconds, the disk was busy servicing requests for this device. BYDSK_CURR_QUEUE_LENGTH ---------------------------------- The average number of physical IO requests that were in the wait and service queues for this disk device during the interval. Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. BYDSK_DEVNAME ---------------------------------- The name of this disk device. On HP-UX, the name identifying the specific disk spindle is the hardware path which specifies the address of the hardware components leading to the disk device. On SUN, these names are the same disk names displayed by “iostat”. On AIX, this is the path name string of this disk device. This is the fsname parameter in the mount(1M) command. If more than one file system is contained on a device (that is, the device is partitioned), this is indicated by an asterisk (“*”) at the end of the path name. On OSF1, this is the path name string of this disk device. This is the file- system parameter in the mount(1M) command. On Windows, this is the unit number of this disk device. BYDSK_DIRNAME ---------------------------------- The name of the file system directory mounted on this disk device. If more than one file system is mounted on this device, “Multiple FS” is seen. BYDSK_DISKNAME ---------------------------------- The device special file(DSF) representing this disk. This metric only gives the last component in the DSF path. On HP-UX 11iv1 and 11iv2, the DSF is of the form /dev/dsk/c#t#d# and hence value of DISKNAME metric will be “c#t#d#” On HP-UX 11iv3, this metric gives the path independent DSF name. So value of DISKNAME metric will be “disk#”. See intro(7) for more details. BYDSK_FS_READ ---------------------------------- The number of physical file system reads from this disk device during the interval. BYDSK_FS_READ_RATE ---------------------------------- The number of physical file system reads per second from this disk device during the interval. BYDSK_FS_WRITE ---------------------------------- The number of physical file system writes to this disk device during the interval. BYDSK_FS_WRITE_RATE ---------------------------------- The number of physical file system writes per second to this disk device during the interval. BYDSK_HISTOGRAM ---------------------------------- A bar chart of the disk IO. HP-UX Shows breakout of the disk IO. Disk IO Rate = BYDSK_FS_READ_RATE + BYDSK_FS_WRITE_RATE + BYDSK_RAW_READ_RATE + BYDSK_RAW_WRITE_RATE + BYDSK_VM_IO_RATE + BYDSK_SYSTEM_IO_RATE ASCII and binary files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of Disk IO on a character mode terminal display. AIX NCR Sinix Shows a breakout of the disk IO. Disk IO Rate = BYDSK_PHYS_READ_RATE + BYDSK_PHYS_WRITE_RATE ASCII and binary files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of Disk IO on a character mode terminal display. SunOS WinNT Shows a breakout of the disk IO. Disk IO Rate = BYDSK_PHYS_READ_RATE + BYDSK_PHYS_WRITE_RATE ASCII and binary files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of Disk IO on a character mode terminal display. BYDSK_ID ---------------------------------- The ID of the current disk device. BYDSK_LOGL_READ ---------------------------------- The number of logical reads for this disk device during the interval. On HP-UX, the logical IO rates by disk device cannot be obtained in a multi- disk LVM configuration because there is no reasonable means of tying logical IO transactions to physical spindles spanned on the logical volume. Therefore, if you have a multi-disk LVM configuration, you always see “na” for this metric. BYDSK_LOGL_READ_RATE ---------------------------------- The number of logical reads per second for this disk device during the interval. On HP-UX, the logical IO rates by disk device cannot be obtained in a multi- disk LVM configuration because there is no reasonable means of tying logical IO transactions to physical spindles spanned on the logical volume. Therefore, if you have a multi-disk LVM configuration, you always see “na” for this metric. BYDSK_LOGL_WRITE ---------------------------------- The number of logical writes for this disk device during the interval. On HP-UX, the logical IO rates by disk device cannot be obtained in a multi- disk LVM configuration because there is no reasonable means of tying logical IO transactions to physical spindles spanned on the logical volume. Therefore, if you have a multi-disk LVM configuration, you always see “na” for this metric. BYDSK_LOGL_WRITE_RATE ---------------------------------- The number of logical writes per second for this disk device during the interval. On HP-UX, the logical IO rates by disk device cannot be obtained in a multi- disk LVM configuration because there is no reasonable means of tying logical IO transactions to physical spindles spanned on the logical volume. Therefore, if you have a multi-disk LVM configuration, you always see “na” for this metric. BYDSK_PHYS_BYTE ---------------------------------- The number of KBs of physical IOs transferred to or from this disk device during the interval. On Unix systems, all types of physical disk IOs are counted, including file system, virtual memory, and raw IO. BYDSK_PHYS_BYTE_RATE ---------------------------------- The average KBs per second transferred to or from this disk device during the interval. On Unix systems, all types of physical disk IOs are counted, including file system, virtual memory, and raw IO. BYDSK_PHYS_IO ---------------------------------- The number of physical IOs for this disk device during the interval. On Unix systems, all types of physical disk IOs are counted, including file system, virtual memory, and raw reads. BYDSK_PHYS_IO_RATE ---------------------------------- The average number of physical IO requests per second for this disk device during the interval. On Unix systems, all types of physical disk IOs are counted, including file system IO, virtual memory and raw IO. BYDSK_PHYS_READ ---------------------------------- The number of physical reads for this disk device during the interval. On Unix systems, all types of physical disk reads are counted, including file system, virtual memory, and raw reads. On AIX, this is an estimated value based on the ratio of read bytes to total bytes transferred. The actual number of reads is not tracked by the kernel. This is calculated as BYDSK_PHYS_READ = BYDSK_PHYS_IO * (BYDSK_PHYS_READ_BYTE / BYDSK_PHYS_IO_BYTE) BYDSK_PHYS_READ_BYTE ---------------------------------- The KBs transferred from this disk device during the interval. On Unix systems, all types of physical disk reads are counted, including file system, virtual memory, and raw IO. BYDSK_PHYS_READ_BYTE_RATE ---------------------------------- The average KBs per second transferred from this disk device during the interval. On Unix systems, all types of physical disk reads are counted, including file system, virtual memory, and raw IO. BYDSK_PHYS_READ_RATE ---------------------------------- The average number of physical reads per second for this disk device during the interval. On Unix systems, all types of physical disk reads are counted, including file system, virtual memory, and raw reads. On AIX, this is an estimated value based on the ratio of read bytes to total bytes transferred. The actual number of reads is not tracked by the kernel. This is calculated as BYDSK_PHYS_READ_RATE = BYDSK_PHYS_IO_RATE * (BYDSK_PHYS_READ_BYTE / BYDSK_PHYS_IO_BYTE) BYDSK_PHYS_WRITE ---------------------------------- The number of physical writes for this disk device during the interval. On Unix systems, all types of physical disk writes are counted, including file system IO, virtual memory IO, and raw writes. On AIX, this is an estimated value based on the ratio of write bytes to total bytes transferred because the actual number of writes is not tracked by the kernel. This is calculated as BYDSK_PHYS_WRITE = BYDSK_PHYS_IO * (BYDSK_PHYS_WRITE_BYTE / BYDSK_PHYS_IO_BYTE) BYDSK_PHYS_WRITE_BYTE ---------------------------------- The KBs transferred to this disk device during the interval. On Unix systems, all types of physical disk writes are counted, including file system, virtual memory, and raw IO. BYDSK_PHYS_WRITE_BYTE_RATE ---------------------------------- The average KBs per second transferred to this disk device during the interval. On Unix systems, all types of physical disk writes are counted, including file system, virtual memory, and raw IO. BYDSK_PHYS_WRITE_RATE ---------------------------------- The average number of physical writes per second for this disk device during the interval. On Unix systems, all types of physical disk writes are counted, including file system IO, virtual memory IO, and raw writes. On AIX, this is an estimated value based on the ratio of write bytes to total bytes transferred. The actual number of writes is not tracked by the kernel. This is calculated as BYDSK_PHYS_WRITE_RATE = BYDSK_PHYS_IO_RATE * (BYDSK_PHYS_WRITE_BYTE / BYDSK_PHYS_IO_BYTE) BYDSK_RAW_READ ---------------------------------- The number of physical raw reads made from this disk device during the interval. BYDSK_RAW_READ_RATE ---------------------------------- The number of raw reads per second made from this disk device during the interval. BYDSK_RAW_WRITE ---------------------------------- The number of physical raw writes made to this disk device during the interval. BYDSK_RAW_WRITE_RATE ---------------------------------- The number of raw writes per second made to this disk device during the interval. BYDSK_REQUEST_QUEUE ---------------------------------- The average number of IO requests that were in the wait queue for this disk device during the interval. These requests are the physical requests (as opposed to logical IO requests). Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. BYDSK_SYSTEM_IO ---------------------------------- The number of physical system reads or writes to this disk device during the interval. BYDSK_SYSTEM_IO_RATE ---------------------------------- The number of physical system reads or writes per second to this disk device during the interval. BYDSK_UTIL ---------------------------------- On HP-UX, this is the percentage of the time during the interval that the disk device had IO in progress from the point of view of the Operating System. In other words, the utilization or percentage of time busy servicing requests for this device. On the non-HP-UX systems, this is the percentage of the time that this disk device was busy transferring data during the interval. Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. This is a measure of the ability of the IO path to meet the transfer demands being placed on it. Slower disk devices may show a higher utilization with lower IO rates than faster disk devices such as disk arrays. A value of greater than 50% utilization over time may indicate that this device or its IO path is a bottleneck, and the access pattern of the workload, database, or files may need reorganizing for better balance of disk IO load. BYDSK_VM_IO ---------------------------------- The number of virtual memory IOs to this disk device during the interval. BYDSK_VM_IO_RATE ---------------------------------- The number of virtual memory IOs per second to this disk device during the interval. BYDSK_VM_READ_RATE ---------------------------------- The number of virtual memory reads per second from this disk device during the interval. BYDSK_VM_WRITE_RATE ---------------------------------- The number of virtual memory writes per second to this disk device during the interval. BYLS_BOOT_TIME ---------------------------------- On vMA, for a host and logical system the metric is the date and time when the system was last booted. The value is NA for resource pool. Note that this date is obtained from the VMware API as an already formatted string and may not conform to the expected localization. BYLS_CLUSTER_NAME ---------------------------------- On vMA, for a host and resource pool it is the name of the cluster to which the host belongs to when it is managed by virtual centre. For a logical system, the value is NA. BYLS_CPU_CLOCK ---------------------------------- On vMA, for a host and logical system, it is the clock speed of the CPUs in MHz if all of the processors have the same clock speed. For a resource pool the value is NA. BYLS_CPU_CYCLE_ENTL_MAX ---------------------------------- On vMA, for a host, logical system and resource pool this value indicates the maximum processor capacity, in MHz, configured for the entity. If the maximum processor capacity is not configured for the entity, a value of “-3” will be displayed in PA and “ul”( unlimited ) in other clients. On HPUX, the maximum processor capacity, in MHz, configured for this logical system. BYLS_CPU_CYCLE_ENTL_MIN ---------------------------------- On vMA, for a host, logical system and resource pool this value indicates the minimum processor capacity, in MHz, configured for the entity. On HPUX, the minimum processor capacity, in MHz, configured for this logical system. BYLS_CPU_CYCLE_TOTAL_USED ---------------------------------- On vMA, for host, resource pool and logical system, it is the total time the physical CPUs were utilized during the interval, represented in cpu cycles. BYLS_CPU_ENTL ---------------------------------- The entitlement or the CPU units granted to a logical system at startup. On AIX SPLPAR, this metric indicates the cpu units allocated by Hypervisor to a logical system at the time of starting. This metric is equivalent to “Entitled Capacity” field of ‘lparstat -i’ command. For WPARs, it is the maximum units of CPU that a WPAR can have when there is a contention for CPU. WPAR shares CPU units of its global environment. BYLS_CPU_ENTL_EMIN ---------------------------------- On vMA, for host, logical system and resource pool the value is “na”. BYLS_CPU_ENTL_MAX ---------------------------------- The maximum CPU units configured for a logical system. On HP-UX HPVM, this metric indicates the maximum percentage of physical CPU that a virtual CPU of this logical system can get. On AIX SPLPAR, this metric is equivalent to “Maximum Capacity” field of ‘lparstat -i’ command. For WPARs, it is the maximum percentage of CPU that a WPAR can have even if there is no contention for CPU. WPAR shares CPU units of its global environment. On Hyper-V host, for Root partition, this metric is NA. On vMA, for a host, the metric is equivalent to total number of cores on the host. For a resource pool and a logical system, this metrics indicates the maximum CPU units configured for it. BYLS_CPU_ENTL_MIN ---------------------------------- The minimum CPU units configured for this logical system. On HP-UX HPVM, this metric indicates the minimum percentage of physical CPU that a virtual CPU of this logical system is guaranteed. On AIX SPLPAR, this metric is equivalent to “Minimum Capacity” field of ‘lparstat -i’ command. For WPARs, it is the minimum CPU share assigned to a WPAR that is guaranteed. WPAR shares CPU units of its global environment. On Hyper-V host, for Root partition, this metric is NA. On vMA, for a host, the metric is equivalent to total number of cores on the host. For a resource pool and a logical system, this metrics indicates the guranteed minimum CPU units configured for it. On Solaris Zones, this metrics indicates the configured minimum CPU percentage reserved for a logical system. For Solaris Zones, this metric is calculated as: BYLS_CPU_ENTL_MIN = ( BYLS_CPU_SHARES_PRIO / Pool-Cpu-Shares ) where, Pool-Cpu-Shares is the total CPU shares available with CPU pool the zone is associated with. Pool-Cpu-Shares is addition of BYLS_CPU_SHARES_PRIO values for all active zones associated with this pool. BYLS_CPU_ENTL_UTIL ---------------------------------- Percentage of entitled processing units (guaranteed processing units allocated to this logical system) consumed by the logical system. On a HP-UX HPVM host the metric indicates the logical system’s CPU utilization with respect to minimum CPU entitlement. On HP-UX HPVM host, this metric is calculated as: BYLS_CPU_ENTL_UTIL = (BYLS_CPU_PHYSC / (BYLS_CPU_ENTL_MIN * BYLS_NUM_CPU)) * 100 On AIX, this metric is calculated as: BYLS_CPU_ENTL_UTIL = (BYLS_CPU_PHYSC / BYLS_CPU_ENTL) * 100 On WPAR, this metric is calculated as: BYLS_CPU_ENTL_UTIL = (BYLS_CPU_PHYSC / BYLS_CPU_ENTL_MAX) * 100 This metric matches “%Resc” of topas command (inside WPAR) On Solaris Zones, the metric indicates the logical system’s CPU utilization with respect to minimum CPU entitlement. This metric is calculated as: BYLS_CPU_ENTL_UTIL = (BYLS_CPU_TOTAL_UTIL / BYLS_CPU_SHARES_PRIO) * 100 If a Solaris zone is not assigned a CPU entitlement value then a CPU entitlement value is derived for this zone based on total CPU entitlement associated with the CPU pool this zone is attached to. On Hyper-V host, for Root partition, this metric is NA. On vMA, for a host the value is same as BYLS_CPU_PHYS_TOTAL_UTIL while for logical system and resource pool the value is the percentage of processing units consumed w.r.t minimum CPU entitlement. BYLS_CPU_MT_ENABLED ---------------------------------- Indicates whether the CPU hardware threads are enabled(“On”) or not(“Off”) for a logical system. For AIX wpars, the metric will be “na”. On vMA, this metric indicates whether the CPU hardware threads are enabled or not for a host while for a resource pool and a logical system the value is not available(“na”). BYLS_CPU_PHYSC ---------------------------------- This metric indicates the number of CPU units utilized by the logical system. On an Uncapped logical system, this value will be equal to the CPU units capacity used by the logical system during the interval. This can be more than the value entitled for a logical system. BYLS_CPU_PHYS_IDLE_MODE_UTIL ---------------------------------- The percentage of time the physical CPUs were in idle state for the logical system during the interval. On AIX LPAR, this value is equivalent to “%idle” field reported by the “lparstat” command. BYLS_CPU_PHYS_READY_UTIL ---------------------------------- On vMA, for a logical system it is the percentage of time, during the interval, that the CPU was in ready state. For a host and resource pool the value is NA. BYLS_CPU_PHYS_SYS_MODE_UTIL ---------------------------------- The percentage of time the physical CPUs were in system mode (kernel mode) for the logical system during the interval. On AIX LPAR, this value is equivalent to “%sys” field reported by the “lparstat” command. On Hyper-V host, this metric indicates the percentage of time spent in Hypervisor code. On vMA, the metric indicates the percentage of time the physical CPUs were in system mode during the interval for the host or logical system. On vMA, for a resource pool, this metric is “na”. BYLS_CPU_PHYS_TOTAL_TIME ---------------------------------- Total time in seconds, spent by the logical system on the physical CPUs. On HPUX, this information is updated internally every 10 seconds so it may take that long for these values to be updated in PA/Glance. On vMA, the value indicates the time spent in seconds on the physical CPU. by logical system or host or resource pool, BYLS_CPU_PHYS_TOTAL_UTIL ---------------------------------- Percentage of total time the physical CPUs were utilized by this logical system during the interval. On HPUX, this information is updated internally every 10 seconds so it may take that long for these values to be updated in PA/Glance. On Solaris, this metric is calculated with respect to the available active physical CPUs on the system. On AIX, this metric is equivalent to sum of BYLS_CPU_PHYS_USER_MODE_UTIL and BYLS_CPU_PHYS_SYS_MODE_UTIL. For AIX lpars, the metric is calculated with respect to the available physical CPUs in the pool to which this LPAR belongs to. For AIX wpars, the metric is calculated with respect to the available physical CPUs in the resource set or Global Environment. On vMA, the value indicates percentage of total time the physical CPUs were utilized by logical system or host or resource pool, BYLS_CPU_PHYS_USER_MODE_UTIL ---------------------------------- The percentage of time the physical CPUs were in user mode for the logical system during the interval. On AIX LPAR, this value is equivalent to “%user” field reported by the “lparstat” command. On Hyper-V host, this metric indicates the percentage of time spent in guest code. On vMA, the metrics indicates the percentage of time the physical CPUs were in user mode during the interval for the host or logical system. On vMA, for a resource pool, this metric is “na”. BYLS_CPU_PHYS_WAIT_MODE_UTIL ---------------------------------- The percentage of time the physical CPUs were in wait mode for the logical system during the interval. On AIX LPAR, this value is equivalent to “%wait” field reported by the “lparstat” command. BYLS_CPU_PHYS_WAIT_UTIL ---------------------------------- On vMA, for a logical system it is the percentage of time, during the interval, that the virtual CPU was waiting for the IOs to complete. For a host and resource pool the value is NA. BYLS_CPU_SHARES_PRIO ---------------------------------- This metric indicates the weightage/priority assigned to a Uncapped logical system. This value determines the minimum share of unutilized processing units that this logical system can utilize. The value of this metric will be “-3” in PA and “ul” in other clients if cpu shares value is ‘Unlimited’ for a logical system. On AIX SPLPAR this value is dependent on the available processing units in the pool and can range from 0 to 255. For WPARs, this metric represents how much of a particular resource a WPAR receives relative to the other WPARs. On vMA, for logical system and resource pool this value can range from 1 to 1000000 while for host the value is NA. On Solaris Zones, this metric sets a limit on the number of fair share scheduler (FSS) CPU shares for a zone. On Hyper-V host, this metric specifies allocation of CPU resources when more than one virtual machine is running and competing for resources. This value can range from 0 to 10000. For Root partition, this metric is NA. BYLS_CPU_SYS_MODE_UTIL ---------------------------------- On vMA, for a host and a logical system, this metric indicates the percentage of time the CPU was in system mode. On vMA, for a resource pool, this metric is “na”. during the interval. BYLS_CPU_TOTAL_UTIL ---------------------------------- Percentage of total time the logical CPUs were not idle during this interval. This metric is calculated against the number of logical CPUs configured for this logical system. For AIX wpars, the metric represents the percentage of time the physical CPUs were not idle during this interval. BYLS_CPU_UNRESERVED ---------------------------------- On vMA, for host, it is the number of CPU cycles that are available for creating a new logical system. For a logical system and resource pool the value is NA. BYLS_CPU_USER_MODE_UTIL ---------------------------------- On vMA, for a host and a logical system, this metric indicates the percentage of time the CPU was in user mode during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DATACENTER_NAME ---------------------------------- On vMA, for a host it is the name of the datacenter to which the host belongs to when it is managed by virtual center. To uniquely identify datacenter in a virtual center, datacenter name is appended with the folder names in bottom up order. For a logical system and resource pool, the value is NA. BYLS_DISK_PHYS_BYTE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of KBs transferred to and from disks during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_BYTE_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the average number of KBs per second at which data was transferred to and from disks during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_READ ---------------------------------- On vMA, for a host and a logical system this metric indicates the number of physical reads during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_READ_BYTE_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the average number of KBs transferred from the disk per second during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_READ_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of physical reads per second during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_WRITE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of physical writes during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_WRITE_BYTE_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the average number of KBs transferred to the disk per second during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_PHYS_WRITE_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of physical writes per second during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_DISK_UTIL ---------------------------------- On vMA, for a host, it is the average percentage of time during the interval (average utilization) that all the disks had IO in progress. For logical system and resource pool the value is NA. BYLS_DISK_UTIL_PEAK ---------------------------------- On vMA, for a host, it is the utilization of the busiest disk during the interval. For a logical system and resource pool the value is NA. BYLS_DISPLAY_NAME ---------------------------------- On vMA, this metric indicates the name of the host or logical system or resource pool. On HPVM, this metric indicates the Virtual Machine name of the logical systemand is equivalent to “Virtual Machine Name” field of ‘hpvmstatus’ command. On AIX the value is as returned by the command “uname -n” (that is, the string returned from the “hostname” program). On Solaris Zones, this metric indicates the zone name and is equivalent to ‘NAME’ field of ‘zoneadm list -vc’ command. On Hyper-V host, this metric indicates the Virtual Machine name of the logical systemand is equivalent to the Name displayed in Hyper-V Manager. For Root partition, the value is always “Root”. BYLS_HYPCALL ---------------------------------- The number of Hypervisor calls made by a logical system during the interval. Higher number of calls will result in higher BYLS_CPU_PHYS_SYS_MODE_UTIL, BYLS_CPU_PHYS_WAIT_MODE_UTIL, GBL_CPU_SYS_MODE_UTIL and GBL_CPU_WAIT_UTIL. For AIX wpars, the metric will be “na”. BYLS_HYP_UTIL ---------------------------------- Percentage of time spent in Hypervisor by a logical system during the interval. Higher utilization of hypervisor will result in higher BYLS_CPU_PHYS_SYS_MODE_UTIL, BYLS_CPU_PHYS_WAIT_MODE_UTIL, GBL_CPU_SYS_MODE_UTIL and GBL_CPU_WAIT_UTIL. For AIX wpars, the metric will be “na”. BYLS_IP_ADDRESS ---------------------------------- This metric indicates IP Address of the particular logical system. On vMA, this metric indicates the IP Address for a host and a logical system while for a resource pool the value is NA. BYLS_LS_HOSTNAME ---------------------------------- This is the DNS registered name of the system. On Hyper-V host, this metric is NA if the logical system is not active or Hyper-V Integration Components are not installed on it. On vMA, for a host and logical system the metric is the Fully Qualified Domain Name, while for resource pool the value is NA. BYLS_LS_HOST_HOSTNAME ---------------------------------- On vMA, for logical system and resource pool, it is the FQDN of the host on which they are hosted. For a host, the value is NA. BYLS_LS_ID ---------------------------------- An unique identifier of the logical system. On HPVM, this metric is a numeric id and is equivalent to “VM # “ field of ‘hpvmstatus’ command. On AIX LPAR, this metric indicates partition number and is equivalent to “Partition Number” field of ‘lparstat -i’ command. For aix wpar, this metric represents the partition number and is equivalent to “uname -W” from inside wpar. On Solaris Zones, this metric indicates the zone id and is equivalent to ‘ID’ field of ‘zoneadm list -vc’ command. On Hyper-V host, this metric indicates the PID of the process corresponding to this logical system. For Root partition, this metric is NA. On vMA, this metric is a unique identifier for a host, resource pool and a logical system. The value of this metric may change for an instance across collection intervals. BYLS_LS_MODE ---------------------------------- This metric indicates whether the CPU entitlement for the logical system is Capped or Uncapped. AIX The value “Uncapped” indicates that the logical system can utilize idle cycles from the shared processor pool of CPUs beyond its CPU entitlement. On AIX SPLPAR, this metric is same as “Mode” field of ‘lparstat -i’ command. For WPARs, this metric is always CAPPED. On vMA, the value is Capped for a host and Uncapped for a logical system. For resource pool, the value is Uncapped or Capped depending on whether the reservation is expandable or not for it. On Solaris Zones, this metric is “Capped” when the zone is assigned CPU shares and is attached to a valid CPU pool. BYLS_LS_NAME ---------------------------------- This is the name of the computer. On HPVM, this metric indicates the Virtual Machine name of the logical systemand is equivalent to “Virtual Machine Name” field of ‘hpvmstatus’ command. On AIX the value is as returned by the command “uname -n” (that is, the string returned from the “hostname” program). On vMA, this metric is a unique identifier for host, resource pool and a logical system. The value of this metric remains the same, for an instance, across collection intervals. On Solaris Zones, this metric indicates the zone name and is equivalent to ‘NAME’ field of ‘zoneadm list -vc’ command. On Hyper-V host, this metric indicates the name of the XML file which has configuration information of the logical system. This file will be present under the logical system’s installation directory indicated by BYLS_LS_PATH. For Root partition, the value is always “Root”. BYLS_LS_OSTYPE ---------------------------------- The Guest OS this logical system is hosting. On HPVM, the metric can have following values: HP-UX Linux Windows OpenVMS Other Unknown On Hyper-V host, the metric can have following values: Windows Other On Hyper-V host, this metric is NA if the logical system is not active or Hyper-V Integration Components are not installed on it. On vMA, the metric can have the following values for host and logical system: ESX/ESXi followed by version or ESX-Serv (applicable only for a host) Linux Windows Solaris Unknown The value is NA for resource pool BYLS_LS_PARENT_TYPE ---------------------------------- On vMA, the metric indicates the type of parent entity. The value is HOST if the parent is a host, RESPOOL if the parent is resource pool. For a host, the value is NA. BYLS_LS_PARENT_UUID ---------------------------------- On vMA, the metric indicates the UUID appended to display_name of the parent entity. For logical system and resource pool this metric could indicate the UUID appended to display_name of a host or resource pool as they can be created under a host or resource pool. For a host, the value is NA. BYLS_LS_PATH ---------------------------------- This metric indicates the installation path for the logical system. On Hyper-V host, for Root partition, this metric is NA. On vMA, the metric indicates the installation path for host or logical system. On vMA, for a resource pool and a host, this metric is “na”. BYLS_LS_PROC_ID ---------------------------------- On HPVM host and Hyper-V host, each VM is manifested as a process. These processes have the executable name hpvmapp for HPVM and vmwp.exe for Hyper-V host. This metric will have the PID of the process corresponding to this logical system. On HPVM, typically hpvmapp has the option -d whose argument is the name of the VM. On Hyper-V host, for Root partition, this metric is NA. BYLS_LS_ROLE ---------------------------------- On vMA, for a host the metric is HOST. For a logical system the value is GUEST and for a resource pool the value is RESPOOL. For logical system which is a vMA, the value is PROXY. BYLS_LS_SHARED ---------------------------------- This metric indicates whether the physical CPUs are dedicated to this logical system or shared. On HPUX HPVM, and Hyper-V host,this metric is always “Shared”. On vMA, the value is “Dedicated” for host, and “Shared” for logical system and resource pool. On AIX SPLPAR, this metric is equivalent to “Type” field of ‘lparstat -i’ command. For AIX wpars,this metric will be always “Shared”. On Solaris Zones, this metric is “Dedicated” when this zone is attached to a CPU pool not shared by any other zone. BYLS_LS_STATE ---------------------------------- The state of this logical system. On HPVM, the logical systems can have one of the following states: Unknown Other invalid Up Down Boot Crash Shutdown Hung On vMA, this metric can have one of the following states for a host: on off unknown The values for a logical system can be one of the following: on off suspended unknown The value is NA for resource pool. On Solaris Zones, the logical systems can have one of the following states: configured incomplete installed ready running shutting down mounted On AIX lpars, the logical system will be always active. On AIX wpars, the logical systems can have one of the following states: Broken Transitional Defined Active Loaded Paused Frozen Error A logical system on a Hyper-V host can have the following states: unknown enabled disabled paused suspended starting snapshtng migrating saving stopping deleted pausing resuming BYLS_LS_TYPE ---------------------------------- The type of this logical system. On AIX, the logical systems can have one of the following types: lpar sys wpar app wpar On vMA, the value of this metric is “VMware”. BYLS_LS_UUID ---------------------------------- UUID of this logical system. This Id uniquely identifies this logical system across multiple hosts. On Hyper-V host, for Root partition, this metric is NA. On vMA, for a logical system or a host, the value indicates the UUID appended to display_name of the system. For a resource pool the value is hostname of the host where resource pool is hosted followed by the unique id of resource pool. BYLS_MACHINE_MODEL ---------------------------------- On vMA, for a host, it is the CPU model of the host system. For a logical system and resource pool the value is “na”. BYLS_MEM_ACTIVE ---------------------------------- On vMA, for a logical system it is the amount of memory, that is actively used. For a host and resource pool the value is NA. BYLS_MEM_AVAIL ---------------------------------- On vMA, for a host, the amount of physical available memory in the host system (in MBs unless otherwise specified). For a logical system and resource pool the value is NA. BYLS_MEM_BALLOON_USED ---------------------------------- On vMA, for logical system, it is the amount of memory held by memory control for ballooning. The value is represented in KB. For a host and resource pool the value is NA. BYLS_MEM_BALLOON_UTIL ---------------------------------- On vMA, for logical system, it is the amount of memory held by memory control for ballooning. It is represented as a percentage of BYLS_MEM_ENTL. For a host, and resource pool the value is NA. BYLS_MEM_ENTL ---------------------------------- The entitled memory configured for this logical system (in MB). On Hyper-V host, for Root partition, this metric is NA. On vMA, for host the value is the physical memory available in the system and for logical system this metric indicates the minimum memory configured while for resource pool the value is NA. BYLS_MEM_ENTL_MAX ---------------------------------- The maximum amount of memory configured for a logical system, in MB. The value of this metric will be “-3” in PA and “ul” in other clients if entitlement is ‘Unlimited’ for a logical system. On AIX LPARs, this metric will be “na”. On vMA, this metric indicates the maximum amount of memory configured for a resource pool or a logical system. For a host, the value is the amount of physical memory available in the system. BYLS_MEM_ENTL_MIN ---------------------------------- The minimum amount of memory configured for the logical system, in MB. On AIX LPARs, this metric will be “na”. On vMA, this metric indicates the reserved amount of memory configured for a host, resource pool or a logical system. BYLS_MEM_ENTL_UTIL ---------------------------------- The percentage of entitled memory in use during the interval. On vMA, for a logical system or a host, the value indicates percentage of entitled memory in use during the interval by it. On vMA, for a resource pool, this metric is “na”. BYLS_MEM_FREE ---------------------------------- The amount of free memory on the logical system, in MB. On vMA, for a host and logical system, it is the amount of memory not allocated. For a resource pool the value is “na”. BYLS_MEM_FREE_UTIL ---------------------------------- The percentage of memory that is free at the end of the interval. On vMA, for a resource pool the value is NA. BYLS_MEM_HEALTH ---------------------------------- On vMA, for a host, it is a number that indicates the state of the memory. Low number indicates system is not under memory pressure. For a logical system and resource pool the value is “na”. On vMA, the values are defined as: 0 - High - indicates free memory is available and no memory pressure. 1 - Soft 2 - Hard 3 - Low - indicates there is a pressure for free memory. For relevant guests, these values represent the level of memory pressure, 0 being none and 3 being very high. BYLS_MEM_LOCKED ---------------------------------- This metric indicates the amount of locked physical memory available to a zone. The metric value is represented in Mbytes. BYLS_MEM_LOCKED_USED ---------------------------------- This metric indicates the amount of locked memory consumed by the zone with respect to total configured locked memory (BYLS_MEM_LOCKED). The metric value is represented in Mbytes. BYLS_MEM_LOCKED_UTIL ---------------------------------- This metric indicates the percentage of locked memory consumed by the zone with respect to total configured locked memory (BYLS_MEM_LOCKED). BYLS_MEM_OVERHEAD ---------------------------------- The amount of memory associated with a logical system, that is currently consumed on the host system, due to virtualization. On vMA, this metric indicates the amount of overhead memory associated with a host, logical system and resource pool. BYLS_MEM_PHYS ---------------------------------- On vMA, for host the value is the physical memory available in the system and for logical system this metric indicates the minimum memory configured. On vMA, for a resource pool, this metric is “na”. On HPVM, this metric matches the data in the “Memory Details” section of “hpvmstatus -V”, when the dynamic memory driver is not enabled, and it matches the data in the “Dynamic Memory Information” section when the dynamic memory driver is active. The dynamic memory driver is currently only available on guests running HPUX 11iv3 or newer versions. BYLS_MEM_PHYS_UTIL ---------------------------------- The percentage of physical memory used during the interval. On vMA, the metric indicates the percentage of physical memory used by a host, logical system. On vMA, for a resource pool, this metric is “na”. BYLS_MEM_SHARES_PRIO ---------------------------------- The weightage/priority for memory assigned to this logical system. This value influences the share of unutilized physical Memory that this logical system can utilize. The value of this metric will be “-3” in PA and “ul” in other clients if memory shares value is ‘Unlimited’ for a logical system. On AIX LPARs, this metric will be “na”. On vMA, this metric indicates the share of memory configured to a resource pool and a logical system. For a host the value is NA. BYLS_MEM_SWAP ---------------------------------- This metric indicates the total amount of swap that can be consumed by user process address space mappings and tmpfs mounts for this zone. The metric value is represented in Mbytes. BYLS_MEM_SWAPIN ---------------------------------- On vMA, for a logical system the value indicates the amount of memory that is swapped in during the interval. For a host and resource pool the value is NA. BYLS_MEM_SWAPOUT ---------------------------------- On vMA, for a logical system the value indicates the amount of memory that is swapped out during the interval. For a host and resource pool the value is NA. BYLS_MEM_SWAPPED ---------------------------------- On vMA, for a host, logical system and resource pool, this metrics indicates the amount of memory that has been transparently swapped to and from the disk. BYLS_MEM_SWAPTARGET ---------------------------------- On vMA, for a logical system the value indicates the amount of memory that can be swapped. For a host and resource pool the value is “na”. BYLS_MEM_SWAP_USED ---------------------------------- This metric indicates the amount of swap memory consumed by the zone with respect to total configured swap memory (BYLS_MEM_SWAP). The metric value is represented in Mbytes. BYLS_MEM_SWAP_UTIL ---------------------------------- On Solaris, this metric indicates the percentage of swap memory consumed by the zone with respect to total configured swap memory (BYLS_MEM_SWAP). This metric is calculated as : BYLS_MEM_SWAP_UTIL = (BYLS_MEM_SWAP_USED ) / (BYLS_MEM_SWAP) * 100 On vMA, for a logical system, it is the percentage of swap memory utilized w.r.t the amount of swap memory available for a logical system. For host and resource pool the value is NA. For a logical system this metric is calculated using the below formula: (BYLS_MEM_SWAPPED * 100)/(BYLS_MEM_ENTL - BYLS_MEM_ENTL_MIN) BYLS_MEM_SYS ---------------------------------- On vMA, for a host, it is the amount of physical memory (in MBs unless otherwise specified) used by the system (kernel) during the interval. For logical system and resource pool the value is NA. BYLS_MEM_UNRESERVED ---------------------------------- On vMA, for a host it is the amount of memory, that is unreserved. For a logical system and resource pool the value is “na”. Memory reservation not used by the Service Console, VMkernel, vSphere services and other powered on VMs user-specified memory reservations and overhead memory. BYLS_MEM_USED ---------------------------------- The amount of memory used by the logical system at the end of the interval. On vMA, this applies to hosts, resource pools and logical systems. On vMA, for a resource pool, this metric is “na”. BYLS_NET_BYTE_RATE ---------------------------------- On vMA, for a host and logical system, it is the sum of data transmitted and received for all the NIC instances of the host and virtual machine. It is represented in KBps. For a resource pool the value is NA. BYLS_NET_IN_BYTE ---------------------------------- On vMA, for a host and logical system, it is number of bytes, in MB, received during the interval. For a resource pool the value is NA. BYLS_NET_IN_PACKET ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of successful packets received through all network interfaces during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_NET_IN_PACKET_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of successful packets per second received through all network interfaces during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_NET_OUT_BYTE ---------------------------------- On vMA, for a host and logical system, it is the number of bytes, in MB, transmitted during the interval. For a resource pool the value is NA. BYLS_NET_OUT_PACKET ---------------------------------- On vMA, for a host and a logical system, it is the number of successful packets sent through all network interfaces during the last interval. On vMA, for a resource pool, this metric is “na”. BYLS_NET_OUT_PACKET_RATE ---------------------------------- On vMA, for a host and a logical system, this metric indicates the number of successful packets per second sent through the network interfaces during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_NET_PACKET_RATE ---------------------------------- On vMA, for a host and a logical system, it is the number of successful packets per second, both sent and received, for all network interfaces during the interval. On vMA, for a resource pool, this metric is “na”. BYLS_NUM_ACTIVE_LS ---------------------------------- On vMA, for a host, this indicates the number of logical systems hosted in a system that are active. For a logical system and resource pool the value is NA. BYLS_NUM_CPU ---------------------------------- The number of virtual CPUs configured for this logical system. This metric is equivalent to GBL_NUM_CPU on the corresponding logical system. On HPVM, the maximum CPUs a logical system can have is 4 with respect to HPVM 3.x. On AIX SPLPAR, the number of CPUs can be configured irrespective of the available physical CPUs in the pool this logical system belongs to. For AIX wpars, this metric represents the logical CPUs of the global environment. On vMA, for a host the metric is the number of physical CPU threads on the host. For a logical system, the metric is the number of virtual cpus configured.For a resource pool the metric is NA. On Solaris Zones, this metric represents number of CPUs in the CPU pool this zone is attached to. This metric value is equivalent to GBL_NUM_CPU inside corresponding non-global zone. BYLS_NUM_CPU_CORE ---------------------------------- On vMA, for a host this metric provides the toal number of CPU cores on the system. For a logical system or a resource pool the value is NA. BYLS_NUM_DISK ---------------------------------- The number of disks configured for this logical system. Only local disk devices and optical devices present on the system are counted in this metric. On vMA, for a host the metric is the number of disks configured for the host . For a logical system, the metric is the number of logical disk devices present on the logical system. For a resource pool the metric is NA. For AIX wpars, this metric will be “na”. On Hyper-V host, this metric value is equivalent to GBL_NUM_DISK inside corresponding Hyper-V guest. On Hyper-V host, this metric is NA if the logical system is not active. BYLS_NUM_LS ---------------------------------- On vMA, for a host, this indicates the number of logical systems hosted in a system. For a logical system and resource pool the value is NA. BYLS_NUM_NETIF ---------------------------------- The number of network interfaces configured for this logical system. On LPAR, this metric includes the loopback interface. On Hyper-V host, this metric value is equivalent to GBL_NUM_NETWORK inside corresponding Hyper-V guest. On Solaris Zones, this metric value is equivalent to GBL_NUM_NETWORK inside corresponding non-global zone. On Hyper-V host, this metric is NA if the logical system is not active. On vMA, for a host the metric is the number of network adapters on the host. For a logical system, the metric is the number of network interfaces configured for the logical system. For a resource pool the metric is NA. BYLS_NUM_SOCKET ---------------------------------- On vMA, for a host, this metrics indicates the number of physical cpu sockets on the system. For a logical system or a resource pool the value is NA. BYLS_PHANTOM_INTR ---------------------------------- It is the number of phantom interrupts that the logical partition received during the interval. A phantom interrupt is an interrupt sent to another logical partition that shares the same CPU Unit. On AIX LPAR, this value is equivalent to “phint” field reported by the “lparstat” command. For AIX wpars, the metric will be “na”. BYLS_POOL_NAME ---------------------------------- This metric indicates the name of the cpu pool this zone is attached to. BYLS_RUN_QUEUE ---------------------------------- The 1-minute load average for processors available for a logical system. On AIX LPAR, the load average is the total number of runnable and running threads summed over all processors during the interval. BYLS_SCHEDULING_CLASS ---------------------------------- This metric indicates the scheduling class for the zone. BYLS_UPTIME_HOURS ---------------------------------- On vMA, for a host and logical system the metrics is the time, in hours, since the last system reboot. For a resource pool the value is NA. BYLS_UPTIME_SECONDS ---------------------------------- The uptime of this logical system in seconds. On AIX LPARs, this metric will be “na”. On vMA, for a host and logical system the metric is the uptime in seconds while for a resource pool the metric is NA. BYLS_VCSWITCH_RATE ---------------------------------- Number of virtual context switches per second for a logical system during the interval. For AIX wpars, the metric will be “na”. BYLS_VC_IP_ADDRESS ---------------------------------- On vMA, for a host, the metric indicates the IP address of the Virtual Centre that the host is managed by. For a resource pool and logical system the value is NA. BYNETIF_COLLISION ---------------------------------- The number of physical collisions that occurred on the network interface during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets. This data is not collected for non-broadcasting devices, such as loopback (lo), and is always zero. For HP-UX, this will be the same as the sum of the “Single Collision Frames”, “Multiple Collision Frames”, “Late Collisions”, and “Excessive Collisions” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For most other Unix systems, this is the same as the sum of the “Coll” column from the “netstat -i” command (“collisions” from the “netstat -i -e” command on Linux) for a network device. See also netstat(1). If BYNETIF_NET_TYPE is “ESXVLan”, then this metric will be N/A. AIX does not support the collision count for the ethernet interface. The collision count is supported for the token ring (tr) and loopback (lo) interfaces. For more information, please refer to the netstat(1) man page. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. BYNETIF_COLLISION_1_MIN_RATE ---------------------------------- The number of physical collisions per minute on the network interface during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets. This data is not collected for non-broadcasting devices, such as loopback (lo), and is always zero. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric will be N/A. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_COLLISION_RATE ---------------------------------- The number of physical collisions per second on the network interface during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets. This data is not collected for non-broadcasting devices, such as loopback (lo), and is always zero. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric will be N/A. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. BYNETIF_ERROR ---------------------------------- The number of physical errors that occurred on the network interface during the interval. An increasing number of errors may indicate a hardware problem in the network. On Unix systems, this data is not available for loop-back (lo) devices and is always zero. For HP-UX, this will be the same as the sum of the “Inbound Errors” and “Outbound Errors” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of “Ierrs” (RX-ERR on Linux) and “Oerrs” (TX-ERR on Linux) from the “netstat -i” command for a network device. See also netstat(1). If BYNETIF_NET_TYPE is “ESXVLan”, then this metric will be N/A. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. BYNETIF_ERROR_1_MIN_RATE ---------------------------------- The number of physical errors per minute on the network interface during the interval. On Unix systems, this data is not available for loop-back (lo) devices and is always zero. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric will be N/A. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_ERROR_RATE ---------------------------------- The number of physical errors per second on the network interface during the interval. On Unix systems, this data is not available for loop-back (lo) devices and is always zero. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric will be N/A. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. BYNETIF_ID ---------------------------------- The ID number of the network interface. BYNETIF_IN_BYTE ---------------------------------- The number of KBs received from the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_IN_BYTE_RATE ---------------------------------- The number of KBs per second received from the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_IN_BYTE_RATE_CUM ---------------------------------- The average number of KBs per second received from the network via this interface over the cumulative collection time. Only the bytes in packets that carry data are included in this rate. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_IN_PACKET ---------------------------------- The number of successful physical packets received through the network interface during the interval. Successful packets are those that have been processed without errors or collisions. For HP-UX, this will be the same as the sum of the “Inbound Unicast Packets” and “Inbound Non-Unicast Packets” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of the “Ipkts” column (RX-OK on Linux) from the “netstat -i” command for a network device. See also netstat(1). If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_IN_PACKET_RATE ---------------------------------- The number of successful physical packets per second received through the network interface during the interval. Successful packets are those that have been processed without errors or collisions. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_NAME ---------------------------------- The name of the network interface. For HP-UX 11.0 and beyond, these are the same names that appear in the “Description” field of the “lanadmin” command output. On all other Unix systems, these are the same names that appear in the “Name” column of the “netstat -i” command. Some examples of device names are: lo - loop-back driver ln - Standard Ethernet driver en - Standard Ethernet driver le - Lance Ethernet driver ie - Intel Ethernet driver tr - Token-Ring driver et - Ether Twist driver bf - fiber optic driver All of the device names will have the unit number appended to the name. For example, a loop-back device in unit 0 will be “lo0”. On vMA for Lan cards which are of type ESXVLan, this metric contains the vmnic as first half and the second half is the ESX host name. BYNETIF_NET_MTU ---------------------------------- The size of the maximum transfer unit (MTU) for this interface. BYNETIF_NET_SPEED ---------------------------------- The speed of this interface. This is the bandwidth in Mega bits/sec. BYNETIF_NET_TYPE ---------------------------------- The type of network device the interface communicates through. Lan - local area network card Loop - software loopback interface (not tied to a hardware device) Loop6 - software loopback interface IPv6 (not tied to a hardware device) Serial - serial modem port Vlan - virtual lan Wan - wide area network card Tunnel - tunnel interface Apa - HP LinkAggregate Interface (APA) Other - hardware network interface type is unknown. ESXVLan - The card type belongs to network cards of ESX hosts which are monitored on vMA. BYNETIF_OUT_BYTE ---------------------------------- The number of KBs sent to the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_OUT_BYTE_RATE ---------------------------------- The number of KBs per second sent to the network via this interface during the interval. Only the bytes in packets that carry data are included in this rate. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_OUT_BYTE_RATE_CUM ---------------------------------- The average number of KBs per second sent to the network via this interface over the cumulative collection time. Only the bytes in packets that carry data are included in this rate. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_OUT_PACKET ---------------------------------- The number of successful physical packets sent through the network interface during the interval. Successful packets are those that have been processed without errors or collisions. For HP-UX, this will be the same as the sum of the “Outbound Unicast Packets” and “Outbound Non-Unicast Packets” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of the “Opkts” column (TX-OK on Linux) from the “netstat -i” command for a network device. See also netstat(1). If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_OUT_PACKET_RATE ---------------------------------- The number of successful physical packets per second sent through the network interface during the interval. Successful packets are those that have been processed without errors or collisions. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_PACKET_RATE ---------------------------------- The number of successful physical packets per second sent and received through the network interface during the interval. Successful packets are those that have been processed without errors or collisions. If BYNETIF_NET_TYPE is “ESXVLan”, then this metric shows the values for the Lan card in the host. Physical statistics are packets recorded by the network drivers. These numbers most likely will not be the same as the logical statistics. The values returned for the loopback interface will show “na” for the physical statistics since there is no network driver activity. Logical statistics are packets seen only by the Interface Protocol (IP) layer of the networking subsystem. Not all packets seen by IP will go out and come in through a network driver. An example is the loopback interface (127.0.0.1). Pings or other network generating commands (ftp, rlogin, and so forth) to 127.0.0.1 will not change physical driver statistics. Pings to IP addresses on remote systems will change physical driver statistics. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. BYNETIF_QUEUE ---------------------------------- The length of the outbound queue at the time of the last sample. This metric will be the same as the “Outbound Queue Length” values from the output of “lanadmin” utility. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On HP-UX, this metric is only available for LAN interfaces. For WAN (Wide- Area Network) interfaces such as ATM and X.25, with interface names such as el, cip/ixe, and netisdn, this metric returns “na”. BYNETIF_UTIL ---------------------------------- The percentage of bandwidth used with respect to the total available bandwidth on a given network interface at the end of the interval. On vMA this value will be N/A for those Lan cards which are of type ESXVLan. BYPROTOCOL_IN_PACKET ---------------------------------- The number of successful packets received via this protocol during the interval. Successful packets are those that have been processed without errors or collisions. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. BYPROTOCOL_IN_PACKET_RATE ---------------------------------- The number of successful packets per second received via this protocol during the interval. Successful packets are those that have been processed without errors or collisions. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. BYPROTOCOL_OUT_PACKET ---------------------------------- The number of successful packets sent via this protocol during the interval. Successful packets are those that have been processed without errors or collisions. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. BYPROTOCOL_OUT_PACKET_RATE ---------------------------------- The number of successful packets per second sent via this protocol during the interval. Successful packets are those that have been processed without errors or collisions. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. DATE ---------------------------------- The date the information in this record was captured, based on local time. The date is an ASCII field in mm/dd/yyyy format unless localized. If localized, the separators may be different and the subfield may be in a different sequence. In ASCII files this field will always contain 10 characters. Each subfield (mm, dd, yyyy) will contain a leading zero if the value is less than 10. This metric is extracted from GBL_STATTIME, which is obtained using the time() system call at the time of data collection. This field responds to language localization. For example, in Italy the field would appear as dd/mm/yyyy and in Japan it would be yyyy/mm/dd. In binary files this field is in MPE CALENDAR format in the least significant 16 bits of the field. The most significant 16 bits should all be zero. Dividing the field by 512 will isolate the year (that is, 94). This field MOD 512 will isolate the day of the year. DATE_SECONDS ---------------------------------- The time that the data in this record was captured, expressed in seconds since January 1, 1970, based on local time. This is related to the standard time- stamp returned by the unix system call time(), but has had the local time zone correction applied. DAY ---------------------------------- The julian day of the year that the data in this record was captured. This metric is extracted from GBL_STATTIME. FS_BLOCK_SIZE ---------------------------------- The maximum block size of this file system, in bytes. A value of “na” may be displayed if the file system is not mounted. If the product is restarted, these unmounted file systems are not displayed until remounted. FS_DEVNAME ---------------------------------- On Unix systems, this is the path name string of the current device. On Windows, this is the disk drive string of the current device. On HP-UX, this is the “fsname” parameter in the mount(1M) command. For NFS devices, this includes the name of the node exporting the file system. It is possible that a process may mount a device using the mount(2) system call. This call does not update the “/etc/mnttab” and its name is blank. This situation is rare, and should be corrected by syncer(1M). Note that once a device is mounted, its entry is displayed, even after the device is unmounted, until the midaemon process terminates. On SUN, this is the path name string of the current device, or “tmpfs” for memory based file systems. See tmpfs(7). FS_DEVNAME_ALIAS ---------------------------------- FS device name. This metric is no longer supported. FS_DEVNO ---------------------------------- On Unix systems, this is the major and minor number of the file system. On Windows, this is the unit number of the disk device on which the logical disk resides. The scope collector logs the value of this metric in decimal format. FS_DIRNAME ---------------------------------- On Unix systems, this is the path name of the mount point of the file system. On Windows, this is the drive letter associated with the selected disk partition. On HP-UX, this is the path name of the mount point of the file system if the logical volume has a mounted file system. This is the directory parameter of the mount(1M) command for most entries. Exceptions are: * For lvm swap areas, this field contains “lvm swap device”. * For logical volumes with no mounted file systems, this field contains “Raw Logical Volume” (relevant only to Perf Agent). On HP-UX, the file names are in the same order as shown in the “/usr/sbin/mount -p” command. File systems are not displayed until they exhibit IO activity once the midaemon has been started. Also, once a device is displayed, it continues to be displayed (even after the device is unmounted) until the midaemon process terminates. On SUN, only “UFS”, “HSFS” and “TMPFS” file systems are listed. See mount(1M) and mnttab(4). “TMPFS” file systems are memory based filesystems and are listed here for convenience. See tmpfs(7). On AIX, see mount(1M) and filesystems(4). On OSF1, see mount(2). FS_DIRNAME_ALIAS ---------------------------------- FS dir name. This metric is no longer supported. FS_FRAG_SIZE ---------------------------------- The fundamental file system block size, in bytes. A value of “na” may be displayed if the file system is not mounted. If the product is restarted, these unmounted file systems are not displayed until remounted. FS_INODE_UTIL ---------------------------------- Percentage of this file system’s inodes in use during the interval. A value of “na” may be displayed if the file system is not mounted. If the product is restarted, these unmounted file systems are not displayed until remounted. FS_MAX_INODES ---------------------------------- Number of configured file system inodes. A value of “na” may be displayed if the file system is not mounted. If the product is restarted, these unmounted file systems are not displayed until remounted. FS_MAX_SIZE ---------------------------------- Maximum number that this file system could obtain if full, in MB. Note that this is the user space capacity - it is the file system space accessible to non root users. On most Unix systems, the df command shows the total file system capacity which includes the extra file system space accessible to root users only. The equivalent fields to look at are “used” and “avail”. For the target file system, to calculate the maximum size in MB, use FS Max Size = (used + avail)/1024 A value of “na” may be displayed if the file system is not mounted. If the product is restarted, these unmounted file systems are not displayed until remounted. On HP-UX, this metric is updated at 4 minute intervals to minimize collection overhead. FS_REQUEST_QUEUE ---------------------------------- The average number of both i/o requests that were queued for the selected filesystem during the interval. FS_SPACE_RESERVED ---------------------------------- The amount of file system space in MBs reserved for superuser allocation. On AIX, this metric is typically zero because by default AIX does not reserve any file system space for the superuser. FS_SPACE_USED ---------------------------------- The amount of file system space in MBs that is being used. FS_SPACE_UTIL ---------------------------------- Percentage of the file system space in use during the interval. Note that this is the user space capacity - it is the file system space accessible to non root users. On most Unix systems, the df command shows the total file system capacity which includes the extra file system space accessible to root users only. A value of “na” may be displayed if the file system is not mounted. If the product is restarted, these unmounted file systems are not displayed until remounted. On HP-UX, this metric is updated at 4 minute intervals to minimize collection overhead. FS_TYPE ---------------------------------- A string indicating the file system type. On Unix systems, some of the possible types are: hfs - user file system ufs - user file system ext2 - user file system cdfs - CD-ROM file system vxfs - Veritas (vxfs) file system nfs - network file system nfs3 - network file system Version 3 On Windows, some of the possible types are: NTFS - New Technology File System FAT - 16-bit File Allocation Table FAT32 - 32-bit File Allocation Table FAT uses a 16-bit file allocation table entry (216 clusters). FAT32 uses a 32-bit file allocation table entry. However, Windows 2000 reserves the first 4 bits of a FAT32 file allocation table entry, which means FAT32 has a theoretical maximum of 228 clusters. NTFS is native file system of Windows NT and beyond. GBL_ACTIVE_CPU ---------------------------------- The number of CPUs online on the system. For HP-UX and certain versions of Linux, the sar(1M) command allows you to check the status of the system CPUs. For SUN and DEC, the commands psrinfo(1M) and psradm(1M) allow you to check or change the status of the system CPUs. For AIX, the pstat(1) command allows you to check the status of the system CPUs. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment if RSET is not configured for the System WPAR. If RSET is configured for the System WPAR, this metric value will report the number of CPUs in the RSET. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_ACTIVE_CPU_CORE ---------------------------------- This metric provides the total number of active CPU cores on a physical system. GBL_ACTIVE_PROC ---------------------------------- An active process is one that exists and consumes some CPU time. GBL_ACTIVE_PROC is the sum of the alive-process-time/interval-time ratios of every process that is active (uses any CPU time) during an interval. The following diagram of a four second interval during which two processes exist on the system should be used to understand the above definition. Note the difference between active processes, which consume CPU time, and alive processes which merely exist on the system. ----------- Seconds ----------- 1 2 3 4 Proc ---- ---- ---- ---- ---- A live live live live B live/CPU live/CPU live dead Process A is alive for the entire four second interval but consumes no CPU. A’s contribution to GBL_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to GBL_ACTIVE_PROC. B’s contribution to GBL_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to GBL_ACTIVE_PROC. Thus, for this interval, GBL_ACTIVE_PROC equals 0.5 and GBL_ALIVE_PROC equals 1.75. Because a process may be alive but not active, GBL_ACTIVE_PROC will always be less than or equal to GBL_ALIVE_PROC. This metric is a good overall indicator of the workload of the system. An unusually large number of active processes could indicate a CPU bottleneck. To determine if the CPU is a bottleneck, compare this metric with GBL_CPU_TOTAL_UTIL and GBL_RUN_QUEUE. If GBL_CPU_TOTAL_UTIL is near 100 percent and GBL_RUN_QUEUE is greater than one, there is a bottleneck. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. GBL_ALIVE_PROC ---------------------------------- An alive process is one that exists on the system. GBL_ALIVE_PROC is the sum of the alive-process-time/interval-time ratios for every process. The following diagram of a four second interval during which two processes exist on the system should be used to understand the above definition. Note the difference between active processes, which consume CPU time, and alive processes which merely exist on the system. ----------- Seconds ----------- 1 2 3 4 Proc ---- ---- ---- ---- ---- A live live live live B live/CPU live/CPU live dead Process A is alive for the entire four second interval but consumes no CPU. A’s contribution to GBL_ALIVE_PROC is 4*1/4. A contributes 0*1/4 to GBL_ACTIVE_PROC. B’s contribution to GBL_ALIVE_PROC is 3*1/4. B contributes 2*1/4 to GBL_ACTIVE_PROC. Thus, for this interval, GBL_ACTIVE_PROC equals 0.5 and GBL_ALIVE_PROC equals 1.75. Because a process may be alive but not active, GBL_ACTIVE_PROC will always be less than or equal to GBL_ALIVE_PROC. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. Win3x/95 The number of virtual machines (VMs) active in the system. Samples are collected every 30 seconds and the maximum collected during a monitoring interval is reported. In both Windows 3.11 and Windows 95, all 16- and 32-bit applications run in a single virtual machine, the system VM. All DOS sessions run in separate virtual machines. Under Windows for Workgroups only, there is a second Windows virtual machine that runs the network server. GBL_ALIVE_THREAD ---------------------------------- The average number of threads sampled during a monitoring interval (Windows 95 only). Samples are collected every 30 seconds. A single virtual machine may have one or many threads of execution. GBL_APP_THRESHOLD ---------------------------------- appthreshold specifies the thresholds for APPLICATION class. This is the percentage of cpu being utilized by an application (APP_CPU_TOTAL_UTIL) during the interval. This threshold value is supplied by the parm file. An application must exceed this threshold value in any given interval before it will be considered interesting to be logged. GBL_BLOCKED_IO_QUEUE ---------------------------------- The average number of processes blocked on local disk resources (IO, paging). This metric is an indicator of disk contention among active processes. It should normally be a very small number. If GBL_DISK_UTIL_PEAK is near 100 percent and GBL_BLOCKED_IO_QUEUE is greater than 1, a disk bottleneck is probable. On SUN, this is the same as the “procs b” field reported in vmstat. On Solaris non-global zones, this metric shows data from the global zone. GBL_BOOT_TIME ---------------------------------- The date and time when the system was last booted. GBL_BYCPU_THRESHOLD ---------------------------------- bycputhreshold specifies the thresholds for CPU class. This is the percentage of time a cpu was busy (BYCPU_CPU_TOTAL_UTIL) during the interval. This threshold value is supplied by the parm file. A cpu must exceed this threshold value in any given interval before it will be considered interesting to be logged. GBL_BYDSK_THRESHOLD ---------------------------------- diskthreshold specifies the threshold for DISK class. This is the percentage of time that a disk busy in performing IO (BYDSK_UTIL) during the interval. This threshold value is supplied by the parm file. A disk must exceed this threshold value in any given interval before it will be considered interesting and be logged. GBL_BYFS_THRESHOLD ---------------------------------- fsthreshold specifies the thresholds for FILESYSTEM class. This is the percentage of space used (FS_SPACE_UTIL) of the filesystem. This threshold value is supplied by the parm file. A filesystem must exceed this threshold value in any given interval before it will be considered interesting to be logged. GBL_BYNETIF_THRESHOLD ---------------------------------- bynetifthreshold specifies the thresholds for NETIF class. This is the number of packets transferred per second during the interval(BYNETIF_PACKET_RATE). This threshold value is supplied by the parm file. A network interface must exceed this threshold value in any given interval before it will be considered interesting to be logged. GBL_COLLECTOR ---------------------------------- ASCII field containing collector name and version. The collector name will appear as either “SCOPE/xx V.UU.FF.LF” or “Coda RV.UU.FF.LF”. xx identifies the platform; V = version, UU = update level, FF = fix level, and LF = lab fix id. For example, SCOPE/UX C.04.00.00; or Coda A.07.10.04. GBL_COLLECT_INTERVAL ---------------------------------- The interval, in seconds, at which non-process metrics are collected. Collection intervals are set in parm file. GBL_COLLECT_INTERVAL_PROC ---------------------------------- The interval, in seconds, at which process metrics are collected. Collection intervals are set in parm file. GBL_COMPLETED_PROC ---------------------------------- The number of processes that terminated during the interval. On non HP-UX systems, this metric is derived from sampled process data. Since the data for a process is not available after the process has died on this operating system, a process whose life is shorter than the sampling interval may not be seen when the samples are taken. Thus this metric may be slightly less than the actual value. Increasing the sampling frequency captures a more accurate count, but the overhead of collection may also rise. GBL_CPU_CLOCK ---------------------------------- The clock speed of the CPUs in MHz if all of the processors have the same clock speed. Otherwise, “na” is shown if the processors have different clock speeds. Note that Linux supports dynamic frequency scaling and if it is enabled then there can be a change in CPU speed with varying load. GBL_CPU_CSWITCH_TIME ---------------------------------- The time, in seconds, that the CPU spent context switching during the interval. On HP-UX, this includes context switches that result in the execution of a different process and those caused by a process stopping, then resuming, with no other process running in the meantime. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_CSWITCH_UTIL ---------------------------------- The percentage of time that the CPU spent context switching during the interval. On HP-UX, this includes context switches that result in the execution of a different process and those caused by a process stopping, then resuming, with no other process running in the meantime. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_CYCLE_ENTL_MAX ---------------------------------- On a recognized VMware ESX guest, where VMware guest SDK is enabled,, this value indicates the maximum processor capacity, in MHz, configured for this logical system. The value is -3 if entitlement is ‘Unlimited’ for this logical system. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na”. On a standalone system, the value is the sum of clock speed of individual CPUs. GBL_CPU_CYCLE_ENTL_MIN ---------------------------------- On a recognized VMware ESX guest, where VMware guest SDK is enabled,, this value indicates the minimum processor capacity, in MHz, configured for this logical system. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na”. On a standalone system, the value is the sum of clock speed of individual CPUs. GBL_CPU_ENTL ---------------------------------- In a virtual environment this metric indicates the physical processor units allocated to this Logical system. On AIX SPLPAR, this metric indicates the entitlement allocated by Hypervisor to a logical system at the time of starting. This metric is equivalent to “Entitled Capacity” field of ‘lparstat -i’ command. On a standalone system the value of this metric is same as GBL_NUM_CPU. GBL_CPU_ENTL_MAX ---------------------------------- In a virtual environment, this metric indicates the maximum number of processing units configured for this logical system. On AIX SPLPAR, this metric is equivalent to “Maximum Capacity” field of ‘lparstat -i’ command. On a recognized VMware ESX guest the value is equivalent to GBL_CPU_CYCLE_ENTL_MAX represented in CPU units. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na”. On a standalone system the value is same as GBL_NUM_CPU. GBL_CPU_ENTL_MIN ---------------------------------- In a virtual environment, this metric indicates the minimum number of processing units configured for this Logical system. On AIX SPLPAR, this metric is equivalent to “Minimum Capacity” field of ‘lparstat -i’ command. On a recognized VMware ESX guest, where VMware guest SDK is enabled, the value is equivalent to GBL_CPU_CYCLE_ENTL_MIN represented in CPU units. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na”. On a standalone system the value is same as GBL_NUM_CPU. GBL_CPU_ENTL_UTIL ---------------------------------- Percentage of entitled processing units (guaranteed processing units allocated to this logical system) consumed by the logical system. AIX On an “Uncapped” logical system, this metric can exceed 100% if the processing units are available in the shared resource pool and the number of virtual CPUs are satisfied. On a Capped logical system this metric can never go beyond 100%. On AIX, this metric is calculated as: GBL_CPU_ENTL_UTIL = (GBL_CPU_PHYSC / GBL_CPU_ENTL) * 100 On a recognized VMware ESX guest, where VMware guest SDK is enabled, this metric is calculated as: GBL_CPU_ENTL_UTIL = (GBL_CPU_PHYSC / GBL_CPU_ENTL_MIN) * 100 On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na”. On a standalone system, the value is same as GBL_CPU_TOTAL_UTIL. GBL_CPU_HISTOGRAM ---------------------------------- Histogram of CPU utilization components. HP-UX Shows breakout: GBL_CPU_TOTAL_UTIL = GBL_CPU_SYSCALL_UTIL + GBL_CPU_NICE_UTIL + GBL_CPU_NORMAL_UTIL + GBL_CPU_REALTIME_UTIL + GBL_CPU_CSWITCH_UTIL + GBL_CPU_INTERRUPT_UTIL ASCII and BINARY files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of CPU usage on a character-mode terminal display. SunOS AIX NCR Sinix Shows breakout: GBL_CPU_TOTAL_UTIL = GBL_CPU_SYS_MODE_UTIL + GBL_CPU_USER_MODE_UTIL ASCII and BINARY files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of CPU usage on a character-mode terminal display. WinNT Shows breakout: GBL_CPU_TOTAL_UTIL = GBL_CPU_SYS_MODE_UTIL + GBL_CPU_USER_MODE_UTIL + GBL_CPU_INTERRUPT_UTIL ASCII and BINARY files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of CPU usage on a character-mode terminal display. GBL_CPU_IDLE_TIME ---------------------------------- The time, in seconds, that the CPU was idle during the interval. This is the total idle time, including waiting for I/O. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. On AIX System WPARs, this metric value is calculated against physical cpu time. On Solaris non-global zones, this metric is N/A. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_IDLE_UTIL ---------------------------------- The percentage of time that the CPU was idle during the interval. This is the total idle time, including waiting for I/O. On Unix systems, this is the same as the sum of the “%idle” and “%wio” fields reported by the “sar -u” command. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. On Solaris non-global zones, this metric is N/A. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_INTERRUPT_TIME ---------------------------------- The time, in seconds, that the CPU spent processing interrupts during the interval. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On Hyper-V host, this metric is NA. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_INTERRUPT_UTIL ---------------------------------- The percentage of time that the CPU spent processing interrupts during the interval. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On Hyper-V host, this metric is NA. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_MT_ENABLED ---------------------------------- On AIX, this metric indicates if this (Logical) System has SMT enabled or not. Other platforms, this metric shows either HyperThreading(HT) is Enabled or Disabled/Not Supported. On Linux, this state is dynamic: if HyperThreading is enabled but all the CPUs have only one logical processor enabled, this metric will report that HT is disabled. On AIX System WPARs, this metric is NA. On Windows, this metric will be “na” on Windows Server 2003 Itanium systems. GBL_CPU_NICE_TIME ---------------------------------- The time, in seconds, that the CPU was in user mode at a nice priority during the interval. On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_NICE_UTIL ---------------------------------- The percentage of time that the CPU was in user mode at a nice priority during the interval. On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_NORMAL_TIME ---------------------------------- The time, in seconds, that the CPU was in user mode at normal priority during the interval. Normal priority user mode CPU excludes CPU used at real-time and nice priorities. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_NORMAL_UTIL ---------------------------------- The percentage of time that the CPU was in user mode at normal priority during the interval. Normal priority user mode CPU excludes CPU used at real-time and nice priorities. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_NUM_THREADS ---------------------------------- The number of active CPU threads supported by the CPU architecture. The Linux kernel currently doesn’t provide any metadata information for disabled CPUs. This means that there is no way to find out types, speeds, as well as hardware IDs or any other information that is used to determine the number of cores, the number of threads, the HyperThreading state, etc... If the agent (or Glance) is started while some of the CPUs are disabled, some of these metrics will be “na”, some will be based on what is visible at startup time. All information will be updated if/when additional CPUs are enabled and information about them becomes available. The configuration counts will remain at the highest discovered level (i.e. if CPUs are then disabled, the maximum number of CPUs/cores/etc... will remain at the highest observed level). It is recommended that the agent be started with all CPUs enabled. On AIX System WPARs, this metric is NA. GBL_CPU_PHYSC ---------------------------------- The number of physical processors utilized by the logical system. On an Uncapped logical system (partition), this value will be equal to the physical processor capacity used by the logical system during the interval. This can be more than the value entitled for a logical system. On a standalone system the value is calculated based on GBL_CPU_TOTAL_UTIL GBL_CPU_PHYS_SYS_MODE_UTIL ---------------------------------- The percentage of time the physical CPU was in system mode (kernel mode) for the logical system during the interval. On AIX LPAR, this value is equivalent to “%sys” field reported by the “lparstat” command. On AIX System WPARs, this metric value is calculated against physical cpu time. GBL_CPU_PHYS_TOTAL_UTIL ---------------------------------- The percentage of time the available physical CPUs were not idle for this logical system during the interval. On AIX, this metric is calculated as : GBL_CPU_PHYS_TOTAL_UTIL = GBL_CPU_PHYS_USER_MODE_UTIL + GBL_CPU_PHYS_SYS_MODE_UTIL ; GBL_CPU_PHYS_TOTAL_UTIL + GBL_CPU_PHYS_WAIT_UTIL + GBL_CPU_PHYS_IDLE_UTIL = 100% On Power5 based systems, traditional sample based calculations cannot be made because the dispatch cycle for each of the virtual CPUs is not same. So Power5 processor maintains a per-thread register PURR. The thread is dispatching instructions or the thread that last dispatched an instruction will be incremented at every processor clock cycle. This makes the value to be distributed between the two threads. Power5 processor also maintains two more registers, one is timebase - which gets incremented at every tick and decrementer - that provided periodic interrupts. On a Shared LPAR environment, PURR is equal to the time that a virtual processor has spent on a physical processor. Hypervisor maintains a virtual timebase which is same as the sum of two PURRs. On a Capped Shared logical system (partition), the calculations for the metric GBL_CPU_PHYS_USER_MODE_UTIL is as follows: (delta PURR in user mode/entitlement) * 100 On an Uncapped Shared logical system (partition): (delta PURR in user mode/entitlement consumed) * 100 The calculations for the other utilizations such as GBL_CPU_PHYS_USER_MODE_UTIL, GBL_CPU_PHYS_SYS_MODE_UTIL, and GBL_CPU_PHYS_WAIT_UTIL are also similar. On a standalone system, the value will be equivalent to GBL_CPU_TOTAL_UTIL. On AIX System WPARs, this metric value is calculated against physical cpu time. GBL_CPU_PHYS_USER_MODE_UTIL ---------------------------------- The percentage of time the physical CPU was in user mode for the logical system during the interval. On AIX LPAR, this value is equivalent to “%user” field reported by the “lparstat” command. On AIX System WPARs, this metric value is calculated against physical cpu time. GBL_CPU_QUEUE ---------------------------------- HP-UX The average number of processes or kernel threads using the CPU plus all of those processes or kernel threads blocked on PRIORITY (waiting for their priority to become high enough to get the CPU) during the interval. This metric is an indicator of CPU demands among the active processes or kernel threads. To determine if the CPU is a bottleneck, compare this metric with GBL_CPU_TOTAL_UTIL. If GBL_CPU_TOTAL_UTIL is near 100 percent and GBL_CPU_QUEUE is greater than four, there is a high probability of a CPU bottleneck. This is calculated as (the CPU time used plus the accumulated time that all processes or kernel threads spent blocked on PRI (that is, priority)) divided by the interval time. The difference between this metric and GBL_PRI_QUEUE is that it includes the processes or kernel threads using the CPU, if any. HP-UX RUN/PRI/CPU Queue differences for multi-cpu systems: For example, let’s assume we’re using a system with eight processors. We start eight CPU intensive threads that consume almost all of the CPU resources. The approximate values shown for the CPU related queue metrics would be: GBL_RUN_QUEUE = 1.0 GBL_PRI_QUEUE = 0.1 GBL_CPU_QUEUE = 1.0 Assume we start an additional eight CPU intensive threads. The approximate values now shown are: GBL_RUN_QUEUE = 2.0 GBL_PRI_QUEUE = 8.0 GBL_CPU_QUEUE = 16.0 At this point, we have sixteen CPU intensive threads running on the eight processors. Keeping the definitions of the three queue metrics in mind, the run queue is 2 (that is, 16 / 8); the pri queue is 8 (only half of the threads can be active at any given time); and the cpu queue is 16 (half of the threads waiting in the cpu queue that are ready to run, plus one for each active thread). This illustrates that the run queue is the average of number of threads waiting in the runqueue for all processors; the pri queue is the number of threads that are blocked on “PRI” (priority); and the cpu queue is the number of threads in the cpu queue that are ready to run, including the threads using the CPU. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. AIX The snapshot of number of processes using the CPU plus all of those processes blocked on Priority (waiting for their priority to become high enough to get the CPU) during the last sub-procinterval. The value represents the queue length during the last sub-procinterval. Its calculated for the last sub- procinterval because the most recent number of processes running now and blocked on priority can be obtained only during the last sub-procinterval. To determine if the CPU is a bottleneck, compare this metric with GBL_CPU_TOTAL_UTIL. If GBL_CPU_TOTAL_UTIL is near 100 percent and GBL_CPU_QUEUE is greater than four, there is a high probability of a CPU bottleneck. This metric also accounts for GBL_PRI_QUEUE and its value is always greater than GBL_PRI_QUEUE. GBL_CPU_REALTIME_TIME ---------------------------------- The time, in seconds, that the CPU was in user mode at a realtime priority during the interval. Running at a realtime priority means that the process or kernel thread was run using the rtprio command or the rtprio system call to alter its priority. Realtime priorities range from zero to 127 and are absolute priorities, meaning the realtime process with the lowest priority runs as long as it wants to. Since this can have a huge impact on the system, the realtime CPU is tracked separately to make visible the effect of using realtime priorities. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_REALTIME_UTIL ---------------------------------- The percentage of time that the CPU was in user mode at a realtime priority during the interval. Running at a realtime priority means that the process or kernel thread was run using the rtprio command or the rtprio system call to alter its priority. Realtime priorities range from zero to 127 and are absolute priorities, meaning the realtime process with the lowest priority runs as long as it wants to. Since this can have a huge impact on the system, the realtime CPU is tracked separately to make visible the effect of using realtime priorities. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_SHARES_PRIO ---------------------------------- The weightage/priority assigned to a Uncapped logical system. This value determines the minimum share of unutilized processing units that this logical system can utilize. On AIX SPLPAR this value is dependent on the available processing units in the pool and can range from 0 to 255 On recognized VMware ESX guest, this value can range from 1 to 100000 On a standalone system the value will be “na”. GBL_CPU_SYSCALL_TIME ---------------------------------- The time, in seconds, that the CPU was in system mode (excluding interrupt, context switch, trap, or vfault CPU) during the interval. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_SYSCALL_UTIL ---------------------------------- The percentage of time that the CPU was in system mode (excluding interrupt, context switch, trap, or vfault CPU) during the interval. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. GBL_CPU_SYS_MODE_TIME ---------------------------------- The time, in seconds, that the CPU was in system mode during the interval. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. On AIX System WPARs, this metric value is calculated against physical cpu time. On Hyper-V host, this metric indicates the time spent in Hypervisor code. GBL_CPU_SYS_MODE_UTIL ---------------------------------- Percentage of time the CPU was in system mode during the interval. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. This metric is a subset of the GBL_CPU_TOTAL_UTIL percentage. This is NOT a measure of the amount of time used by system daemon processes, since most system daemons spend part of their time in user mode and part in system calls, like any other process. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. High system mode CPU percentages are normal for IO intensive applications. Abnormally high system mode CPU percentages can indicate that a hardware problem is causing a high interrupt rate. It can also indicate programs that are not calling system calls efficiently. On a logical system, this metric indicates the percentage of time the logical processor was in kernel mode during this interval. On Hyper-V host, this metric indicates the percentage of time spent in Hypervisor code. GBL_CPU_TOTAL_TIME ---------------------------------- The total time, in seconds, that the CPU was not idle in the interval. This is calculated as GBL_CPU_TOTAL_TIME = GBL_CPU_USER_MODE_TIME + GBL_CPU_SYS_MODE_TIME On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. On AIX System WPARs, this metric value is calculated against physical cpu time. GBL_CPU_TOTAL_UTIL ---------------------------------- Percentage of time the CPU was not idle during the interval. This is calculated as GBL_CPU_TOTAL_UTIL = GBL_CPU_USER_MODE_UTIL + GBL_CPU_SYS_MODE_UTIL On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. GBL_CPU_TOTAL_UTIL + GBL_CPU_IDLE_UTIL = 100% This metric varies widely on most systems, depending on the workload. A consistently high CPU utilization can indicate a CPU bottleneck, especially when other indicators such as GBL_RUN_QUEUE and GBL_ACTIVE_PROC are also high. High CPU utilization can also occur on systems that are bottlenecked on memory, because the CPU spends more time paging and swapping. NOTE: On Windows, this metric may not equal the sum of the APP_CPU_TOTAL_UTIL metrics. Microsoft states that “this is expected behavior” because this GBL_CPU_TOTAL_UTIL metric is taken from the performance library Processor objects while the APP_CPU_TOTAL_UTIL metrics are taken from the Process objects. Microsoft states that there can be CPU time accounted for in the Processor system objects that may not be seen in the Process objects. On a logical system, this metric indicates the logical utilization with respect to number of processors available for the logical system (GBL_NUM_CPU). On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. Win3x/95 For Windows 3.11 systems, this is a system-wide, rather than a strictly CPU metric. It usually includes time spent waiting for device drivers to complete IO operations. The metric is valid only for Windows applications. All time spent in most DOS applications will be reported as busy time. The GBL_ALIVE_PROC metric can be used to indicate whether DOS was in use. If more than one virtual machine (more than two when using Windows for Workgroups) is shown, then a DOS “box” has been opened. GBL_CPU_USER_MODE_TIME ---------------------------------- The time, in seconds, that the CPU was in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. On AIX System WPARs, this metric value is calculated against physical cpu time. On Hyper-V host, this metric indicates the time spent in guest code. GBL_CPU_USER_MODE_UTIL ---------------------------------- The percentage of time the CPU was in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. This metric is a subset of the GBL_CPU_TOTAL_UTIL percentage. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. High user mode CPU percentages are normal for computation-intensive applications. Low values of user CPU utilization compared to relatively high values for GBL_CPU_SYS_MODE_UTIL can indicate an application or hardware problem. On a logical system, this metric indicates the percentage of time the logical processor was in user mode during this interval. On Hyper-V host, this metric indicates the percentage of time spent in guest code. GBL_CPU_WAIT_TIME ---------------------------------- The time, in seconds, that the CPU was idle and there were processes waiting for physical IOs to complete during the interval. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On AIX System WPARs, this metric value is calculated against physical cpu time. On Solaris non-global zones, this metric is N/A. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. On Linux, this includes CPU steal time (shown as ‘%steal’ in ‘sar’ and ‘st’ in ‘vmstat’). GBL_CPU_WAIT_UTIL ---------------------------------- The percentage of time during the interval that the CPU was idle and there were processes waiting for physical IOs to complete. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. On Solaris non-global zones, this metric is N/A. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. On Linux, this includes CPU steal time (shown as ‘%steal’ in ‘sar’ and ‘st’ in ‘vmstat’). GBL_CSWITCH_RATE ---------------------------------- The average number of context switches per second during the interval. On HP-UX, this includes context switches that result in the execution of a different process and those caused by a process stopping, then resuming, with no other process running in the meantime. On Windows, this includes switches from one thread to another either inside a single process or across processes. A thread switch can be caused either by one thread asking another for information or by a thread being preempted by another higher priority thread becoming ready to run. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_BLOCK_IO ---------------------------------- The total number of block IOs during the interval. On SUN, these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These do include the IO of the inode (system write) and the file system data IO. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_BLOCK_IO_RATE ---------------------------------- The total number of block IOs per second during the interval. On SUN, these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These do include the IO of the inode (system write) and the file system data IO. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_BLOCK_READ ---------------------------------- The number of block reads during the interval. On SUN, these are physical reads generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, these are physical reads generated by file system access and do not include virtual memory reads, or reads relating to raw disk access. These do include the read of the inode (system read) and the file data read. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_BLOCK_READ_RATE ---------------------------------- The number of block reads per second during the interval. On SUN, these are physical reads generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, these are physical reads generated by file system access and do not include virtual memory reads, or reads relating to raw disk access. These do include the read of the inode (system read) and the file data read. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_BLOCK_WRITE ---------------------------------- The number of block writes during the interval. On SUN, these are physical writes generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, these are physical writes generated by file system access and do not include virtual memory writes, or writes relating to raw disk access. These do include the write of the inode (system write) and the file system data write. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_BLOCK_WRITE_RATE ---------------------------------- The number of block writes per second during the interval. On SUN, these are physical writes generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, these are physical writes generated by file system access and do not include virtual memory writes, or writes relating to raw disk access. These do include the write of the inode (system write) and the file system data write. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_CACHE_READ ---------------------------------- The number of cached reads made during the interval. GBL_DISK_CACHE_READ_RATE ---------------------------------- The number of cached reads per second made during the interval. GBL_DISK_FS_IO ---------------------------------- The total of physical file system disk reads and writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical IOs generated by user file system access and do not include virtual memory IOs, system IOs (inode updates), or IOs relating to raw disk access. An exception is user files accessed via the mmap(2) call, which will not show their physical IOs in this category. They appear under virtual memory IOs. GBL_DISK_FS_IO_RATE ---------------------------------- The total of file system disk physical reads and writes per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical IOs generated by user file system access and do not include virtual memory IOs, system IOs (inode updates), or IOs relating to raw disk access. An exception is user files accessed via the mmap(2) call, which will not show their physical IOs in this category. They appear under virtual memory IOs. Win3x/95 The number of read and write operations delivered to the file system each second. GBL_DISK_FS_READ ---------------------------------- The number of file system disk reads during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access), or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical reads in this category. They appear under virtual memory reads. GBL_DISK_FS_READ_RATE ---------------------------------- The number of file system disk reads per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access), or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical reads in this category. They appear under virtual memory reads. GBL_DISK_FS_WRITE ---------------------------------- The number of file system disk writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical writes generated by user file system access and do not include virtual memory writes, system writes (inode updates), or writes relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical writes in this category. They appear under virtual memory writes. GBL_DISK_FS_WRITE_RATE ---------------------------------- The number of file system disk writes per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical writes generated by user file system access and do not include virtual memory writes, system writes (inode updates), or writes relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical writes in this category. They appear under virtual memory writes. GBL_DISK_HISTOGRAM ---------------------------------- Histogram of physical Disk IO rate components. On HP-UX, this shows a breakout of: GBL_DISK_PHYS_IO_RATE = GBL_DISK_VM_IO_RATE + GBL_DISK_SYSTEM_IO_RATE + GBL_DISK_FS_IO_RATE + GBL_DISK_RAW_IO_RATE On SUN systems, this shows a breakout of: GBL_DISK_PHYS_IO_RATE = GBL_DISK_BLOCK_READ_RATE + GBL_DISK_BLOCK_WRITE_RATE + GBL_DISK_RAW_READ_RATE + GBL_DISK_RAW_WRITE_RATE + GBL_DISK_VM_IO_RATE On the remaining Unix systems, this shows a breakout of: GBL_DISK_PHYS_IO_RATE = GBL_DISK_BLOCK_IO_RATE + GBL_DISK_VM_IO_RATE + GBL_DISK_RAW_IO_RATE On Windows, this shows a breakout of: GBL_DISK_PHYS_IO_RATE = GBL_DISK_PHYS_READ_RATE + GBL_DISK_PHYS_WRITE_RATE ASCII and BINARY files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of Disk usage on a character-mode terminal display. GBL_DISK_LOGL_IO ---------------------------------- The number of logical IOs made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. GBL_DISK_LOGL_IO_RATE ---------------------------------- The number of logical IOs per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. Win3x/95 The number of requests per second made to the SmartDrive cache manager (Windows 3.11 only). This metric is not available for Windows for Workgroups 3.11 systems using 32-bit file access. GBL_DISK_LOGL_READ ---------------------------------- On most systems, this is the number of logical reads made during the interval. On SUN, this is the number of logical block reads made during the interval. On Windows, this includes both buffered (cached) read requests and unbuffered reads. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. GBL_DISK_LOGL_READ_BYTE ---------------------------------- The number of KBs transferred through logical reads during the last interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. GBL_DISK_LOGL_READ_BYTE_RATE ---------------------------------- The number of KBs transferred per second via logical reads during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. GBL_DISK_LOGL_READ_RATE ---------------------------------- On most systems, this is The average number of logical reads per second made during the interval. On SUN, this is the average number of logical block reads per second made during the interval. On Windows, this includes both buffered (cached) read requests and unbuffered reads. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_LOGL_WRITE ---------------------------------- On most systems, this is the number of logical writes made during the interval. On SUN, this is the number of logical block writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. GBL_DISK_LOGL_WRITE_BYTE ---------------------------------- The number of KBs transferred via logical writes during the last interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. GBL_DISK_LOGL_WRITE_BYTE_RATE ---------------------------------- The number of KBs per second transferred via logical writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. GBL_DISK_LOGL_WRITE_RATE ---------------------------------- On most systems, this is the average number of logical writes per second made during the interval. On SUN, this is the average number of logical block writes per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_PATH_COUNT ---------------------------------- The number of paths available to the disks on the system. This metric is only valid on aix VIO servers. GBL_DISK_PHYS_BYTE ---------------------------------- The number of KBs transferred to and from disks during the interval. The bytes for all types of physical IOs are counted. Only local disks are counted in this measurement. NFS devices are excluded. It is not directly related to the number of IOs, since IO requests can be of differing lengths. On Unix systems, this includes file system IO, virtual memory IO, and raw IO. On Windows, all types of physical IOs are counted. On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_BYTE_RATE ---------------------------------- The average number of KBs per second at which data was transferred to and from disks during the interval. The bytes for all types physical IOs are counted. Only local disks are counted in this measurement. NFS devices are excluded. This is a measure of the physical data transfer rate. It is not directly related to the number of IOs, since IO requests can be of differing lengths. This is an indicator of how much data is being transferred to and from disk devices. Large spikes in this metric can indicate a disk bottleneck. On Unix systems, all types of physical disk IOs are counted, including file system, virtual memory, and raw reads. On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_IO ---------------------------------- The number of physical IOs during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk IOs are counted, including file system IO, virtual memory IO and raw IO. On HP-UX, this is calculated as GBL_DISK_PHYS_IO = GBL_DISK_FS_IO + GBL_DISK_VM_IO + GBL_DISK_SYSTEM_IO + GBL_DISK_RAW_IO On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_IO_RATE ---------------------------------- The number of physical IOs per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk IOs are counted, including file system IO, virtual memory IO and raw IO. On HP-UX, this is calculated as GBL_DISK_PHYS_IO_RATE = GBL_DISK_FS_IO_RATE + GBL_DISK_VM_IO_RATE + GBL_DISK_SYSTEM_IO_RATE + GBL_DISK_RAW_IO_RATE On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_READ ---------------------------------- The number of physical reads during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk reads are counted, including file system, virtual memory, and raw reads. On HP-UX, there are many reasons why there is not a direct correlation between the number of logical IOs and physical IOs. For example, small sequential logical reads may be satisfied from the buffer cache, resulting in fewer physical IOs than logical IOs. Conversely, large logical IOs or small random IOs may result in more physical than logical IOs. Logical volume mappings, logical disk mirroring, and disk striping also tend to remove any correlation. On HP-UX, this is calculated as GBL_DISK_PHYS_READ = GBL_DISK_FS_READ + GBL_DISK_VM_READ + GBL_DISK_SYSTEM_READ + GBL_DISK_RAW_READ On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_READ_BYTE_RATE ---------------------------------- The average number of KBs transferred from the disk per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_READ_PCT ---------------------------------- The percentage of physical reads of total physical IO during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_READ_RATE ---------------------------------- The number of physical reads per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk reads are counted, including file system, virtual memory, and raw reads. On HP-UX, this is calculated as GBL_DISK_PHYS_READ_RATE = GBL_DISK_FS_READ_RATE + GBL_DISK_VM_READ_RATE + GBL_DISK_SYSTEM_READ_RATE + GBL_DISK_RAW_READ_RATE On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_WRITE ---------------------------------- The number of physical writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk writes are counted, including file system IO, virtual memory IO, and raw writes. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On HP-UX, there are many reasons why there is not a direct correlation between logical IOs and physical IOs. For example, small logical writes may end up entirely in the buffer cache, and later generate fewer physical IOs when written to disk due to the larger IO size. Or conversely, small logical writes may require physical prefetching of the corresponding disk blocks before the data is merged and posted to disk. Logical volume mappings, logical disk mirroring, and disk striping also tend to remove any correlation. On HP-UX, this is calculated as GBL_DISK_PHYS_WRITE = GBL_DISK_FS_WRITE + GBL_DISK_VM_WRITE + GBL_DISK_SYSTEM_WRITE + GBL_DISK_RAW_WRITE On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_WRITE_BYTE_RATE ---------------------------------- The average number of KBs transferred to the disk per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk writes are counted, including file system IO, virtual memory IO, and raw writes. On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_PHYS_WRITE_RATE ---------------------------------- The number of physical writes per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk writes are counted, including file system IO, virtual memory IO, and raw writes. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On HP-UX, this is calculated as GBL_DISK_PHYS_WRITE_RATE = GBL_DISK_FS_WRITE_RATE + GBL_DISK_VM_WRITE_RATE + GBL_DISK_SYSTEM_WRITE_RATE + GBL_DISK_RAW_WRITE_RATE On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_RAW_IO ---------------------------------- The total number of raw reads and writes during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Sun, tape drive accesses are included in raw IOs, but not in physical IOs. To determine if raw IO is tape access versus disk access, compare the global physical disk accesses to the total raw, block, and vm IOs. If the totals are the same, the raw IO activity is to a disk, floppy, or CD drive. Check physical IO data for each individual disk device to isolate a device. If the totals are different, there is raw IO activity to a non-disk device like a tape drive. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_RAW_IO_RATE ---------------------------------- The total number of raw reads and writes per second during the interval. Only accesses to local disk devices are counted. On Sun, tape drive accesses are included in raw IOs, but not in physical IOs. To determine if raw IO is tape access versus disk access, compare the global physical disk accesses to the total raw, block, and vm IOs. If the totals are the same, the raw IO activity is to a disk, floppy, or CD drive. Check physical IO data for each individual disk device to isolate a device. If the totals are different, there is raw IO activity to a non-disk device like a tape drive. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_RAW_READ ---------------------------------- The number of raw reads during the interval. Only accesses to local disk devices are counted. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_RAW_READ_RATE ---------------------------------- The number of raw reads per second during the interval. Only accesses to local disk devices are counted. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_RAW_WRITE ---------------------------------- The number of raw writes during the interval. Only accesses to local disk devices are counted. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_RAW_WRITE_RATE ---------------------------------- The number of raw writes per second during the interval. Only accesses to local disk devices are counted. On Sun, tape drive accesses are included in raw IOs, but not in physical IOs. To determine if raw IO is tape access versus disk access, compare the global physical disk accesses to the total raw, block, and vm IOs. If the totals are the same, the raw IO activity is to a disk, floppy, or CD drive. Check physical IO data for each individual disk device to isolate a device. If the totals are different, there is raw IO activity to a non-disk device like a tape drive. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_DISK_REQUEST_QUEUE ---------------------------------- The total length of all of the disk queues at the end of the interval. Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boottime, the operating system does not provide performance data for that device. This can be determined by checking the “by-disk” data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_SPACE ---------------------------------- The total disk capacity of the installed local fixed disk in megabytes. GBL_DISK_SPACE_FREE ---------------------------------- The total free space on all local, fixed disk partitions. The value is sampled every 30 seconds and the minimum sample in the recording Interval is reported. GBL_DISK_SUBSYSTEM_QUEUE ---------------------------------- The average number of processes or kernel threads blocked on the disk subsystem (in a “queue” waiting for their file system disk IO to complete) during the interval. This is the sum of processes or kernel threads in the DISK, INODE, CACHE and CDFS wait states. Processes or kernel threads doing raw IO to a disk are not included in this measurement. As this number rises, it is an indication of a disk bottleneck. This is calculated as the accumulated time that all processes or kernel threads spent blocked on (DISK + INODE + CACHE + CDFS) divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. GBL_DISK_SYSTEM_IO ---------------------------------- The number of physical disk IOs generated by the kernel for file system management (inode accesses or updates) during the interval. Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_SYSTEM_IO_RATE ---------------------------------- The number of physical disk IOs per second generated by the kernel for file system management (inode accesses or updates) during the interval. Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_SYSTEM_READ ---------------------------------- Number of physical disk reads generated by the kernel for file system management (inode accesses) during the interval. Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_SYSTEM_READ_RATE ---------------------------------- Number of physical disk reads per second generated by the kernel for file system management (inode accesses) during the interval. Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_SYSTEM_WRITE ---------------------------------- Number of physical disk writes generated by the kernel for file system management (inode updates) during the interval. Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_SYSTEM_WRITE_RATE ---------------------------------- Number of physical disk writes per second generated by the kernel for file system management (inode updates) during the interval. Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_TIME_PEAK ---------------------------------- The time, in seconds, during the interval that the busiest disk was performing IO transfers. This is for the busiest disk only, not all disk devices. This counter is based on an end-to-end measurement for each IO transfer updated at queue entry and exit points. Only local disks are counted in this measurement. NFS devices are excluded. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_UTIL ---------------------------------- On HP-UX, this is the average percentage of time during the interval that all disks had IO in progress from the point of view of the Operating System. This is the average utilization for all disks. On all other Unix systems, this is the average percentage of disk in use time of the total interval (that is, the average utilization). Only local disks are counted in this measurement. NFS devices are excluded. GBL_DISK_UTIL_PEAK ---------------------------------- The utilization of the busiest disk during the interval. On HP-UX, this is the percentage of time during the interval that the busiest disk device had IO in progress from the point of view of the Operating System. On all other systems, this is the percentage of time during the interval that the busiest disk was performing IO transfers. It is not an average utilization over all the disk devices. Only local disks are counted in this measurement. NFS devices are excluded. Some Linux kernels, typically 2.2 and older kernels, do not support the instrumentation needed to provide values for this metric. This metric will be “na” on the affected kernels. The “sar -d” command will also not be present on these systems. Distributions and OS releases that are known to be affected include: TurboLinux 7, SuSE 7.2, and Debian 3.0. A peak disk utilization of more than 50 percent often indicates a disk IO subsystem bottleneck situation. A bottleneck may not be in the physical disk drive itself, but elsewhere in the IO path. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_VM_IO ---------------------------------- The total number of virtual memory IOs made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On HP-UX, the IOs to user file data are not included in this metric unless they were done via the mmap(2) system call. On SUN, when a file is accessed, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On SUN, this metric is calculated by subtracting raw and block IOs from physical IOs. Tape drive accesses are included in the raw IOs, but not in the physical IOs. Therefore, when tape drive accesses are occurring on a system, all virtual memory and raw IO is counted as raw IO. For example, you may see heavy raw IO occurring during system backup. Raw IOs for disks are counted in the physical IOs. To determine if the raw IO is tape access versus disk access, compare the global physical disk accesses to the total of raw, block, and VM IOs. If the totals are the same, the raw IO activity is to a disk, floppy, or CD drive. Check physical IO data for each individual disk device to isolate a device. If the totals are different, there is raw IO activity to a non-disk device like a tape drive. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_VM_IO_RATE ---------------------------------- The number of virtual memory IOs per second made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On HP-UX, the IOs to user file data are not included in this metric unless they were done via the mmap(2) system call. On SUN, when a file is accessed, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On SUN, this metric is calculated by subtracting raw and block IOs from physical IOs. Tape drive accesses are included in the raw IOs, but not in the physical IOs. Therefore, when tape drive accesses are occurring on a system, all virtual memory and raw IO is counted as raw IO. For example, you may see heavy raw IO occurring during system backup. Raw IOs for disks are counted in the physical IOs. To determine if the raw IO is tape access versus disk access, compare the global physical disk accesses to the total of raw, block, and VM IOs. If the totals are the same, the raw IO activity is to a disk, floppy, or CD drive. Check physical IO data for each individual disk device to isolate a device. If the totals are different, there is raw IO activity to a non-disk device like a tape drive. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_DISK_VM_READ ---------------------------------- The number of virtual memory reads made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On HP-UX, the reads to user file data are not included in this metric unless they were accessed via the mmap(2) system call. On AIX System WPARs, this metric is NA. GBL_DISK_VM_READ_RATE ---------------------------------- The number of virtual memory reads per second made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On HP-UX, the reads to user file data are not included in this metric unless they were accessed via the mmap(2) system call. On AIX System WPARs, this metric is NA. GBL_DISK_VM_WRITE ---------------------------------- The number of virtual memory writes made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On HP-UX, the writes to user file data are not included in this metric unless they were done via the mmap(2) system call. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On AIX System WPARs, this metric is NA. GBL_DISK_VM_WRITE_RATE ---------------------------------- The number of virtual memory writes per second made during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On HP-UX, the writes to user file data are not included in this metric unless they were done via the mmap(2) system call. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On AIX System WPARs, this metric is NA. GBL_DISTRIBUTION ---------------------------------- The software distribution, if available. GBL_FLUSH ---------------------------------- Flush specifies the interval, in seconds, at which scope logs the application and device data classes even though the data does not meet the threshold conditions being set. Flush parameter is set in parm file. GBL_FS_SPACE_UTIL_PEAK ---------------------------------- The percentage of occupied disk space to total disk space for the fullest file system found during the interval. Only locally mounted file systems are counted in this metric. This metric can be used as an indicator that at least one file system on the system is running out of disk space. On Unix systems, CDROM and PC file systems are also excluded. This metric can exceed 100 percent. This is because a portion of the file system space is reserved as a buffer and can only be used by root. If the root user has made the file system grow beyond the reserved buffer, the utilization will be greater than 100 percent. This is a dangerous situation since if the root user totally fills the file system, the system may crash. On Windows, CDROM file systems are also excluded. On Solaris non-global zones, this metric shows data from the global zone. GBL_GMTOFFSET ---------------------------------- The difference, in minutes, between local time and GMT (Greenwich Mean Time). GBL_GUI_DELAY_INDEX ---------------------------------- A value ranging from 0 (fast) to 100 (slow) indicating the delay in processing Windows messages (Windows 3.11 only). Slow message processing (delays greater than around 20) indicates sluggish responses to mouse and keyboard actions. This measurement is used only on 16-bit Windows platforms. The metric GBL_GUI_INPUT_DELAY provides similar system responsiveness information on 32- bit platforms. GBL_GUI_INPUT_COUNT ---------------------------------- The number of keyboard strokes and mouse clicks during the interval. GBL_GUI_INPUT_DELAY ---------------------------------- The average delay in milliseconds in servicing keyboard strokes and mouse clicks. This metric is a general service measurement suitable for 32-bit platforms. It provides a “one number” indicator of the overall system performance seen by the user. The value should generally be close to zero. Although this metric may be reported for 16-bit platforms, it can be volatile and less reliable due to the lower system clock resolution on DOS-based Windows systems. The metric GBL_GUI_DELAY_INDEX performs a similar function on 16-bit platforms. This number is an average that is often influenced by single, lengthy delays. While normal delays may be less than a few ms, occasional delays (for example, during a large program load) may be several thousands of ms. Isolated long delay averages probably do not indicate poor service. Sustained average delays above a few ms probably do indicate poor service. GBL_GUI_INPUT_RATE ---------------------------------- The number of keyboard strokes and mouse clicks per minute. GBL_GUI_KEYBOARD_COUNT ---------------------------------- The number of keyboard strokes during the interval. GBL_GUI_KEYBOARD_RATE ---------------------------------- The number of keyboard strokes per minute. GBL_GUI_MOUSE_COUNT ---------------------------------- The number of mouse clicks and double clicks during the interval. GBL_GUI_MOUSE_RATE ---------------------------------- The number of mouse clicks and double clicks per minute. GBL_HYP_UTIL ---------------------------------- The percentage of time spent in Hypervisor by this partition in this interval with respect to system mode utilization. GBL_IGNORE_MT ---------------------------------- This boolean value indicates whether the CPU normalization is on or off. If the metric value is “true”, CPU related metrics in the global class will report values which are normalized against the number of active cores on the system. If the metric value is “false”, CPU related metrics in the global class will report values which are normalized against the number of CPU threads on the system. If CPU MultiThreading is turned off this configuration option is a no-op and the metric value will be “true”. On Linux, this metric will only report “true” if this configuration is on and if the kernel provides enough information to determine whether MultiThreading is turned on. On HPUX, this metric will report “na” if the processor doesn’t support the feature. GBL_INTERRUPT ---------------------------------- The number of IO interrupts during the interval. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_INTERRUPT_RATE ---------------------------------- The average number of IO interrupts per second during the interval. On HPUX and SUN this value includes clock interrupts. To get non-clock device interrupts, subtract clock interrupts from the value. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_INTERVAL ---------------------------------- The amount of time in the interval. This measured interval is slightly larger than the desired or configured interval if the collection program is delayed by a higher priority process and cannot sample the data immediately. GBL_IPC_SUBSYSTEM_QUEUE ---------------------------------- The average number of processes or kernel threads blocked on the InterProcess Communication (IPC) subsystems (waiting for their interprocess communication activity to complete) during the interval. This is the sum of processes or kernel threads in the IPC, MSG, SEM, PIPE, SOCKT (that is, sockets) and STRMS (that is, streams IO) wait states. This is calculated as the accumulated time that all processes or kernel threads spent blocked on (IPC + MSG + SEM + PIPE + SOCKT + STRMS) divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. GBL_JAVAARG ---------------------------------- This boolean value indicates whether the java class overloading mechanism is enabled or not. This metric will be set when the javaarg flag in the parm file is set. The metric affected by this setting is PROC_PROC_ARGV1. This setting is useful to construct parm file java application definitions using the argv1= keyword. GBL_LOADAVG ---------------------------------- The 1 minute load average of the system obtained at the time of logging. On windows this is the load average of the system over the interval. Load average on windows is the average number of threads that have been waiting in ready state during the interval. This is obtained by checking the number of threads in ready state every sub proc interval, accumulating them over the interval and averaging over the interval. On Solaris non-global zones, this metric shows data from the global zone. GBL_LOADAVG15 ---------------------------------- The 15 minute load average of the system obtained at the time of logging. GBL_LOADAVG5 ---------------------------------- The 5 minute load average of the system obtained at the time of logging. On Solaris non-global zones, this metric shows data from the global zone. GBL_LOGFILE_VERSION ---------------------------------- Three byte ASCII field containing the log file version number. The log file version is assigned by scopeux and is incremented when changes to the log file causes the layout to be different from previous versions. The current version is “ D”. Every effort is made to protect the information investment maintained in historical log files by providing forward compatibility and/or conversion utilities when log files change. GBL_LOGGING_TYPES ---------------------------------- A 13-byte field indicating the types of data logged by the collector. This is controlled by the LOG statement in the parm file. Each position will contain either a space or the characters as shown below. Note that positions two (all applications) and four (all processes) were implemented for HP internal use only and are not normally used outside of HP. An @ in position two indicates that all applications are logged each five minute interval even if they had no activity during the interval. An @ in position four indicates that all processes, not just the interesting ones, are logged each one minute interval. This can result in very large log files.An @ in position 6 indicates all devices( File System Device,Disk,CPU,LAN,Logical Volume) are logged. Position Char Meaning 1 G Global data 2 @ All applications 3 A Applications 4 @ All processes 5 P Interesting processes 6 @ All Devices 7 F File System Device 8 D Disk 9 C CPU 10 L LAN 11 V Logical Volume 12 T Transaction data 13 space Not used DEC Note: Position 9, Transaction data, is not implemented. HP-UX SunOS AIX DEC By default, global, interesting process, LAN data is logged, in which case this field would be “ G P L”. GBL_LOST_MI_TRACE_BUFFERS ---------------------------------- The number of trace buffers lost by the measurement processing daemon. On HP-UX systems, if this value is > 0, the measurement subsystem is not keeping up with the system events that generate traces. For other Unix systems, if this value is > 0, the measurement subsystem is not keeping up with the ARM API calls that generate traces. Note: The value reported for this metric will roll over to 0 once it crosses INTMAX. GBL_LS_CPU_NUM_DEDICATED ---------------------------------- Number of processor units in dedicated partitions. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_CPU_NUM_SHARED ---------------------------------- Number of processor units in shared partitions. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_ID ---------------------------------- On AIX LPAR, this metric indicates partition number and is equivalent to “Partition Number” field of ‘lparstat -i’ command. On a standalone system the value of this metrics is ‘na’ On AIX System WPARs, this metric is NA. GBL_LS_MODE ---------------------------------- Indicates whether the CPU entitlement for the logical system is Capped or Uncapped. AIX The value “Uncapped” indicates that the logical system can utilize idle cycles from the shared processor pool of CPUs beyond its CPU entitlement. On AIX SPLPAR, this metric is same as “Mode” field of ‘lparstat -i’ command. Linux WinNT On a recognized VMware ESX guest, where VMware guest SDK is enabled, the value is “Uncapped” if maximum CPU entitlement (GBL_CPU_ENTL_MAX) is unlimited. Else, the value is always “Capped”. GBL_LS_NUM_CAPPED ---------------------------------- Number of Capped shared partitions. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_NUM_DEDICATED ---------------------------------- Number of partitions which have dedicated processors. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_NUM_SHARED ---------------------------------- Number of partitions which share the processors. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_NUM_UNCAPPED ---------------------------------- Number of Uncapped shared partitions. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_PHYS_MEM_CONSUMED ---------------------------------- The physical memory (in MBs) that is consumed by partitions. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_PHYS_MEM_TOTAL ---------------------------------- Total physical memory (in MBs) allotted across all the partitions. This metric is with respect to the partitions which are responding over network. On AIX System WPARs, this metric is NA. GBL_LS_ROLE ---------------------------------- Indicates whether Perf Agent is installed on Logical system or host or standalone system. This metric will be either “GUEST”, “HOST” or “STAND”. GBL_LS_SHARED ---------------------------------- In a virtual environment, this metric indicates whether the physical CPUs are dedicated to this Logical system or shared. On AIX SPLPAR, this metric is equivalent to “Type” field of ‘lparstat -i’ command. On a recognized VMware ESX guest, where VMware guest SDK is enabled, the value is “Shared”. On a standalone system the value of this metrics is “Dedicated”. On AIX System WPARs, this metric is NA. GBL_LS_TYPE ---------------------------------- The virtulization technology if applicable. The value of this metric is “HPVM” on HP-UX host, “LPAR” on AIX LPAR, “Sys WPAR” on system WPAR, “Zone” on Solaris Zones, “VMware” on recognized VMware ESX guest and VMware ESX Server console, “Hyper-V” on Hyper-V host, else “NoVM”. In conjunction with GBL_LS_ROLE this metric could be used to identify the environment in which Perf Agent/Glance is running. For example, if GBL_LS_ROLE is “Guest” and GBL_LS_TYPE is “VMware” then PA/Glance is running on a VMware Guest. GBL_LS_UUID ---------------------------------- UUID of this logical system. This Id uniquely identifies this logical system in the virtualized enviroments. On a standalone system the value of this metrics is ‘na’. GBL_LV_THRESHOLD ---------------------------------- lvthreshold specifies the thresholds for LOGICALVOLUME class. This is the number of IOs per second done by logical volume (LV_READ_RATE + LV_WRITE_RATE). This threshold value is supplied by the parm file. A logicalvolume must exceed this threshold value in any given interval before it will be considered interesting to be logged. GBL_MACHINE ---------------------------------- An ASCII string representing the Processor Architecture. And machine hardware model is represented by GBL_MACHINE_MODEL metric. Win3x/95 A text string representing the type of the computer. For example, “80686”. GBL_MACHINE_MEM_USED ---------------------------------- The amount of physical host memory currently consumed for this logical system’s physical memory. On a standalone system, the value will be (GBL_MEM_UTIL * GBL_MEM_PHYS) / 100 GBL_MACHINE_MODEL ---------------------------------- The CPU model. This is similar to the information returned by the GBL_MACHINE metric and the uname command(except for Solaris 10 x86/x86_64). However, this metric returns more information on some processors. On HP-UX, this is the same information returned by the model command. GBL_MEM_ACTIVE_VIRT ---------------------------------- The total virtual memory (in MBs unless otherwise specified) allocated for processes that are currently on the run queue or processes that have executed recently. This is the sum of the virtual memory sizes of the data and stack regions for these processes. On HP-UX, this is the sum of the virtual memory of all processes which have had a thread run in the last 20 seconds. On AIX System WPARs, this metric is NA. GBL_MEM_ACTIVE_VIRT_UTIL ---------------------------------- The percentage of total virtual memory active at the end of the interval. Active virtual memory is the virtual memory associated with processes that are currently on the run queue or processes that have executed recently. This is the sum of the virtual memory sizes of the data and stack regions for these processes. On HP-UX, this is the sum of the virtual memory of all processes which have had a thread run in the last 20 seconds. GBL_MEM_ARC_UTIL ---------------------------------- The percentage of physical memory used by ZFS ARC during the interval. On SUN, the buffer cache is a memory pool used by the system to cache inode, indirect block and cylinder group related disk accesses. This is different from the traditional concept of a buffer cache that also holds file system data. On Solaris 5.X, as file data is cached, accesses to it show up as virtual memory IOs. File data caching occurs through memory mapping managed by the virtual memory system, not through the buffer cache. The “nbuf” value is dynamic, but it is very hard to create a situation where the memory cache metrics change, since most systems have more than adequate space for inode, indirect block, and cylinder group data caching. This cache is more heavily utilized on NFS file servers. GBL_MEM_AVAIL ---------------------------------- The amount of physical available memory in the system (in MBs unless otherwise specified). On Windows, memory resident operating system code and data is not included as available memory. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_CACHE ---------------------------------- The amount of physical memory (in MBs unless otherwise specified) used by the buffer cache during the interval. On HP-UX 11i v2 and below, the buffer cache is a memory pool used by the system to stage disk IO data for the driver. On HP-UX 11i v3 and above this metric value represents the usage of the file system buffer cache which is still being used for file system metadata. On SUN, this value is obtained by multiplying the system page size times the number of buffer headers (nbuf). For example, on a SPARCstation 10 the buffer size is usually (200 (page size buffers) * 4096 (bytes/page) = 800 KB). If ZFS is configured, this includes ZFS ARC cache usage during the interval. On SUN, the buffer cache is a memory pool used by the system to cache inode, indirect block and cylinder group related disk accesses. This is different from the traditional concept of a buffer cache that also holds file system data. On Solaris 5.X, as file data is cached, accesses to it show up as virtual memory IOs. File data caching occurs through memory mapping managed by the virtual memory system, not through the buffer cache. The “nbuf” value is dynamic, but it is very hard to create a situation where the memory cache metrics change, since most systems have more than adequate space for inode, indirect block, and cylinder group data caching. This cache is more heavily utilized on NFS file servers. On AIX, this value should be minimal since most disk IOs are done through memory mapped files. GBL_MEM_CACHE_FLUSH_RATE ---------------------------------- The rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request. GBL_MEM_CACHE_HIT_PCT ---------------------------------- On HP-UX, the percentage of buffer cache reads resolved from the buffer cache (rather than going to disk) during the interval. Buffer cache reads can occur as a result of a logical read (for example, file read system call), a read generated by a client, a read-ahead on behalf of a logical read or a system procedure. On HP-UX, this metric is obtained by measuring the number of buffered read calls that were satisfied by the data that was in the file system buffer cache. Reads to filesystem file buffers that are not in the buffer cache result in disk IO. Reads to raw IO and virtual memory IO (including memory mapped files), do not go through the filesystem buffer cache, and so are not relevant to this metric. On HP-UX, a low cache hit rate may indicate low efficiency of the buffer cache, either because applications have poor data locality or because the buffer cache is too small. Overly large buffer cache sizes can lead to a memory bottleneck. The buffer cache should be sized small enough so that pageouts do not occur even when the system is busy. However, in the case of VxFS, all memory-mapped IOs show up as page ins/page outs and are not a result of memory pressure. On AIX, the percentage of disk reads that were satisfied in the file system buffer cache (rather than going to disk) during the interval. On AIX, the traditional file system buffer cache is not normally used, since files are implicitly memory mapped and the access is through the virtual memory system rather than the buffer cache. However, if a file is read as a block device (e.g /dev/hdisk1), the file system buffer cache is used, making this metric meaningful in that situation. If no IO through the buffer cache occurs during the interval, this metric is 0. On the remaining Unix systems, this is the percentage of logical reads satisfied in memory (rather than going to disk) during the interval. This includes inode, indirect block and cylinder group related disk reads, plus file reads from files memory mapped by the virtual memory IO system. On Windows, this is the percentage of buffered reads satisfied in the buffer cache (rather than going to disk) during the interval. This metric is obtained by measuring the number of buffered read calls that were satisfied by the data that was in the system buffer cache. Reads that are not in the buffer cache result in disk IO. Unbuffered IO and virtual memory IO (including memory mapped files), are not counted in this metric. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. Win3x/95 The percentage of IO requests satisfied in the cache (rather than going to disk) during the interval. This value is reported for Windows 3.11 using SmartDrive. It is not available for Windows for Workgroups 3.11 systems using 32-bit file access. GBL_MEM_CACHE_UTIL ---------------------------------- The percentage of physical memory used by the buffer cache during the interval. On HP-UX 11i v2 and below, the buffer cache is a memory pool used by the system to stage disk IO data for the driver. On HP-UX 11i v3 and above this metric value represents the usage of the file system buffer cache which is still being used for file system metadata. On SUN, this percentage is based on calculating the buffer cache size by multiplying the system page size times the number of buffer headers (nbuf). For example, on a SPARCstation 10 the buffer size is usually (200 (page size buffers) * 4096 (bytes/page) = 800 KB). If ZFS is configured, this includes ZFS ARC cache utilization during the interval. On SUN, the buffer cache is a memory pool used by the system to cache inode, indirect block and cylinder group related disk accesses. This is different from the traditional concept of a buffer cache that also holds file system data. On Solaris 5.X, as file data is cached, accesses to it show up as virtual memory IOs. File data caching occurs through memory mapping managed by the virtual memory system, not through the buffer cache. The “nbuf” value is dynamic, but it is very hard to create a situation where the memory cache metrics change, since most systems have more than adequate space for inode, indirect block, and cylinder group data caching. This cache is more heavily utilized on NFS file servers. On AIX, this value should be minimal since most disk IOs are done through memory mapped files. On Windows the value reports ‘copy read hit %’ and ‘Pin read hit %’. GBL_MEM_CACHE_WRITE_HIT ---------------------------------- The number of write cache hits - logical writes that did not result in physical IOs during the interval. A cache write hit occurs when a logical write request is issued to a disk file block that is already mapped in a buffer that is in a delayed write state. This metric gives an indication of how many physical IOs are eliminated as a result of buffering logical write requests. Physical IOs are eliminated in environments where asynchronous writes are done (see the O_SYNC flag in open(2)) to the same file blocks before being explicitly written to the disk or flushed to disk by the syncher process. Environments that attempt to minimize the chance of file system data loss by issuing synchronous writes or by using shorter syncer intervals will see fewer cache write hits. During a short interval, the number of physical writes can exceed the number of logical write requests. This would yield a negative number of “write hits”. If this occurs in an interval, “na” will be returned. GBL_MEM_CACHE_WRITE_HIT_PCT ---------------------------------- The percentage of logical disk writes that did not result in physical disk IOs during the interval. A cache write hit occurs when a logical write request is issued to a disk file block that is already mapped in a buffer that is in a delayed write state. This metric gives an indication of how many physical IOs are eliminated as a result of buffering logical write requests. Physical IOs are eliminated in environments where asynchronous writes are done (see the O_SYNC flag in open(2)) to the same file blocks before being explicitly written to the disk or flushed to disk by the syncher process. Environments that attempt to minimize the chance of file system data loss by issuing synchronous writes or by using shorter syncer intervals will see fewer cache write hits. During a short interval, the number of physical writes can exceed the number of logical write requests. This would yield a negative number of “write hits”. If this occurs in an interval, “na” will be returned. GBL_MEM_COMMIT_PCT ---------------------------------- On Windows 3.11, this is the sum of allocated swap space and allocated RAM memory expressed as a percentage of available RAM memory. On Windows 95, this is the amount of committed virtual storage expressed as a percentage of available RAM memory. GBL_MEM_DATAMAP_HIT_PCT ---------------------------------- The percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory. GBL_MEM_DISCARD ---------------------------------- The total number of discards in the interval (Windows 95 only). GBL_MEM_DISCARD_RATE ---------------------------------- The number of pages discarded from memory per second. (The pages aren’t swapped to the disk because the information is already on the disk.) A high rate is an important indicator of memory pressure (Windows 95 only). GBL_MEM_DNLC_HIT_PCT ---------------------------------- The percentage of time a pathname component was found in the directory name lookup cache (rather than requiring a disk read to find a file) during the interval. On HP-UX, the directory name lookup cache is used to minimize sequential searches through directory entries for pathname components during pathname to inode translations. Such translations are done whenever a file is accessed through its filename. The cache holds the inode cache table offset for recently referenced pathname components. Pathname components that exceed 15 characters are not cached. Any HP-UX system call that includes a path parameter can result in directory name lookup cache activity, including but not limited to system calls such as open, stat, exec, lstat, unlink. Each component of a path parameter is parsed and converted to an inode separately, therefore several dnlc hits per path are possible. High directory name cache hit rates on HP-UX will be seen on systems where pathname component requests are frequently repeated. For example, when users or applications work in the same directory where they repeatedly list or open the same files, cache hit rates will be high. Unusually low cache hit rates might be seen on HP-UX systems where users or applications access many different directories in no particular pattern. Low cache hit rates can also be an indicator of an underconfigured inode cache. When an inode cache is too small, the kernel will more frequently have to flush older inode cache and their corresponding directory name cache entries in order to make room for new inode cache entries. On HP-UX, the directory name lookup cache is static in size and is allocated in kernel memory. As a result, it is not affected by user memory constraints. The size of the cache is stored in the kernel variable “ncsize” and is not directly tunable by the system administrator; however, it can be changed indirectly by tuning other tables used in the formula to compute the “ncsize”. The formula is: ncsize = MAX(((nproc+16+maxusers)+ 32+(2*npty)),ninode) Note that ncsize is always >= ninode which is the default size of the inode cache. This is because the directory name cache contains inode table offsets for each cached pathname component. On SUN, long file names (greater than 30 characters) are not cached and are a type of cache miss. “Enters”, or cache data updates, are not included in this data. The DNLC size is: (maxusers * 17) + 90 On Solaris non-global zones, this metric shows data from the global zone. GBL_MEM_ENTL_MAX ---------------------------------- In a virtual environment, this metric indicates the maximum amount of memory configured for this logical system. The value is -3 if entitlement is ‘Unlimited’ for this logical system. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na” On Solaris non-global zones, this metric value is equivalent to ‘capped- memory’ value for ‘zonecfg -z zonename info’ command. On a standalone system this metric is equivalent to GBL_MEM_PHYS. GBL_MEM_ENTL_MIN ---------------------------------- In a virtual environment, this metric indicates the minimum amount of memory configured for this logical system. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na” On a standalone system, this metrics is equivalent to GBL_MEM_PHYS. GBL_MEM_ENTL_UTIL ---------------------------------- In a virtual environment, this metric indicates the maximum amount of memory utilized against memory configured for this logical system. GBL_MEM_FAULT_RATE ---------------------------------- The number of page faults per second. Page faults occur when a virtual storage linear address is accessed whose corresponding real storage page is not present. A page fault may require disk IO to PAGE IN the missing virtual storage. Disk IO may also be required to PAGE OUT virtual storage already in memory to make room for the new page. Alternatively, the page may be RECLAIMED from lists of pages waiting to be paged out or reused. (In this case, no disk IO occurs.) On a 386 Enhanced Mode system with a swap file, page faulting is an important indicator of memory pressure. Page faulting is caused by a combination of memory over commitment, program memory reference patterns (working set), and the frequency with which the user swaps between applications. GBL_MEM_FILE_PAGEIN_RATE ---------------------------------- The number of page ins from the file system per second during the interval. On Solaris, this is the same as the “fpi” value from the “vmstat -p” command, divided by page size in KB. On Linux, the value is reported in kilobytes and matches the ‘io/bi’ values from vmstat. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_FILE_PAGEOUT_RATE ---------------------------------- The number of page outs to the file system per second during the interval. On Solaris, this is the same as the “fpo” value from the “vmstat -p” command, divided by page size in KB. On Linux, the value is reported in kilobytes and matches the ‘io/bo’ values from vmstat. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_FILE_PAGE_CACHE ---------------------------------- The amount of physical memory (in MBs unless otherwise specified) used by the file cache during the interval. File cache is a memory pool used by the system to stage disk IO data for the driver. This metric is supported on HP-UX 11iv3 and above. The filecache_min and filecache_max tunables control the filecache memory usage on the system. The filecache_min tunable specifies the amount of physical memory that is guaranteed to be available for filecache on the system. The filecache memory usage can grow beyond filecache_min, up to the limit set by the filecache_max tunable. The Virtual Memory(VM) subsystem always pre reserves ‘filecache_min’ tunable value worth of pages on the system for filecache, even in the case of filecache under utilization (actual filecache utilization < filecache_min value). This preserved memory by the VM is not available for the user. In this scenario, this metric will show the ‘filecache_min’ as the filecache value, rather than showing the actual filecache utilization. On Linux, this metric is equal to ‘cached’ value of ‘free -m’ command output. GBL_MEM_FILE_PAGE_CACHE_UTIL ---------------------------------- The percentage of physical_memory used by the file cache during the interval. File cache is a memory pool used by the system to stage disk IO data for the driver. This metric is supported on HP-UX 11iv3 and above. The filecache_min and filecache_max tunables control the filecache memory usage on the system. The filecache_min tunable specifies the amount of physical memory that is guaranteed to be available for filecache on the system. The filecache memory usage can grow beyond filecache_min, up to the limit set by the filecache_max tunable. The Virtual Memory(VM) subsystem always pre reserves ‘filecache_min’ tunable value worth of pages on the system for filecache, even in the case of filecache under utilization (actual filecache utilization < filecache_min value). This preserved memory by the VM is not available for the user. In this scenario, this metric will show the ‘filecache_min’ as the filecache value, rather than showing the actual filecache utilization. On Linux, this metric is derived from ‘cached’ value of ‘free -m’ command output. GBL_MEM_FREE ---------------------------------- The amount of memory not allocated (in MBs unless otherwise specified). As this value drops, the likelihood increases that swapping or paging out to disk may occur to satisfy new memory requests. On SUN, low values for this metric may not indicate a true memory shortage. This metric can be influenced by the VMM (Virtual Memory Management) system. On uncapped solaris zones, the metric indicates the amount of memory that is available across the whole system that is not consumed by the global zone and other non-global zones. In case of capped solaris zones, the metric indicates the amount of memory that is not consumed by this zone against the memory cap set. On Linux, this metric is sum of ‘free’ and ‘cached’ memory. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. Locality Domain metrics are available on HP-UX 11iv2 and above. GBL_MEM_FREE and LDOM_MEM_FREE, as well as the memory utilization metrics derived from them, may not always fully match. GBL_MEM_FREE represents free memory in the kernel’s reservation layer while LDOM_MEM_FREE shows actual free pages. If memory has been reserved but not actually consumed from the Locality Domains, the two values won’t match. Because GBL_MEM_FREE includes pre-reserved memory, the GBL_MEM_* metrics are a better indicator of actual memory consumption in most situations. GBL_MEM_FREE_UTIL ---------------------------------- The percentage of physical memory that was free at the end of the interval. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_GDIRES_FREE ---------------------------------- The smallest value returned from a monitoring interval that represents a percentage of the Graphics Device Interface resources still free. Windows 3.11 provides only limited space in its Graphics Device Interface and User modules to hold the handles (memory identifiers) that describe window objects and other program items. GBL_MEM_LOAD_INDEX ---------------------------------- The level of memory use according to a number (Memory Load index) obtained from the Windows 95 operating system. This number is calculated internally by the operating system. A number of 0 indicates no memory use and a number of 100 indicates full memory use. The monitor samples this value every 30 seconds and reports the maximum of the samples recorded during the measurement interval. (The calculation compares committed memory to physical memory. When committed memory is equal to physical memory, it reports 0; when committed memory is 2 times physical memory, it reports 100.) GBL_MEM_LOCKED ---------------------------------- The amount of physical memory (in KBs unless otherwise specified) marked as locked memory at the end of the interval. This includes memory locked by processes, kernel and driver code, and can not exceed available physical memory on the system. This is the total non-paged pool memory usage. This memory is allocated from the system-wide non-paged pool, and is not affected by the pageout process. The kernel and driver code use the non-paged pool for data that should always be in physical memory. The size of the non-paged pool is limited to the approximately 128 MB on Windows NT systems and to 256 MB on Windows 2000 systems. A failure to allocate memory from the non-paged pool can cause a system crash. GBL_MEM_LOCKED_UTIL ---------------------------------- The percentage of physical memory marked as locked memory at the end of the interval. This includes memory locked by processes, kernel and driver code. This is the total non-paged pool memory usage. This memory is allocated from the system-wide non-paged pool, and is not affected by the pageout process. The kernel and driver code use the non-paged pool for data that should always be in physical memory. The size of the non-paged pool is limited to the approximately 128 MB on Windows NT systems and to 256 MB on Windows 2000 systems. A failure to allocate memory from the non-paged pool can cause a system crash. GBL_MEM_ONLINE ---------------------------------- In a virtual environment, this metric indicates the amount of memory currently online for this logical system. For AIX wpars, this metric will be “na”. GBL_MEM_OVERHEAD ---------------------------------- The amount of “overhead” memory associated with this logical system that is currently consumed on the host system. On VMware ESX Server console, the value is equivalent to sum of the current overhead memory for all running virtual machines On a standalone system, the value will be 0. On a recognized VMware ESX guest, where VMware guest SDK is disabled, the value is “na”. GBL_MEM_PAGEIN ---------------------------------- The total number of page ins from the disk during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. On HP-UX, this is the same as the “page ins” value from the “vmstat -s” command. On AIX, this is the same as the “paging space page ins” value. Remember that “vmstat -s” reports cumulative counts. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. Win3x/95 The total number of page-in operations in the interval (Windows 95 only). GBL_MEM_PAGEIN_BYTE ---------------------------------- The number of KBs (or MBs if specified) of page ins during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. GBL_MEM_PAGEIN_BYTE_RATE ---------------------------------- The number of KBs per second of page ins during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. GBL_MEM_PAGEIN_RATE ---------------------------------- The total number of page ins per second from the disk during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. On HP-UX and AIX, this is the same as the “pi” value from the vmstat command. On Solaris, this is the same as the sum of the “epi” and “api” values from the “vmstat -p” command, divided by the page size in KB. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. Win3x/95 The number of pages swapped into memory per second, including pages loaded from (Win32) executable or other memory-mapped files (Windows 95 only). Because this count includes program load or memory mapped file activity, it does not necessarily indicate a shortage of memory. GBL_MEM_PAGEOUT ---------------------------------- The total number of page outs to the disk during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. On HP-UX, this is the same as the “page outs” value from the “vmstat -s” command. On HP-UX 11iv3 and above this includes filecache page outs also. On AIX, this is the same as the “paging space page outs” value. Remember that “vmstat -s” reports cumulative counts. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. Win3x/95 The total number of page outs to the disk during the interval (Windows 95 only). GBL_MEM_PAGEOUT_BYTE ---------------------------------- The number of KBs (or MBs if specified) of page outs during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PAGEOUT_BYTE_RATE ---------------------------------- The number of KBs (or MBs if specified) per second of page outs during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PAGEOUT_RATE ---------------------------------- The total number of page outs to the disk per second during the interval. On HP-UX, Solaris, Linux and AIX, this reflects paging activity between memory and paging space. It does not include activity between memory and file systems. On Windows, this includes paging activity for both file systems and paging space. On HP-UX and AIX, this is the same as the “po” value from the vmstat command. On Solaris, this is the same as the sum of the “epo” and “apo” values from the “vmstat -p” command, divided by the page size in KB. On Windows, this counter also includes paging traffic on behalf of the system cache to access file data for applications and so may be high when there is no memory pressure. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. Win3x/95 The total number of page outs to the disk during the interval (Windows 95 only). GBL_MEM_PAGE_FAULT ---------------------------------- The number of page faults that occurred during the interval. On Linux this metric is available only on 2.6 and above kernel versions. GBL_MEM_PAGE_FAULT_RATE ---------------------------------- The number of page faults per second during the interval. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PAGE_REQUEST ---------------------------------- The number of page requests to or from the disk during the interval. On HP-UX, Solaris, and AIX, this includes pages paged to or from the paging space and not to the file system. On Windows, this includes pages paged to or from both paging space and the file system. On HP-UX, this is the same as the sun of the “page ins” and “page outs” values from the “vmstat -s” command. On AIX, this is the same as the sum of the “paging space page ins” and “paging space page outs” values. Remember that “vmstat -s” reports cumulative counts. On Windows, this counter also includes paging traffic on behalf of the system cache to access file data for applications and so may be high when there is no memory pressure. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PAGE_REQUEST_RATE ---------------------------------- The number of page requests to or from the disk per second during the interval. On HP-UX, Solaris, and AIX, this includes pages paged to or from the paging space and not to or from the file system. On Windows, this includes pages paged to or from both paging space and the file system. On HP-UX and AIX, this is the same as the sum of the “pi” and “po” values from the vmstat command. On Solaris, this is the same as the sum of the “epi”, “epo”, “api”, and “apo” values from the “vmstat -p” command, divided by the page size in KB. Higher than normal rates can indicate either a memory or a disk bottleneck. Compare GBL_DISK_UTIL_PEAK and GBL_MEM_UTIL to determine which resource is more constrained. High rates may also indicate memory thrashing caused by a particular application or set of applications. Look for processes with high major fault rates to identify the culprits. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PG_SCAN ---------------------------------- The number of pages scanned by the pageout daemon (or by the Clock Hand on AIX) during the interval. The clock hand algorithm is used to control page aging on the system. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PG_SCAN_RATE ---------------------------------- The number of pages scanned per second by the pageout daemon (or by the Clock Hand on AIX, “vmstat -s” pages examined by clock) during the interval. The clock hand algorithm is used to control page aging on the system. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_PG_STEAL_RATE ---------------------------------- The number of pages stolen per second by the Virtual Memory Manager during the interval. GBL_MEM_PHYS ---------------------------------- The amount of physical memory in the system (in MBs unless otherwise specified). On HP-UX, banks with bad memory are not counted. Note that on some machines, the Processor Dependent Code (PDC) code uses the upper 1MB of memory and thus reports less than the actual physical memory of the system. Thus, on a system with 256MB of physical memory, this metric and dmesg(1M) might only report 267,386,880 bytes (255MB). This is all the physical memory that software on the machine can access. On Windows, this is the total memory available, which may be slightly less than the total amount of physical memory present in the system. This value is also reported in the Control Panel’s About Windows NT help topic. On Linux, this is the amount of memory given by dmesg(1M). If the value is not available in kernel ring buffer, then the sum of system memory and available memory will be reported as physical memory. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. Win3x/95 This will be smaller than the installed RAM, as it does not include real mode drivers and other memory resident programs. GBL_MEM_PHYS_MB ---------------------------------- The amount of physical memory in the system (in MB unless otherwise specified). This will be smaller than the installed RAM, as it does not include real mode drivers and other memory resident programs. GBL_MEM_PHYS_SWAPPED ---------------------------------- On a recognized VMware ESX guest, where VMware guest SDK is enabled, this metrics indicates the amount of memory that has been reclaimed by ESX Server from this logical system by transparently swapping logical system’s memory to disk. The value is “na” otherwise. GBL_MEM_QUEUE ---------------------------------- The average number of processes or kernel threads blocked on memory (waiting for virtual memory disk accesses to complete) during the interval. This typically happens when processes or kernel threads are allocating a large amount of memory. It can also happen when processes or kernel threads access memory that has been paged out to disk (swap) because of overall memory pressure on the system. Note that large programs can block on VM disk access when they are initializing, bringing their text and data pages into memory. When this metric rises, it can be an indication of a memory bottleneck, especially if overall system memory utilization (GBL_MEM_UTIL) is near 100% and there is also swapout or page out activity. This is calculated as the accumulated time that all processes or kernel threads spent blocked on memory divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. GBL_MEM_SHARES_PRIO ---------------------------------- The weightage/priority for memory assigned to this logical system. This value influences the share of unutilized physical Memory that this logical system can utilize. On a recognized VMware ESX guest, where VMware guest SDK is enabled, this value can range from 0 to 100000. The value will be “na” otherwise. GBL_MEM_SWAP ---------------------------------- The total number of swap ins and swap outs (or deactivations and reactivations on HP-UX) during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. SunOS The total number of swap ins and swap outs during the interval. On SUN systems, this metric is only available on SunOS 4.1.X. GBL_MEM_SWAPIN_BYTE ---------------------------------- The number of KBs transferred in from disk due to swap ins (or reactivations on HP-UX) during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_SWAPIN_BYTE_RATE ---------------------------------- The number of KBs per second transferred from disk due to swap ins (or reactivations on HP-UX) during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_SWAPIN_RATE ---------------------------------- The number of swap ins (or reactivations on HP-UX) per second during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_SWAPOUT_BYTE ---------------------------------- The number of KBs (or MBs if specified) transferred out to disk due to swap outs (or deactivations on HP-UX) during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_SWAPOUT_BYTE_RATE ---------------------------------- The number of KBs (or MBs if specified) per second transferred out to disk due to swap outs (or deactivations on HP-UX) during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_SWAPOUT_RATE ---------------------------------- The number of swap outs (or deactivations on HP-UX) per second during the interval. On Linux and AIX, swap metrics are equal to the corresponding page metrics. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. On Solaris non-global zones with Uncapped Memory scenario, this metric value is same as seen in global zone. GBL_MEM_SWAP_1_HR_RATE ---------------------------------- HP-UX The number of deactivations/reactivations per hour during the interval. On HP-UX, process swapping was replaced by a combination of paging and deactivation. Process deactivation occurs when the system is thrashing or when the amount of free memory falls below a critical level. The swapper then marks certain processes for deactivation and removes them from the run queue. Pages within the associated memory regions are reused or paged out by the memory management vhand process in favor of pages belonging to processes that are not deactivated. Unlike traditional process swapping, deactivated memory pages may or may not be written out to the swap area, because a process could be reactivated before the paging occurs. To summarize, a process swap-out on HP-UX is a process deactivation. A swap- in is a reactivation of a deactivated process. Swap metrics that report swap- out bytes now represent bytes paged out to swap areas from deactivated regions. Because these pages are pushed out over time based on memory demands, these counts are much smaller than HP-UX 9.x counts where the entire process was written to the swap area when it was swapped-out. Likewise, swap- in bytes now represent bytes paged in as a result of reactivating a deactivated process and reading in any pages that were actually paged out to the swap area while the process was deactivated. SunOS The number of swap ins and swap outs per hour during the interval (on SunOS 4.1.3 only). This metric is not on SunOS 5.x as swap in and swap out statistics are counted as paging. This metric does not necessarily indicate memory pressure, because it also records inactive processes undergoing soft swap-ins where pages are reclaimed from the freelist without generating disk activity. GBL_MEM_SWAP_QUEUE ---------------------------------- The average number of processes waiting to be swapped in. These processes are inactive because they are waiting for pages to be paged in. This is the same as the “procs b” field reported in vmstat. GBL_MEM_SYS ---------------------------------- The amount of physical memory (in MBs unless otherwise specified) used by the system (kernel) during the interval. System memory does not include the buffer cache. On HP-UX and Linux this does not include filecache also. On HP-UX 11.0, this metric does not include some kinds of dynamically allocated kernel memory. This has always been reported in the GBL_MEM_USER* metrics. On HP-UX 11.11 and beyond, this metric includes some kinds of dynamically allocated kernel memory. On Solaris non-global zones, this metric shows value as 0. GBL_MEM_SYSRES_FREE ---------------------------------- The lesser of USER and Graphics Device Interface resources free. This is a significant measurement for Windows 3.11 systems. These systems often become unstable when resources fall to low values. Windows will not start new tasks and will issue “Out of Memory” messages if the free percentage falls below 10%. GBL_MEM_SYS_AND_CACHE_UTIL ---------------------------------- The percentage of physical memory used by the system (kernel) and the buffer cache at the end of the interval. On HP-UX 11iv3, this includes file cache also. On HP-UX 11.0, this metric does not include some kinds of dynamically allocated kernel memory. This has always been reported in the GBL_MEM_USER* metrics. On HP-UX 11.11 and beyond, this metric includes some kinds of dynamically allocated kernel memory. On Solaris non-global zones, this metric is N/A. GBL_MEM_SYS_UTIL ---------------------------------- The percentage of physical memory used by the system during the interval. System memory does not include the buffer cache. On HP-UX and Linux this does not include filecache also. On HP-UX 11.0, this metric does not include some kinds of dynamically allocated kernel memory. This has always been reported in the GBL_MEM_USER* metrics. On HP-UX 11.11 and beyond, this metric includes some kinds of dynamically allocated kernel memory. On Solaris non-global zones, this metric shows value as 0. GBL_MEM_USER ---------------------------------- The amount of physical memory (in MBs unless otherwise specified) allocated to user code and data at the end of the interval. User memory regions include code, heap, stack, and other data areas including shared memory. This does not include memory for buffer cache. On HP-UX and Linux this does not include filecache also. On HP-UX 11.0, this metric includes some kinds of dynamically allocated kernel memory. On HP-UX 11.11 and beyond, this metric does not include some kinds of dynamically allocated kernel memory. This is now reported in the GBL_MEM_SYS* metrics. Large fluctuations in this metric can be caused by programs which allocate large amounts of memory and then either release the memory or terminate. A slow continual increase in this metric may indicate a program with a memory leak. GBL_MEM_USERRES_FREE ---------------------------------- The smallest value returned from a monitoring interval that represents a percentage of the User resources still free. Windows 3.11 provides only limited space in its Graphics Device Interface and User modules to hold the handles (memory identifiers) that describe window objects and other program items. GBL_MEM_USER_REFERENCED_UTIL ---------------------------------- The percent of physical memory referenced by user code and data at the end of the interval. This metric shows the percent of memory owned by user memory regions such as user code, heap, stack and other data areas including shared memory. This does not include memory for buffer cache. GBL_MEM_USER_UNREFERENCED_UTIL ---------------------------------- The percent of physical memory not referenced by user code and data which was allocated for user code and date at the end of the interval. GBL_MEM_USER_UTIL ---------------------------------- The percent of physical memory allocated to user code and data at the end of the interval. This metric shows the percent of memory owned by user memory regions such as user code, heap, stack and other data areas including shared memory. This does not include memory for buffer cache. On HP-UX and Linux this does not include filecache also. On HP-UX 11.0, this metric includes some kinds of dynamically allocated kernel memory. On HP-UX 11.11 and beyond, this metric does not include some kinds of dynamically allocated kernel memory. This is now reported in the GBL_MEM_SYS* metrics. Large fluctuations in this metric can be caused by programs which allocate large amounts of memory and then either release the memory or terminate. A slow continual increase in this metric may indicate a program with a memory leak. GBL_MEM_UTIL ---------------------------------- The percentage of physical memory in use during the interval. This includes system memory (occupied by the kernel), buffer cache and user memory. On HP-UX 11iv3 and above, this includes file cache also. On HP-UX, this calculation is done using the byte values for physical memory and used memory, and is therefore more accurate than comparing the reported kilobyte values for physical memory and used memory. On Linux, the value of this metric includes buffer cache when the cachemem parameter in the parm file is set to user. On SUN, high values for this metric may not indicate a true memory shortage. This metric can be influenced by the VMM (Virtual Memory Management) system. Locality Domain metrics are available on HP-UX 11iv2 and above. GBL_MEM_FREE and LDOM_MEM_FREE, as well as the memory utilization metrics derived from them, may not always fully match. GBL_MEM_FREE represents free memory in the kernel’s reservation layer while LDOM_MEM_FREE shows actual free pages. If memory has been reserved but not actually consumed from the Locality Domains, the two values won’t match. Because GBL_MEM_FREE includes pre-reserved memory, the GBL_MEM_* metrics are a better indicator of actual memory consumption in most situations. GBL_MEM_VIRT ---------------------------------- The total private virtual memory (in MBs unless otherwise specified) at the end of the interval. This is the sum of the virtual allocation of private data and stack regions for all processes. GBL_NETWORK_SUBSYSTEM_QUEUE ---------------------------------- The average number of processes or kernel threads blocked on the network subsystem (waiting for their network activity to complete) during the interval. This is the sum of processes or kernel threads in the LAN, NFS, and RPC wait states. This does not include processes or kernel threads blocked on SOCKT (that is, sockets) waits, as some processes or kernel threads sit idle in SOCKT waits for long periods. This is calculated as the accumulated time that all processes or kernel threads spent blocked on (LAN + NFS + RPC) divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. GBL_NET_BYTE_RATE ---------------------------------- The total kilobytes per second transferred on the network adapter (Windows 95 only). This measurement requires that the Microsoft Network Monitor protocol driver be installed. The metric derives from the bytes per second count for either Ethernet or Token Ring adapters. On Windows 95 systems, you can also use the GBL_RDR_BYTE_RATE and the GBL_SVR_BYTE_RATE to show client (re- director) and server network traffic. GBL_NET_COLLISION ---------------------------------- The number of collisions that occurred on all network interfaces during the interval. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not include deferred packets. This does not include data for loopback interface. For HP-UX, this will be the same as the sum of the “Single Collision Frames”, “Multiple Collision Frames”, “Late Collisions”, and “Excessive Collisions” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of the “Coll” column from the “netstat -i” command (“collisions” from the “netstat -i -e” command on Linux) for a network device. See also netstat(1). AIX does not support the collision count for the ethernet interface. The collision count is supported for the token ring (tr) and loopback (lo) interfaces. For more information, please refer to the netstat(1) man page. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. GBL_NET_COLLISION_1_MIN_RATE ---------------------------------- The number of collisions per minute on all network interfaces during the interval. This metric does not include deferred packets. This does not include data for loopback interface. Collisions occur on any busy network, but abnormal collision rates could indicate a hardware or software problem. AIX does not support the collision count for the ethernet interface. The collision count is supported for the token ring (tr) and loopback (lo) interfaces. For more information, please refer to the netstat(1) man page. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_COLLISION_PCT ---------------------------------- The percentage of collisions to total outbound packet attempts during the interval. Outbound packet attempts include both successful packets and collisions. This does not include data for loopback interface. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. This metric does not currently include deferred packets. AIX does not support the collision count for the ethernet interface. The collision count is supported for the token ring (tr) and loopback (lo) interfaces. For more information, please refer to the netstat(1) man page. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_COLLISION_RATE ---------------------------------- The number of collisions per second on all network interfaces during the interval. This metric does not include deferred packets. This does not include data for loopback interface. A rising rate of collisions versus outbound packets is an indication that the network is becoming increasingly congested. AIX does not support the collision count for the ethernet interface. The collision count is supported for the token ring (tr) and loopback (lo) interfaces. For more information, please refer to the netstat(1) man page. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_DEFERRED_PCT ---------------------------------- The percentage of deferred packets to total outbound packet attempts during the interval. Outbound packet attempts include both packets successfully transmitted and those that were deferred. This does not include data for loopback interface. HP-UX This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_ERROR ---------------------------------- The number of errors that occurred on all network interfaces during the interval. This does not include data for loopback interface. For HP-UX, this will be the same as the sum of the “Inbound Errors” and “Outbound Errors” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of “Ierrs” (RX-ERR on Linux) and “Oerrs” (TX-ERR on Linux) from the “netstat -i” command for a network device. See also netstat(1). This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. GBL_NET_ERROR_1_MIN_RATE ---------------------------------- The number of errors per minute on all network interfaces during the interval. This rate should normally be zero or very small. A large error rate can indicate a hardware or software problem. This does not include data for loopback interface. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. GBL_NET_ERROR_RATE ---------------------------------- The number of errors per second on all network interfaces during the interval. This does not include data for loopback interface. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_IN_ERROR_PCT ---------------------------------- The percentage of inbound network errors to total inbound packet attempts during the interval. Inbound packet attempts include both packets successfully received and those that encountered errors. This does not include data for loopback interface. A large number of errors may indicate a hardware problem on the network. The percentage of inbound errors to total packets attempted should remain low. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_IN_ERROR_RATE ---------------------------------- The number of inbound errors per second on all network interfaces during the interval. This does not include data for loopback interface. A large number of errors may indicate a hardware problem on the network. The percentage of inbound errors to total packets attempted should remain low. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_IN_PACKET ---------------------------------- The number of successful packets received through all network interfaces during the interval. Successful packets are those that have been processed without errors or collisions. This does not include data for loopback interface. For HP-UX, this will be the same as the sum of the “Inbound Unicast Packets” and “Inbound Non-Unicast Packets” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of the “Ipkts” column (RX-OK on Linux) from the “netstat -i” command for a network device. See also netstat(1). This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_IN_PACKET_RATE ---------------------------------- The number of successful packets per second received through all network interfaces during the interval. Successful packets are those that have been processed without errors or collisions. This does not include data for loopback interface. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_OUTQUEUE ---------------------------------- The sum of the outbound queue lengths for all network interfaces (BYNETIF_QUEUE). This metric is derived from the same source as the Outbound Queue Length shown in the lanadmin(1M) program. This does not include data for loopback interface. For most interfaces, the outbound queue is usually zero. When the value is non-zero over a period of time, the network may be experiencing a bottleneck. Determine which network interface has a non-zero queue and compare its traffic levels to normal. Also see if processes are blocking on network wait states. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. GBL_NET_OUT_ERROR_PCT ---------------------------------- The percentage of outbound network errors to total outbound packet attempts during the interval. Outbound packet attempts include both packets successfully sent and those that encountered errors. This does not include data for loopback interface. The percentage of outbound errors to total packets attempted to be transmitted should remain low. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_OUT_ERROR_RATE ---------------------------------- The number of outbound errors per second on all network interfaces during the interval. This does not include data for loopback interface. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_OUT_PACKET ---------------------------------- The number of successful packets sent through all network interfaces during the last interval. Successful packets are those that have been processed without errors or collisions. This does not include data for loopback interface. For HP-UX, this will be the same as the sum of the “Outbound Unicast Packets” and “Outbound Non-Unicast Packets” values from the output of the “lanadmin” utility for the network interface. Remember that “lanadmin” reports cumulative counts. As of the HP-UX 11.0 release and beyond, “netstat -i” shows network activity on the logical level (IP) only. For all other Unix systems, this is the same as the sum of the “Opkts” column (TX-OK on Linux) from the “netstat -i” command for a network device. See also netstat(1). This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_OUT_PACKET_RATE ---------------------------------- The number of successful packets per second sent through the network interfaces during the interval. Successful packets are those that have been processed without errors or collisions. This does not include data for loopback interface. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. On Solaris non-global zones, this metric shows data from the global zone. GBL_NET_PACKET_RATE ---------------------------------- The number of successful packets per second (both inbound and outbound) for all network interfaces during the interval. Successful packets are those that have been processed without errors or collisions. This does not include data for loopback interface. This metric is updated at the sampling interval, regardless of the number of IP addresses on the system. On Windows system, the packet size for NBT connections is defined as 1 Kbyte. On Solaris non-global zones, this metric shows data from the global zone. Win3x/95 The total packets per second transferred on the network adapter (Windows 95 only). This metric requires that the Microsoft Network Monitor protocol driver be installed. The metric is derived from the frames per second count for either Ethernet or Token Ring adaptors. On Windows 95 systems, you can also use the GBL_RDR_BYTE_RATE and the _GBL_SVR_BYTE_RATE to show client (re- director) and server network traffic. GBL_NET_UTIL_PEAK ---------------------------------- It is the utilisation of the most used network interfaces at the end of the interval. GBL_NFS_CALL ---------------------------------- The number of NFS calls the local system has made as either a NFS client or server during the interval. This includes both successful and unsuccessful calls. Unsuccessful calls are those that cannot be completed due to resource limitations or LAN packet errors. NFS calls include create, remove, rename, link, symlink, mkdir, rmdir, statfs, getattr, setattr, lookup, read, readdir, readlink, write, writecache, null and root operations. On AIX System WPARs, this metric is NA. GBL_NFS_CALL_RATE ---------------------------------- The number of NFS calls per second the system made as either a NFS client or NFS server during the interval. Each computer can operate as both a NFS server, and as an NFS client. This metric includes both successful and unsuccessful calls. Unsuccessful calls are those that cannot be completed due to resource limitations or LAN packet errors. NFS calls include create, remove, rename, link, symlink, mkdir, rmdir, statfs, getattr, setattr, lookup, read, readdir, readlink, write, writecache, null and root operations. On AIX System WPARs, this metric is NA. GBL_NUM_ACTIVE_LS ---------------------------------- This indicates the number of LS hosted in a system that are active . If Perf Agent is installed in a guest or in a standalone system this value will be 0. On Solaris non-global zones, this metric shows value as 0. GBL_NUM_APP ---------------------------------- The number of applications defined in the parm file plus one (for “other”). The application called “other” captures all other processes not defined in the parm file. You can define up to 999 applications. GBL_NUM_CPU ---------------------------------- The number of physical CPUs on the system. This includes all CPUs, either online or offline. For HP-UX and certain versions of Linux, the sar(1M) command allows you to check the status of the system CPUs. For SUN and DEC, the commands psrinfo(1M) and psradm(1M) allow you to check or change the status of the system CPUs. For AIX, this metric indicates the maximum number of CPUs the system ever had. On a logical system, this metric indicates the number of virtual CPUs configured. When hardware threads are enabled, this metric indicates the number of logical processors. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. The Linux kernel currently doesn’t provide any metadata information for disabled CPUs. This means that there is no way to find out types, speeds, as well as hardware IDs or any other information that is used to determine the number of cores, the number of threads, the HyperThreading state, etc... If the agent (or Glance) is started while some of the CPUs are disabled, some of these metrics will be “na”, some will be based on what is visible at startup time. All information will be updated if/when additional CPUs are enabled and information about them becomes available. The configuration counts will remain at the highest discovered level (i.e. if CPUs are then disabled, the maximum number of CPUs/cores/etc... will remain at the highest observed level). It is recommended that the agent be started with all CPUs enabled. Win3x/95 The number of CPUs physically on the system. GBL_NUM_CPU_CORE ---------------------------------- This metric provides the total number of CPU cores on a physical system. On VMs, this metric shows information according to resources available on that VM. On non HP-UX system, this metric is equivalent to active CPU cores. On AIX System WPARs, this metric value is identical to the value on AIX Global Environment. On Windows, this metric will be “na” on Windows Server 2003 Itanium systems. The Linux kernel currently doesn’t provide any metadata information for disabled CPUs. This means that there is no way to find out types, speeds, as well as hardware IDs or any other information that is used to determine the number of cores, the number of threads, the HyperThreading state, etc... If the agent (or Glance) is started while some of the CPUs are disabled, some of these metrics will be “na”, some will be based on what is visible at startup time. All information will be updated if/when additional CPUs are enabled and information about them becomes available. The configuration counts will remain at the highest discovered level (i.e. if CPUs are then disabled, the maximum number of CPUs/cores/etc... will remain at the highest observed level). It is recommended that the agent be started with all CPUs enabled. GBL_NUM_DISK ---------------------------------- The number of disks on the system. Only local disk devices are counted in this metric. On HP-UX, this is a count of the number of disks on the system that have ever had activity over the cumulative collection time. On Solaris non-global zones, this metric shows value as 0. On AIX System WPARs, this metric shows value as 0. GBL_NUM_LS ---------------------------------- This indicates the number of LS hosted in a system. If Perf Agent is installed in a guest or in a standalone system this value will be 0. On Solaris non-global zones, this metric shows value as 0. GBL_NUM_LV ---------------------------------- SunOS The sum of configured logical volumes. Sinix The number of configured virtual disks. GBL_NUM_NETWORK ---------------------------------- The number of network interfaces on the system. This includes the loopback interface. On certain platforms, this also include FDDI, Hyperfabric, ATM, Serial Software interfaces such as SLIP or PPP, and Wide Area Network interfaces (WAN) such as ISDN or X.25. The “netstat -i” command also displays the list of network interfaces on the system. WinNT The number of Network protocols in use on the system. GBL_NUM_ONLINE_VCPU ---------------------------------- The number of virtual processors currently online. This metric is same as “Online Virtual CPUs” field of ‘lparstat -i’ command. GBL_NUM_SOCKET ---------------------------------- The number of physical cpu sockets on the system. On VMs, this metric shows information according to resources available on that VM. On Windows, this metric will be “na” on Windows Server 2003 Itanium systems. GBL_NUM_USER ---------------------------------- The number of users logged in at the time of the interval sample. This is the same as the command “who | wc -l”. For Unix systems, the information for this metric comes from the utmp file which is updated by the login command. For more information, read the man page for utmp. Some applications may create users on the system without using login and updating the utmp file. These users are not reflected in this count. This metric can be a general indicator of system usage. In a networked environment, however, users may maintain inactive logins on several systems. On Windows, the information for this metric comes from the Server Sessions counter in the Performance Libraries Server object. It is a count of the number of users using this machine as a file server. GBL_NUM_VIRTUAL_TARGETS ---------------------------------- The number of virtual target devices served by the VIO server. This metric is only valid on aix VIO servers. GBL_NUM_VSWITCH ---------------------------------- The number of virtual switches configured on the host system. GBL_OSKERNELTYPE_INT ---------------------------------- This indicates the word size of the current kernel on the system. Some hardware can load the 64-bit kernel or the 32-bit kernel. GBL_OSNAME ---------------------------------- A string representing the name of the operating system. On Unix systems, this is the same as the output from the “uname -s” command. Win3x/95 A string representing the name of the operating system. For example, “Windows”. GBL_OSRELEASE ---------------------------------- The current release of the operating system. On most Unix systems, this is same as the output from the “uname -r” command. On AIX, this is the actual patch level of the operating system. This is similar to what is returned by the command “lslpp -l bos.rte” as the most recent level of the COMMITTED Base OS Runtime. For example, “5.2.0”. Win3x/95 The current release of the operating system. GBL_OSVERSION ---------------------------------- A string representing the version of the operating system. This is the same as the output from the “uname -v” command. This string is limited to 20 characters, and as a result, the complete version name might be truncated. On Windows, this is a string representing the service pack installed on the operating system. Win3x/95 A string representing the version of the operating system. GBL_OTHER_QUEUE ---------------------------------- HP-UX The average number of processes or kernel threads blocked on other (unknown) activities during the interval. This includes processes or kernel threads that were started and subsequently suspended before the midaemon was started and have not been resumed, or the block state is unknown. This is calculated as the accumulated time that all processes or kernel threads spent blocked on OTHER divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. SunOS AIX The average number of processes blocked on other (unknown) activities during the interval. GBL_PARTITION_SPACE_MIN ---------------------------------- The total free space on the partition having the least amount of free space, in megabytes and reported for local, fixed disk only. The value is sampled every 30 seconds and the minimum sample in the recording interval reported. GBL_POOL_CPU_AVAIL ---------------------------------- The available physical processors in the shared processor pool during the interval. This metric will be “na” if pool_util_authority is not set in HMC. pool_util_authority indicates if pool utilization data is available or not. To set pool_util_authority, select the “Allow shared processor pool utilization authority” check box from HMC. On AIX System WPARs, this metric is NA. GBL_POOL_CPU_ENTL ---------------------------------- The number of physical processors available in the shared processor pool to which this logical system belongs. On AIX SPLPAR, this metric is equivalent to “Active Physical CPUs in system” field of ‘lparstat -i’ command. On a standalone system, the value is “na”. On AIX System WPARs, this metric is NA. GBL_POOL_ID ---------------------------------- In a virtual environment, this metric identifies the shared resource pool to which the logical system belongs. On AIX SPLPAR, this metric is equivalent to “Shared Pool ID” field of ‘lparstat -i’ command. On a standalone system, the value is “na”. On AIX System WPARs, this metric is NA. GBL_POOL_NUM_CPU ---------------------------------- The number of physical processors in the shared resource pool to which this logical system belongs. On AIX SPLPAR, this metric is equivalent to “Physical CPUs in system” field of ‘lparstat -i’ command. On a standalone system, the value is “na”. AIX On AIX System WPARs, this metric value is not available. GBL_POOL_TOTAL_UTIL ---------------------------------- Percentage of time, the pool CPU was not idle during the interval. This metric will be “na” if pool_util_authority is not set in HMC. pool_util_authority indicates if pool utilization data is available or not. To set pool_util_authority, select the “Allow shared processor pool utilization authority” check box from HMC. On AIX System WPARs, this metric is NA. GBL_PRI_QUEUE ---------------------------------- The average number of processes or kernel threads blocked on PRI (waiting for their priority to become high enough to get the CPU) during the interval. To determine if the CPU is a bottleneck, compare this metric with GBL_CPU_TOTAL_UTIL. If GBL_CPU_TOTAL_UTIL is near 100 percent and GBL_PRI_QUEUE is greater than three, there is a high probability of a CPU bottleneck. This is calculated as the accumulated time that all processes or kernel threads spent blocked on PRI divided by the interval time. HP-UX RUN/PRI/CPU Queue differences for multi-cpu systems: For example, let’s assume we’re using a system with eight processors. We start eight CPU intensive threads that consume almost all of the CPU resources. The approximate values shown for the CPU related queue metrics would be: GBL_RUN_QUEUE = 1.0 GBL_PRI_QUEUE = 0.1 GBL_CPU_QUEUE = 1.0 Assume we start an additional eight CPU intensive threads. The approximate values now shown are: GBL_RUN_QUEUE = 2.0 GBL_PRI_QUEUE = 8.0 GBL_CPU_QUEUE = 16.0 At this point, we have sixteen CPU intensive threads running on the eight processors. Keeping the definitions of the three queue metrics in mind, the run queue is 2 (that is, 16 / 8); the pri queue is 8 (only half of the threads can be active at any given time); and the cpu queue is 16 (half of the threads waiting in the cpu queue that are ready to run, plus one for each active thread). This illustrates that the run queue is the average of number of threads waiting in the runqueue for all processors; the pri queue is the number of threads that are blocked on “PRI” (priority); and the cpu queue is the number of threads in the cpu queue that are ready to run, including the threads using the CPU. Note that if the value for GBL_PRI_QUEUE greatly exceeds the value for GBL_RUN_QUEUE, this may be a side-effect of the measurement interface having lost trace data. In this case, check the value of the GBL_LOST_MI_TRACE_BUFFERS metric. If there has been buffer loss, you can correct the value of GBL_PRI_QUEUE by restarting the midaemon and the performance tools. You can use the /opt/perf/bin/midaemon -T command to force immediate shutdown of the measurement interface. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. GBL_PROC_RUN_TIME ---------------------------------- The average run time, in seconds, for processes that terminated during the interval. GBL_PROC_SAMPLE ---------------------------------- The number of process data samples that have been averaged into global metrics (such as GBL_ACTIVE_PROC) that are based on process samples. GBL_QUEUE_HISTOGRAM ---------------------------------- A bar chart of the processes waiting in queues. Shows breakout of the components of processes waiting in queues. The sum of processes waiting = GBL_RUN_QUEUE + GBL_DISK_SUBSYSTEM_QUEUE + GBL_MEM_QUEUE + GBL_NETWORK_SUBSYSTEM_QUEUE ASCII and binary files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of processes waiting on a character mode terminal display. GBL_RDR_BYTE_RATE ---------------------------------- The number of kilobytes of data per second read and written through the Microsoft Network Client redirector (Windows 95 only). GBL_RDR_REQUEST_RATE ---------------------------------- The number of requests for data per second to be read and written through the Microsoft Network Client redirector (Windows 95 only). (This value is not reported by the Microsoft Client for NetWare). GBL_RUN_QUEUE ---------------------------------- On UNIX systems except Linux, this is the average number of threads waiting in the runqueue over the interval. The average is computed against the number of times the run queue is occupied instead of time. The average is updated by the kernel at a fine grain interval, only when the run queue is occupied. It is not averaged against the interval and can therefore be misleading for long intervals when the run queue is empty most or part of the time. This value matches runq-sz reported by the “sar -q” command. The GBL_LOADAVG* metrics are better indicators of run queue pressure. On Linux and Windows, this is instantaneous value obtained at the time of logging. On Linux, it shows the number of threads waiting in the runqueue. On Windows, it shows the Processor Queue Length. On Unix systems, GBL_RUN_QUEUE will typically be a small number. Larger than normal values for this metric indicate CPU contention among threads. This CPU bottleneck is also normally indicated by 100 percent GBL_CPU_TOTAL_UTIL. It may be OK to have GBL_CPU_TOTAL_UTIL be 100 percent if no other threads are waiting for the CPU. However, if GBL_CPU_TOTAL_UTIL is 100 percent and GBL_RUN_QUEUE is greater than the number of processors, it indicates a CPU bottleneck. On Windows, the Processor Queue reflects a count of process threads which are ready to execute. A thread is ready to execute (in the Ready state) when the only resource it is waiting on is the processor. The Windows operating system itself has many system threads which intermittently use small amounts of processor time. Several low priority threads intermittently wake up and execute for very short intervals. Depending on when the collection process samples this queue, there may be none or several of these low-priority threads trying to execute. Therefore, even on an otherwise quiescent system, the Processor Queue Length can be high. High values for this metric during intervals where the overall CPU utilization (gbl_cpu_total_util) is low do not indicate a performance bottleneck. Relatively high values for this metric during intervals where the overall CPU utilization is near 100% can indicate a CPU performance bottleneck. HP-UX RUN/PRI/CPU Queue differences for multi-cpu systems: For example, let’s assume we’re using a system with eight processors. We start eight CPU intensive threads that consume almost all of the CPU resources. The approximate values shown for the CPU related queue metrics would be: GBL_RUN_QUEUE = 1.0 GBL_PRI_QUEUE = 0.1 GBL_CPU_QUEUE = 1.0 Assume we start an additional eight CPU intensive threads. The approximate values now shown are: GBL_RUN_QUEUE = 2.0 GBL_PRI_QUEUE = 8.0 GBL_CPU_QUEUE = 16.0 At this point, we have sixteen CPU intensive threads running on the eight processors. Keeping the definitions of the three queue metrics in mind, the run queue is 2 (that is, 16 / 8); the pri queue is 8 (only half of the threads can be active at any given time); and the cpu queue is 16 (half of the threads waiting in the cpu queue that are ready to run, plus one for each active thread). This illustrates that the run queue is the average of number of threads waiting in the runqueue for all processors; the pri queue is the number of threads that are blocked on “PRI” (priority); and the cpu queue is the number of threads in the cpu queue that are ready to run, including the threads using the CPU. On Solaris non-global zones, this metric shows data from the global zone. GBL_SLEEP_QUEUE ---------------------------------- HP-UX The average number of processes or kernel threads blocked on SLEEP (waiting to awaken from sleep system calls) during the interval. A process or kernel thread enters the SLEEP state by putting itself to sleep using system calls such as sleep, wait, pause, sigpause, sigsuspend, poll and select. This is calculated as the accumulated time that all processes or kernel threads spent blocked on SLEEP divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. SunOS The average number of processes sleeping during the interval (in a “queue” waiting to awaken from sleep system calls). This is calculated as the accumulated time that all processes spent blocked on SLEEP divided by the interval time. On SUN systems, this metric is only available on SunOS 4.1.X. GBL_SRV_WRKITM_SHORTAGES ---------------------------------- The number of times STATUS_DATA_NOT_ACCEPTED was returned at receive indication time. This occurs when no work item is available or can be allocated to service the incoming request. GBL_STARTED_PROC ---------------------------------- The number of processes that started during the interval. GBL_STARTED_PROC_RATE ---------------------------------- The number of processes that started per second during the interval. GBL_STATTIME ---------------------------------- An ASCII string representing the time at the end of the interval, based on local time. GBL_SUBPROCSAMPLEINTERVAL ---------------------------------- The SubProcSampleInterval parameter sets the internal sampling interval of process data. This option only changes the frequency of how often the operating system process table is scanned in order to accumulate process statistics during a log interval and does not change the logging interval for process data logging. If, for example, the CPU utilization is higher than expected (possibly due to a large operating system process table), you can decrease the utilization by increasing the sampling interval. Note: Increasing the SUBPROC sample interval (SUBPROC can be used interchangeably with SUBPROCSAMPLEINTERVAL) parameter may decrease the accuracy of application data and process data since short-lived processes (those completing within a sample interval) cannot be captured and hence logged by scopeux. To set process subintervals to 5 (default), 10, 15, 20, 30, or 60 seconds (these are the only values allowed), you will have to enter the SUBPROC or SUBPROCSAMPLEINTERVAL sample interval parameter in your parm file. You cannot input a value lower than 5. For example, to set the interval to 15 seconds, add one of the following lines in your parm file: SUBPROC=15 or SUBPROCSAMPLEINTERVAL=15 Changes made to the parm file are logged every time the Performance Agent is restarted. To check changes made to the SUBPROC sample interval parameter in your parm file, you can use the following command: # utility -xs -D |grep -i sub 04/23/99 13:04 Process Collection Sample SubInterval 5 seconds -> 5 seconds 04/23/99 14:31 Process Collection Sample SubInterval 5 seconds -> 15 seconds 04/23/99 14:43 Process Collection Sample SubInterval 15 seconds -> 30 seconds Specify the full pathname of the performance tool bin directory as needed. You can also export the GBL_SUBPROCSAMPLEINTERVAL metric from the Configuration data. GBL_SUSPENDED_PROCS ---------------------------------- The average number of processes which have been either marked as should be suspended (SGETOUT) or have been suspended (SSWAPPED) during the interval. Processes are suspended when the OS detects that memory thrashing is occurring. The scheduler looks for processes that have a high repage rate compared with the number of major page faults the process has done and suspends these processes. GBL_SVR_BYTE_RATE ---------------------------------- The number of kilobytes of data per second read and written through the Microsoft Network Server (Windows 95 only). GBL_SWAP_SPACE_AVAIL ---------------------------------- The total amount of potential swap space, in MB. On HP-UX, this is the sum of the device swap areas enabled by the swapon command, the allocated size of any file system swap areas, and the allocated size of pseudo swap in memory if enabled. Note that this is potential swap space. This is the same as (AVAIL: total) as reported by the “swapinfo -mt” command. On SUN, this is the total amount of swap space available from the physical backing store devices (disks) plus the amount currently available from main memory. This is the same as (used + available) /1024, reported by the “swap - s” command. On Linux, this is same as (Swap: total) as reported by the “free -m” command. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. Win3x/95 On Windows 3.11, this is the sum of the swap file size and the physical memory available to Windows 3.11. On Windows 95, this is the size, or potential size, of the swap file. When configured without an explicit limit on swap size, this will reflect the amount of free disk space. GBL_SWAP_SPACE_AVAIL_KB ---------------------------------- The total amount of potential swap space, in KB. On HP-UX, this is the sum of the device swap areas enabled by the swapon command, the allocated size of any file system swap areas, and the allocated size of pseudo swap in memory if enabled. Note that this is potential swap space. Since swap is allocated in fixed (SWCHUNK) sizes, not all of this space may actually be usable. For example, on a 61MB disk using 2 MB swap size allocations, 1 MB remains unusable and is considered wasted space. On HP-UX, this is the same as (AVAIL: total) as reported by the “swapinfo -t” command. On SUN, this is the total amount of swap space available from the physical backing store devices (disks) plus the amount currently available from main memory. This is the same as (used + available)/1024, reported by the “swap - s” command. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_SWAP_SPACE_DEVICE_AVAIL ---------------------------------- The amount of swap space configured on disk devices exclusively as swap space (in MB). On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. GBL_SWAP_SPACE_FREE ---------------------------------- The amount of free virtual memory (Windows 3.11 only). This includes free heap memory in Windows 3.11 and free memory held by the DPMI host. Unlike the Windows Program Manager About box, it does not include allocated segments that are discardable. GBL_SWAP_SPACE_MEM_AVAIL ---------------------------------- The amount of physical memory available for pseudo swap (in MB). On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. GBL_SWAP_SPACE_RESERVED ---------------------------------- The amount of swap space (in MB) reserved for the swapping and paging of programs currently executing. Process pages swapped include data (heap and stack pages), bss (data uninitialized at the beginning of process execution), and the process user area (uarea). Shared memory regions also require the reservation of swap space. Swap space is reserved (by decrementing a counter) when virtual memory for a program is created, but swap is only used when a page or swap to disk is actually done or the page is locked in memory if swapping to memory is enabled. Virtual memory cannot be created if swap space cannot be reserved. On HP-UX, this is the same as (USED: total) as reported by the “swapinfo -mt” command. On SUN, this is the same as used/1024, reported by the “swap -s” command. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. Win3x/95 The amount of committed virtual storage (Windows 95 only). Committed virtual storage is backed by swap file, executable, or memory-mapped file space, or it is nonpagable. GBL_SWAP_SPACE_USED ---------------------------------- The amount of swap space used, in MB. On HP-UX, “Used” indicates written to disk (or locked in memory), rather than reserved. This is the same as (USED: total - reserve) as reported by the “swapinfo -mt” command. On SUN, “Used” indicates amount written to disk (or locked in memory), rather than reserved. Swap space is reserved (by decrementing a counter) when virtual memory for a program is created. This is the same as (bytes allocated)/1024, reported by the “swap -s” command. On Linux, this is same as (Swap: used) as reported by the “free -m” command. On AIX System WPARs, this metric is NA. On Solaris non-global zones, this metric is N/A. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. Win3x/95 GBL_SWAP_SPACE_USED less GBL_SWAP_SPACE_FREE (Windows 3.11 only). GBL_SWAP_SPACE_USED_UTIL ---------------------------------- This is the percentage of swap space used. On HP-UX, “Used %” indicates percentage of swap space written to disk (or locked in memory), rather than reserved. This is the same as percentage of ((USED: total - reserve)/total)*100, as reported by the “swapinfo -mt” command. On SUN, “Used %” indicates percentage of swap space written to disk (or locked in memory), rather than reserved. Swap space is reserved (by decrementing a counter) when virtual memory for a program is created. This is the same as percentage of ((bytes allocated)/total)*100, reported by the “swap -s” command. On SUN, global swap space is tracked through the operating system. Device swap space is tracked through the devices. For this reason, the amount of swap space used may differ between the global and by-device metrics. Sometimes pages that are marked to be swapped to disk by the operating system are never swapped. The operating system records this as used swap space, but the devices do not, since no physical IOs occur. (Metrics with the prefix “GBL” are global and metrics with the prefix “BYSWP” are by device.) On Linux, this is same as percentage of ((Swap: used)/total)*100, as reported by the “free -m” command. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. GBL_SWAP_SPACE_UTIL ---------------------------------- The percent of available swap space that was being used by running processes in the interval. On Windows, this is the percentage of virtual memory, which is available to user processes, that is in use at the end of the interval. It is not an average over the entire interval. It reflects the ratio of committed memory to the current commit limit. The limit may be increased by the operating system if the paging file is extended. This is the same as (Committed Bytes / Commit Limit) * 100 when comparing the results to Performance Monitor. On HP-UX, swap space must be reserved (but not allocated) before virtual memory can be created. If all of available swap is reserved, then no new processes or virtual memory can be created. Swap space locations are actually assigned (used) when a page is actually written to disk or locked in memory (pseudo swap in memory). This is the same as (PCT USED: total) as reported by the “swapinfo -mt” command. On Unix systems, this metric is a measure of capacity rather than performance. As this metric nears 100 percent, processes are not able to allocate any more memory and new processes may not be able to run. Very low swap utilization values may indicate that too much area has been allocated to swap, and better use of disk space could be made by reallocating some swap partitions to be user filesystems. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. On AIX System WPARs, this metric is NA. GBL_SYSCALL ---------------------------------- The number of system calls during the interval. High system call rates are normal on busy systems, especially with IO intensive applications. Abnormally high system call rates may indicate problems such as a “hung” terminal that is stuck in a loop generating read system calls. GBL_SYSCALL_RATE ---------------------------------- The average number of system calls per second during the interval. High system call rates are normal on busy systems, especially with IO intensive applications. Abnormally high system call rates may indicate problems such as a “hung” terminal that is stuck in a loop generating read system calls. On HP-UX, system call rates affect the overhead of the midaemon. Due to the system call instrumentation on HP-UX, the fork and vfork system calls are double counted. In the case of fork and vfork, one process starts the system call, but two processes exit. HP-UX lightweight system calls, such as umask, do not show up in the Glance System Calls display, but will get added to the global system call rates. If a process is being traced (debugged) using standard debugging tools (such as adb or xdb), all system calls used by that process will show up in the System Calls display while being traced. On HP-UX, compare this metric to GBL_DISK_LOGL_IO_RATE to see if high system callrates correspond to high disk IO. GBL_CPU_SYSCALL_UTIL shows the CPU utilization due to processing system calls. GBL_SYSCALL_READ_BYTE_RATE ---------------------------------- The number of KBs transferred per second via read system calls during the interval. This includes reads to all devices including disks, terminals and tapes. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_SYSCALL_WRITE_BYTE_RATE ---------------------------------- The number of KBs per second transferred via write system calls during the interval. This includes writes to all devices including disks, terminals and tapes. On Solaris non-global zones with Uncapped CPUs, this metric shows data from the global zone. GBL_SYSTEM_ID ---------------------------------- The network node hostname of the system. This is the same as the output from the “uname -n” command. On Windows, the name obtained from GetComputerName. Win3x/95 The system ID as defined at the time of the MeasureWare desktop installation which specifies the name of the client on which data is being collected. GBL_SYSTEM_UPTIME_HOURS ---------------------------------- The time, in hours, since the last system reboot. GBL_SYSTEM_UPTIME_SECONDS ---------------------------------- The time, in seconds, since the last system reboot. GBL_TERM_FIRST_RESP_DIST_1 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_10 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_2 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_3 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_4 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_5 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_6 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_7 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_8 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_DIST_9 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with first response times falling into the 10 ranges collected. GBL_TERM_FIRST_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the first response times for the interval. GBL_TERM_FIRST_RESP_RANGE_1 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_10 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_2 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_3 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_4 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_5 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_6 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_7 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_8 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_FIRST_RESP_RANGE_9 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 first response time bins in seconds. This is for reporting of histograms showing the distribution of first response times. GBL_TERM_IO_QUEUE ---------------------------------- The average number of processes or kernel threads blocked on terminal IO (waiting for their terminal IO to complete) during the interval. This is calculated as the accumulated time that all processes or kernel threads spent blocked on TERM (that is, terminal IO) divided by the interval time. The Global QUEUE metrics, which are based on block states, represent the average number of process or kernel thread counts, not actual queues. The Global WAIT PCT metrics, which are also based on block states, represent the percentage of all processes or kernel threads that were alive on the system. No direct comparison is reasonable with the Application WAIT PCT metrics since they represent percentages within the context of a specific application and cannot be summed or compared with global values easily. In addition, the sum of each Application WAIT PCT for all applications will not equal 100% since these values will vary greatly depending on the number of processes or kernel threads in each application. For example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high. In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk I/O subsystem. GBL_TERM_RESP_DIST_1 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_10 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_2 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_3 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_4 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_5 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_6 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_7 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_8 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_DIST_9 ---------------------------------- An array of 10 numbers showing the distribution of transactions done during the interval with response times falling into the 10 ranges collected. GBL_TERM_RESP_RANGE_(1-10) returns the limits for the 10 ranges. This presents a histogram distribution of the response times for the interval. GBL_TERM_RESP_RANGE_1 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_10 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_2 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_3 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_4 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_5 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_6 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_7 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_8 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_TERM_RESP_RANGE_9 ---------------------------------- An array of 10 numbers showing the upper limit of ranges for the 10 response time bins in seconds. This is for reporting of histograms showing the distribution of response times. GBL_THRESHOLD_CPU ---------------------------------- The percent of CPU that a process must use to become interesting during an interval. The default for this threshold is “5.0”, which means a process must have a value of at least 5.0% for PROC_CPU_TOTAL_UTIL to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_DISK ---------------------------------- On HP-UX, this is the rate (IOs/sec) of physical disk IOs that a process must generate to become interesting during an interval. On Linux, this is the KB rate of physical disk IOs that the system must generate to become interesting during an interval. On the other Unix systems, this is the rate of either block disk IOs or major faults that a process must generate to become interesting during an interval. The default values and corresponding metric for this threshold are noted below. In order to exceed this threshold, the metric noted must match or exceed the value shown. HP-UX 5.0 for PROC_DISK_PHYS_IO_RATE for the given process SUN 5.0 for PROC_DISK_BLOCK_IO_RATE for the given process AIX 5.0 for PROC_DISK_BLOCK_IO_RATE for the given process OSF1 2.0 for PROC_IO_BYTE_RATE for the given process Linux 15.0 for GBL_DISK_PHYS_BYTE_RATE All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_FIRSTRESP ---------------------------------- The number of seconds that the average transaction time to first response must exceed for a process to become interesting during an interval. The default for this threshold is “ 5.0” which means a process must have a PROC_TERM_FIRST_RESP value of 5.0 seconds or greater to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_MAXTHINK ---------------------------------- The maximum think time in order for a terminal transaction to be considered valid. Transactions with think times greater than this value will be ignored. This parameter can be used to eliminate counting the first transaction at a terminal following a long pause. Such first transactions are unusually slow since the system must reinstate the processes resources to main memory before it can begin. GBL_THRESHOLD_MINTHINK ---------------------------------- The minimum think time in order for a terminal transaction to be considered valid. Transactions with think times less than this value will be ignored. This parameter can be used to eliminate counting transactions by hardware devices such as serial printers. GBL_THRESHOLD_NOKILLED ---------------------------------- This is a flag specifying that terminating processes are not interesting. The flag is set by the THRESHOLD NOKILLED statement in the parm file. If this flag is set, then the process will be logged only if it exceeds at least one of the thresholds. The default (blank) is for the flag to be turned off, which means a terminating process will be logged in the interval it exits even if it did not exceed any thresholds during that interval. This is so that the death of a process is recorded even if it does not exceed any of the thresholds. On HP-UX, an exception to this is short-lived processes that are alive for less than one second. By default, short-lived processes are not considered interesting. However, there is a flag (THRESHOLD_SHORTLIVED) to turn on the logging of short-lived processes. GBL_THRESHOLD_NONEW ---------------------------------- This is a flag specifying that newly created processes are not interesting. The flag is set by the THRESHOLD NONEW statement in the parm file. If this flag is set, then the process will be logged only if it exceeds at least one of the thresholds. The default (blank) is for the flag to be turned off, which means a new process will be logged in the interval it was created even if it did not exceed any thresholds during that interval. This is so that the existence of a process is recorded even if it does not exceed any of the thresholds. On HP-UX, an exception to this is short-lived processes that are alive for less than one second. By default, short-lived processes are not considered interesting. However, there is a flag (THRESHOLD_SHORTLIVED) to turn on the logging of short-lived processes. GBL_THRESHOLD_PROCMEM ---------------------------------- The process memory threshold specified in the parm file. GBL_THRESHOLD_RESPONSE ---------------------------------- The number of seconds that the average transaction time to prompt must exceed for a process to become interesting during an interval. The default for this threshold is “ 30.0” which means a process must have a PROC_TERM_RESP value of 30.0 seconds or greater to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_SHORTLIVED ---------------------------------- This is a flag to specify that short-lived processes are to be considered interesting. A short-lived process is one that runs for less than one second. By default, a short-lived process is not logged unless it exceeded any threshold during its short life. This is because on UNIX systems there are many of these short-lived processes that do not consume much of the system resources. Many are simply processes created to fork another process. Logging them can become quite expensive. The THRESHOLD SHORTLIVED statement in the parm file can be used to turn logging of short-lived processes on. GBL_THRESHOLD_TRANS ---------------------------------- The number of terminal transactions that a process must complete to become interesting during an interval. The default for this threshold is “ 100” which means a process must have a value of at least 100 for PROC_TERM_TRAN to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. This metric is available on HP-UX 10.20. GBL_THRESHOLD_WAIT_CPU ---------------------------------- The percent of time that a process must spend waiting on the CPU to become interesting during an interval. The default for this threshold is “ 100.0” which means a process must have a value of at least 100.0% for PROC_PRI_WAIT_PCT to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_WAIT_DISK ---------------------------------- The percent of time that a process must spend waiting on the disk subsystem to become interesting during an interval. The disk subsystem includes disk transfers, memory cache, inode access, or CD-ROM disk transfers. The default for this threshold is “ 100.0” which means a process must have a value of at least 100.0% for PROC_DISK_SUBSYSTEM_WAIT_PCT to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_WAIT_IMPEDE ---------------------------------- The percent of time that a process must spend waiting on a semaphore to become interesting during an interval. The default for this threshold is “ 100.0” which means a process must have a value of at least 100.0% for PROC_SEM_WAIT_PCT to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_THRESHOLD_WAIT_MEMORY ---------------------------------- The percent of time that a process must spend waiting on access to main memory to become interesting during an interval. The default for this threshold is “ 100.0” which means a process must have a value of at least 100.0% for PROC_MEM_WAIT_PCT to exceed this threshold. All threshold values are supplied by the parm file. A process must exceed at least one threshold value in any given interval before it will be considered interesting and be logged. GBL_TOTAL_DISPATCH_TIME ---------------------------------- Total lpar dispatch time in seconds during the interval. On AIX 5.3 or below, value of this metric will be “na”. On AIX System WPARs, this metric is NA. GBL_TT_OVERFLOW_COUNT ---------------------------------- The number of new transactions that could not be measured because the Measurement Processing Daemon’s (midaemon) Measurement Performance Database is full. If this happens, the default Measurement Performance Database size is not large enough to hold all of the registered transactions on this system. This can be remedied by stopping and restarting the midaemon process using the -smdvss option to specify a larger Measurement Performance Database size. The current Measurement Performance Database size can be checked using the midaemon -sizes option. GBL_VCSWITCH_RATE ---------------------------------- The average number of Virtual Context switches per second. On AIX System WPARs, this metric is NA. GBL_WEB_CACHE_HIT_PCT ---------------------------------- The ratio of cache hits to all cache requests during the interval. Cache hits occur when a file open, directory listing or service specific object request is found in the cache. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_CGI_REQUEST_RATE ---------------------------------- The number of CGI requests being processed per second. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_CONNECTION_RATE ---------------------------------- The sum of the number of simultaneous connections to the HTTP, FTP or gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_FILES_RECEIVED_RATE ---------------------------------- The rate of files/sec received by the HTTP or FTP servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_FILES_SENT_RATE ---------------------------------- The rate of files/sec sent by the HTTP, FTP or gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_FTP_READ_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are received by FTP servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_FTP_WRITE_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are sent by FTP servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_GET_REQUEST_RATE ---------------------------------- The number of GET requests being processed per second. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_GOPHER_READ_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are received by gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_GOPHER_WRITE_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are sent by gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_HEAD_REQUEST_RATE ---------------------------------- The number of HEAD requests being processed per second. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_HTTP_READ_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are received by HTTP servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_HTTP_WRITE_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are sent by HTTP servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_ISAPI_REQUEST_RATE ---------------------------------- The number of ISAPI requests being processed per second. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_LOGON_FAILURES ---------------------------------- The number of logon failures that have been made by the HTTP, FTP or gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_NOT_FOUND_ERRORS ---------------------------------- Number of requests that could not be satisfied by service because requested documents could not be found; typically reported as HTTP 404 error code to client. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_OTHER_REQUEST_RATE ---------------------------------- The number of OTHER requests being processed per second. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_POST_REQUEST_RATE ---------------------------------- The number of POST requests being processed per second. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_READ_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are received by the HTTP, FTP or gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. GBL_WEB_WRITE_BYTE_RATE ---------------------------------- The byte rate in KBs per second that data bytes are sent by the HTTP, FTP or gopher servers during the interval. This metric is available only for Internet Information Server (IIS) 3.0 because IIS 3.0 uses the HTTP object. The GBL_WEB_* metrics are not available for IIS 4.0 because IIS 4.0 uses the Web Service object, not the HTTP object. There is a sample Extended Collection Builder policy that uses selected metrics from the Web Service object. This policy is provided with the MeasureWare Agent product. INTERVAL ---------------------------------- The number of seconds in the measurement interval. For the process data class, this is the number of seconds the process was alive during the interval. LV_DEVNAME_ALIAS ---------------------------------- The name of this volume group associated with a logical volume. This metric is applicable only for the Veritas LVM. LV_DIRNAME ---------------------------------- HP-UX The path name of this logical volume or volume/disk group. On HP-UX 11i and beyond, data is available from VERITAS Volume Manager (VxVM). LVM (Logical Volume Manager) uses the terminology “volume group” to describe a set of related volumes. VERITAS Volume Manager uses the terminology “disk group” to describe a collection of VM disks. For additional information on VERITAS Volume Manager, see vxintro(1M). For LVM logical volumes, this is the name used as a parameter to the lvdisplay(1M) command. For volume groups, this is the name used as a parameter to the vgdisplay(1M) command. The entry referred to as the “/dev/vgXX/group” entry shows the internal resources used by the LVM software to manage the logical volumes. SunOS The absolute path name of this logical volume, volume group, or DiskSuite metadevice name. For example: Volume group: /dev/vx/dsk/ Logical volume: /dev/vx/dsk// Disk Suite: /dev/md/dsk/ AIX The device file name of this logical volume or volume group. Sinix The device file name of the virtual disk. The name is used as a parameter to the dkconfig(8) command. The example device file name is “/dev/vd/vdisk13”. Virtual disks function identically to traditional physical disks, but their relation to physical disks is determined from a mapping of a physical disk (or disks) to a virtual disk (vdisk(1M)). This is done by means of a virtual disk configuration file, /etc/dktab. DEC The device file name of a logical volume. For example: Volume groups: /dev/vol/ To get a list of all group names from the system use: volprint -G Logical volumes: /dev/vol// To get a list of all logical-volume names from a group: ls -l /dev/vol// LV_DIRNAME_ALIAS ---------------------------------- The absolute path name of this logical volume. For example: Logical volume: /dev/vx/dsk// This metric is applicable only for the Veritas LVM. LV_GROUP_NAME ---------------------------------- On HP-UX, this is the name of this volume/disk group associated with a logical volume. On SUN and AIX, this is the name of this volume group associated with a logical volume. On SUN, this metric is applicable only for the Veritas LVM. On HP-UX 11i and beyond, data is available from VERITAS Volume Manager (VxVM). LVM (Logical Volume Manager) uses the terminology “volume group” to describe a set of related volumes. VERITAS Volume Manager uses the terminology “disk group” to describe a collection of VM disks. For additional information on VERITAS Volume Manager, see vxintro(1M). LV_LOGL_READ ---------------------------------- The number of logical reads for the current logical volume during the interval. Note: This metric is not available on HP-UX. LV_LOGL_WRITE ---------------------------------- The number of logical writes to the current logical volume during the interval. Note: This metric is not available on HP-UX. LV_READ_BYTE_RATE ---------------------------------- The number of physical KBs per second read from this logical volume during the interval. Note that bytes read from the buffer cache are not included in this calculation. SunOS DiskSuite metadevices are not supported. This metric is reported as “na” for volume groups since it is not applicable. LV_READ_RATE ---------------------------------- HP-UX The number of physical reads per second for this logical volume during the interval. This may not correspond to the physical read rate from a particular disk drive since a logical volume may be composed of many disk drives or it may be a subset of a disk drive. An individual physical read from one logical volume may span multiple individual disk drives. Since this is a physical read rate, there may not be any correspondence to the logical read rate since many small reads are satisfied in the buffer cache, and large logical read requests must be broken up into physical read requests. SunOS The number of physical reads per second for this logical volume during the interval. This may not correspond to the physical read rate from a particular disk drive since a logical volume may be composed of many disk drives or it may be a subset of a disk drive. An individual physical read from one logical volume may span multiple individual disk drives. Since this is a physical read rate, there may not be any correspondence to the logical read rate since many small reads are satisfied in the buffer cache, and large logical read requests must be broken up into physical read requests. DiskSuite metadevices are not supported. This metric is reported as “na” for volume groups since it is not applicable. Sinix The number of physical reads per second for the current virtual disk during the interval. Virtual disks function identically to traditional physical disks, but their relation to physical disks is determined from a mapping of a physical disk (or disks) to a virtual disk (vdisk(1M)). This is done by means of a virtual disk configuration file, /etc/dktab. DEC The number of physical reads per second for this logical volume during the interval. This may not correspond to the physical read rate from a particular disk drive since a logical volume may be composed of many disk drives or it may be a subset of a disk drive. An individual physical read from one logical volume may span multiple individual disk drives. Since this is a physical read rate, there may not be any correspondence to the logical read rate since many small reads are satisfied in the buffer cache, and large logical read requests must be broken up into physical read requests. The utility volstat can be used to get the data from the shell. LV_SPACE_UTIL ---------------------------------- Percentage of the logical volume file system space in use during the interval. A value of “na” is displayed for volume groups and logical volumes which have no mounted filesystem. LV_WRITE_BYTE_RATE ---------------------------------- The number of KBs per second written to this logical volume during the interval. SunOS DiskSuite metadevices are not supported. This metric is reported as “na” for volume groups since it is not applicable. LV_WRITE_RATE ---------------------------------- HP-UX The number of physical writes per second to this logical volume during the interval. This may not correspond to the physical write rate to a particular disk drive since a logical volume may be composed of many disk drives or it may be a subset of a disk drive. Since this is a physical write rate, there may not be any correspondence to the logical write rate since many small writes are combined in the buffer cache, and many large logical writes must be broken up. SunOS The number of physical writes per second to this logical volume during the interval. This may not correspond to the physical write rate to a particular disk drive since a logical volume may be composed of many disk drives or it may be a subset of a disk drive. Since this is a physical write rate, there may not be any correspondence to the logical write rate since many small writes are combined in the buffer cache, and many large logical writes must be broken up. DiskSuite metadevices are not supported. This metric is reported as “na” for volume groups since it is not applicable. Sinix The number of physical writes per second to the current virtual disk during the interval. Virtual disks function identically to traditional physical disks, but their relation to physical disks is determined from a mapping of a physical disk (or disks) to a virtual disk (vdisk(1M)). This is done by means of a virtual disk configuration file, /etc/dktab. DEC The number of physical writes per second to this logical volume during the interval. This may not correspond to the physical write rate to a particular disk drive since a logical volume may be composed of many disk drives or it may be a subset of a disk drive. Since this is a physical write rate, there may not be any correspondence to the logical write rate since many small writes are combined in the buffer cache, and many large logical writes must be broken up. The utility volstat can be used to get the data from the shell. PROC_APP_ID ---------------------------------- The ID number of the application to which the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) belonged during the interval. Application “other” always has an ID of 1. There can be up to 999 user- defined applications, which are defined in the parm file. PROC_CPU_ALIVE_SYS_MODE_UTIL ---------------------------------- The total CPU time consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) in system mode as a percentage of the time it is alive during the interval. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_ALIVE_TOTAL_UTIL ---------------------------------- The total CPU time consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) as a percentage of the time it is alive during the interval. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_ALIVE_USER_MODE_UTIL ---------------------------------- The total CPU time consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) in user mode as a percentage of the time it is alive during the interval. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_CSWITCH_TIME ---------------------------------- The time, in seconds, that the process or kernel thread spent in context switching during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_CSWITCH_UTIL ---------------------------------- The percentage of time spent in context switching the current process or kernel thread during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_INTERRUPT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread spent processing interrupts during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_INTERRUPT_UTIL ---------------------------------- The percentage of time that this process or kernel thread was in interrupt mode during the last interval. Interrupt mode means that interrupts were being handled while the process or kernel thread was loaded and running on the CPU. The interrupts may have been generated by any process, not just the running process, but they were handled while the process or kernel thread was running and may have had an impact on the performance of this process or kernel thread. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_NICE_TIME ---------------------------------- The time, in seconds, that this niced process or kernel thread was using the CPU in user mode during the interval. On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_NICE_UTIL ---------------------------------- The percentage of time that this niced process or kernel thread was in user mode during the interval. On HP-UX, the NICE metrics include positive nice value CPU time only. Negative nice value CPU is broken out into NNICE (negative nice) metrics. Positive nice values range from 20 to 39. Negative nice values range from 0 to 19. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_NORMAL_TIME ---------------------------------- The time, in seconds, that the selected process or kernel thread was in user mode at normal priority during the interval. Normal priority user mode CPU excludes CPU used at real-time and nice priorities. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_NORMAL_UTIL ---------------------------------- The percentage of time that this process or kernel thread was in user mode at a normal priority during the interval. “At a normal priority” means the neither rtprio or nice had been used to alter the priority of the process or kernel thread during the interval. Normal priority user mode CPU excludes CPU used at real-time and nice priorities. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_REALTIME_TIME ---------------------------------- The time, in seconds, that the selected process or kernel thread was in user mode at a realtime priority during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_REALTIME_UTIL ---------------------------------- The percentage of time that this process or kernel thread was at a realtime priority during the interval. The realtime CPU is separated out to allow users to see the effect of using the realtime facilities to alter priority. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_SYSCALL_TIME ---------------------------------- The time, in seconds, that this process or kernel thread spent executing system calls in system mode, excluding interrupt or context processing, during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_SYSCALL_UTIL ---------------------------------- The percentage of the total CPU time this process or kernel thread spent in system mode (excluding interrupt, context switch, trap, or vfault CPU) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_SYS_MODE_TIME ---------------------------------- The CPU time in system mode in the context of the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) during the interval. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_SYS_MODE_UTIL ---------------------------------- The percentage of time that the CPU was in system mode in the context of the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) during the interval. A process operates in either system mode (also called kernel mode on Unix or privileged mode on Windows) or user mode. When a process requests services from the operating system with a system call, it switches into the machine’s privileged protection mode and runs in system mode. Unlike the global and application CPU metrics, process CPU is not averaged over the number of processors on systems with multiple CPUs. Single-threaded processes can use only one CPU at a time and never exceed 100% CPU utilization. High system mode CPU utilizations are normal for IO intensive programs. Abnormally high system CPU utilization can indicate that a hardware problem is causing a high interrupt rate. It can also indicate programs that are not using system calls efficiently. A classic “hung shell” shows up with very high system mode CPU because it gets stuck in a loop doing terminal reads (a system call) to a device that never responds. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_TOTAL_TIME ---------------------------------- The total CPU time, in seconds, consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) during the interval. Unlike the global and application CPU metrics, process CPU is not averaged over the number of processors on systems with multiple CPUs. Single-threaded processes can use only one CPU at a time and never exceed 100% CPU utilization. On HP-UX, the total CPU time is the sum of the CPU time components for a process or kernel thread, including system, user, context switch, interrupts processing, realtime, and nice utilization values. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_TOTAL_TIME_CUM ---------------------------------- The total CPU time consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) over the cumulative collection time. CPU time is in seconds unless otherwise specified. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. This is calculated as PROC_CPU_TOTAL_TIME_CUM = PROC_CPU_SYS_MODE_TIME_CUM + PROC_CPU_USER_MODE_TIME_CUM On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_TOTAL_UTIL ---------------------------------- The total CPU time consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) as a percentage of the total CPU time available during the interval. Unlike the global and application CPU metrics, process CPU is not averaged over the number of processors on systems with multiple CPUs. Single-threaded processes can use only one CPU at a time and never exceed 100% CPU utilization. On HP-UX, the total CPU utilization is the sum of the CPU utilization components for a process or kernel thread, including system, user, context switch, interrupts processing, realtime, and nice utilization values. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. AIX On AIX SPLPAR, this metric indicates the total physical processing units consumed by processes. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_TOTAL_UTIL_CUM ---------------------------------- The total CPU time consumed by a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) as a percentage of the total CPU time available over the cumulative collection time. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. Unlike the global and application CPU metrics, process CPU is not averaged over the number of processors on systems with multiple CPUs. Single-threaded processes can use only one CPU at a time and never exceed 100% CPU utilization. On HP-UX, the total CPU utilization is the sum of the CPU utilization components for a process or kernel thread, including system, user, context switch, interrupts processing, realtime, and nice utilization values. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_USER_MODE_TIME ---------------------------------- The time, in seconds, the process (or kernel threads, if HP-UX/Linux Kernel 2.6 and above) was using the CPU in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_CPU_USER_MODE_UTIL ---------------------------------- The percentage of time the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) was using the CPU in user mode during the interval. User CPU is the time spent in user mode at a normal priority, at real-time priority (on HP-UX, AIX, and Windows systems), and at a nice priority. Unlike the global and application CPU metrics, process CPU is not averaged over the number of processors on systems with multiple CPUs. Single-threaded processes can use only one CPU at a time and never exceed 100% CPU utilization. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On multi-processor HP-UX systems, processes which have component kernel threads executing simultaneously on different processors could have resource utilization sums over 100%. The maximum percentage is 100% times the number of CPUs online. On platforms other than HPUX, If the ignore_mt flag is set(true) in parm file, this metric will report values normalized against the number of active cores in the system. If the ignore_mt flag is not set(false) in parm file, this metric will report values normalized against the number of threads in the system. This flag will be a no-op if Multithreading is turned off. On HPUX, CPU utilization normalization is controlled by the “-ignore_mt” option of the midaemon(1m). To change normalization from core-based to logical-cpu-based, or vice-versa, all performance components (scopeux, glance, perfd) must be shut down and the midaemon restarted in the desired mode. To start the midaemon with “-ignore_mt” by default, this option should be added in the /etc/rc.config.d/ovpa control file. Refer to the documentation regarding ovpa startup. Note that, on HPUX, unlike other platforms, specifying core-based normalization affects CPU, application, process and thread metrics. PROC_DISK_BLOCK_IO ---------------------------------- The number of block IOs made by (or for) a process during the interval. On Sun 5.X (Solaris 2.X or later), these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, block IOs refer to data transferred between disk and the file system buffer cache in block size chunks. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_IO_CUM ---------------------------------- The number of block IOs made by (or for) a process during its lifetime or over the cumulative collection time. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On Sun 5.X (Solaris 2.X or later), these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, block IOs refer to data transferred between disk and the file system buffer cache in block size chunks. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_IO_RATE ---------------------------------- The number of block IOs per second made by (or for) a process during the interval. On Sun 5.X (Solaris 2.X or later), these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, block IOs refer to data transferred between disk and the file system buffer cache in block size chunks. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_IO_RATE_CUM ---------------------------------- The average number of block IOs per second made by (or for) a process during its lifetime or over the cumulative collection time. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On Sun 5.X (Solaris 2.X or later), these are physical IOs generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). On AIX, block IOs refer to data transferred between disk and the file system buffer cache in block size chunks. Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_READ ---------------------------------- The number of block reads made by a process during the interval. On Sun 5.X (Solaris 2.X or later), these are physical reads generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_READ_RATE ---------------------------------- The number of block reads per second made by (or for) a process during the interval. On Sun 5.X (Solaris 2.X or later), these are physical reads generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_WRITE ---------------------------------- Number of block writes made by a process during the interval. Calls destined for NFS mounted files are not included. On Sun 5.X (Solaris 2.X or later), these are physical writes generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_BLOCK_WRITE_RATE ---------------------------------- The number of block writes per second made by (or for) a process during the interval. On Sun 5.X (Solaris 2.X or later), these are physical writes generated by file system access and do not include virtual memory IOs, or IOs relating to raw disk access. These are IOs for inode and superblock updates which are handled through the buffer cache. Because virtual memory IOs are not credited to the process, the block IOs tend to be much lower on SunOS 5.X than they are on SunOS 4.1.X systems. When a file is accessed on SunOS 5.X or later, it is memory mapped by the operating system. Accesses generate virtual memory IOs. Reading a file generates block IOs as the file’s inode information is cached. File writes are a combination of posting to memory mapped allocations (VM IOs) and posting updated inode information to disk (block IOs). Note, when a file is accessed on AIX, it is memory mapped by the operating system, so accesses generate virtual memory IOs, not block IOs. PROC_DISK_FS_IO ---------------------------------- The number of file system disk IOs for a process during the interval. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access, or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical IOs in this category (they appear under virtual memory IOs). PROC_DISK_FS_IO_RATE ---------------------------------- The number of file system disk IOs per second for a process during the interval. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access), or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical IOs in this category (they appear under virtual memory IOs). PROC_DISK_FS_READ ---------------------------------- Number of file system physical disk reads made by a process or kernel thread during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access), or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical reads in this category. They appear under virtual memory reads. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_FS_READ_RATE ---------------------------------- The number of file system physical disk reads made by a process or kernel thread during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical reads generated by user file system access and do not include virtual memory reads, system reads (inode access), or reads relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical reads in this category. They appear under virtual memory reads. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_FS_WRITE ---------------------------------- Number of file system physical disk writes made by a process or kernel thread during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical writes generated by user file system access and do not include virtual memory writes, system writes (inode updates), or writes relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical writes in this category. They appear under virtual memory writes. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_FS_WRITE_RATE ---------------------------------- The number of file system physical disk writes made by a process or kernel thread during the interval. Only local disks are counted in this measurement. NFS devices are excluded. These are physical writes generated by user file system access and do not include virtual memory writes, system writes (inode updates), or writes relating to raw disk access. An exception is user files accessed via the mmap(2) call, which does not show their physical writes in this category. They appear under virtual memory writes. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_LOGL_IO_CUM ---------------------------------- The number of logical IOs made by (or for) a process or kernel thread over the cumulative collection time. NFS mounted disks are not included in this list. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_LOGL_IO_RATE_CUM ---------------------------------- The average number of logical IOs per second made by (or for) a process or kernel thread over the cumulative collection time. Only local disks are counted in this measurement. NFS devices are excluded. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. On many Unix systems, there are several reasons why logical IOs may not correspond with physical IOs. Logical IOs may not always result in a physical disk access, since the data may already reside in memory -- either in the buffer cache, or in virtual memory if the IO is to a memory mapped file. Several logical IOs may all map to the same physical page or block. In these two cases, logical IOs are greater than physical IOs. The reverse can also happen. A single logical write can cause a physical read to fetch the block to be updated from disk, and then cause a physical write to put it back on disk. A single logical IO can require more than one physical page or block, and these can be found on different disks. Mirrored disks further distort the relationship between logical and physical IO, since physical writes are doubled. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_LOGL_READ ---------------------------------- The number of disk logical reads made by a process or kernel thread during the interval. Calls destined for NFS mounted files are not counted. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_LOGL_READ_RATE ---------------------------------- The number of logical reads per second made by (or for) a process or kernel thread during the interval. Calls destined for NFS mounted files are not counted. On many Unix systems, logical disk IOs are measured by counting the read system calls that are directed to disk devices. Also counted are read system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_LOGL_WRITE ---------------------------------- Number of disk logical writes made by a process or kernel thread during the interval. Calls destined for NFS mounted files are not counted. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_LOGL_WRITE_RATE ---------------------------------- The number of logical writes per second made by (or for) a process or kernel thread during the interval. NFS mounted disks are not included in this list. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). On many Unix systems, logical disk IOs are measured by counting the write system calls that are directed to disk devices. Also counted are write system calls made indirectly through other system calls, including writev, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, send, sento, sendmsg, and ipcsend. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_PHYS_IO ---------------------------------- The number of physical IOs made by (or for) a process during the interval. PROC_DISK_PHYS_IO_CUM ---------------------------------- This is the total number of physical disk transfers done by a process since it was created. It is calculated as: PROC_DISK_PHYS_IO_CUM = PROC_DISK_PHYS_IO_RATE_CUM * PROC_RUN_TIME PROC_DISK_PHYS_IO_RATE ---------------------------------- The average number of physical disk IOs per second made by the process or kernel thread during the interval. For processes which run for less than the measurement interval, this metric is normalized over the measurement interval. For example, a process ran for 1 second and did 50 IOs during its life. If the measurement interval is 5 seconds, it is reported as having done 10 IOs per second. If the measurement interval is 60 seconds, it is reported as having done 50/60 or 0.83 IOs per second. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_DISK_PHYS_IO_RATE_CUM ---------------------------------- The number of physical disk IOs per second made by the selected process or kernel thread over the cumulative collection time. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_DISK_PHYS_READ ---------------------------------- The number of physical reads made by (or for) a process or kernel thread during the last interval. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). NFS mounted disks are not included in this list. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_DISK_PHYS_READ_RATE ---------------------------------- The number of physical reads per second made by (or for) a process or kernel thread during the interval. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). NFS mounted disks are not included in this list. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_DISK_PHYS_WRITE ---------------------------------- The number of physical writes made by (or for) a process or kernel thread during the last interval. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_DISK_PHYS_WRITE_RATE ---------------------------------- The number of physical writes per second made by (or for) a process or kernel thread during the interval. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). NFS mounted disks are not included in this list. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_DISK_SUBSYSTEM_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on the disk subsystem (waiting for its file system IOs to complete) during the interval. This includes time spent waiting in the DISK, INODE, CACHE, and CDFS wait states. It does not include processes doing raw IO to disk devices. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_DISK_SUBSYSTEM_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on the disk subsystem (waiting for its file system IOs to complete) during the interval. This includes time spent waiting in the DISK, INODE, CACHE, and CDFS wait states. It does not include processes doing raw IO to disk devices. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_DISK_SYSTEM_IO ---------------------------------- Number of file system management physical disk IOs made for a process or kernel thread during the interval. File system management IOs are the physical accesses required to obtain or update internal information about the file system structure (inode access). Accesses or updates to user data are not included in this metric. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_SYSTEM_IO_RATE ---------------------------------- The number of file system management physical disk IOs per second made for a process or kernel thread during the interval. File system management IOs are the physical accesses required to obtain or update internal information about the file system structure (inode access). Accesses or updates to user data are not included in this metric. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_VM_IO ---------------------------------- The number of virtual memory IOs made for a process or kernel thread during the interval. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_DISK_VM_IO_RATE ---------------------------------- The number of virtual memory IOs per second made for a process or kernel thread during the interval. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_EUID ---------------------------------- The Effective User ID of a process(or kernel thread, if HP-UX/Linux Kernel 2.6 and above). On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_FORCED_CSWITCH ---------------------------------- The number of times that the process (or kernel thread, if HP-UX) was preempted by an external event and another process (or kernel thread, if HP- UX) was allowed to execute during the interval. Examples of reasons for a forced switch include expiration of a time slice or returning from a system call with a higher priority process (or kernel thread, if HP-UX) ready to run. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. PROC_GROUP_ID ---------------------------------- On most systems, this is the real group ID number of the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above). On AIX, this is the effective group ID number of the process. On HP-UX, this is the effective group ID number of the process if not in setgid mode. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_INTEREST ---------------------------------- A string containing the reason(s) why the process or thread is of interest, based on the thresholds specified in the parm file. An ‘A’ indicates that the process or thread exceeds the process CPU threshold, computed using the actual time the process or thread was alive during the interval. A ‘C’ indicates that the process or thread exceeds the process CPU threshold, computed using the collection interval. Currently, the same CPU threshold is used for both CPU interest reasons. A ‘D’ indicates that the process or thread exceeds the process disk IO threshold. An ‘I’ indicates that the process or thread exceeds the IO threshold. An ‘M’ indicates that the process exceeds the process memory threshold. This interest reason is only meaningful for processes and therefore not shown for threads. New processes or threads are identified with an ‘N’, terminated processes or threads are identified with a ‘K’. Note that the parm file ‘nonew’, ‘nokill’ and ‘shortlived’ settings are logging only options and therefore ignored in Glance components. HP-UX SunOS AIX NCR Sinix DEC 4 D Disk IOs exceeded threshold HP-UX DEC 5 M Memory used exceeded threshold HP-UX 6 F First-response time exceeded threshold 7 T Transaction rate exceeded threshold 8 c Wait for CPU percentage exceeded threshold 9 d Wait for disk percentage exceeded threshold 10 m Wait for memory percentage exceeded threshold 11 i Wait for impede percentage exceeded threshold 12 blank Special purpose field SunOS AIX NCR Sinix WinNT 5 blank Not Used SunOS AIX NCR Sinix DEC WinNT 6 blank Not Used 7 blank Not Used 8 blank Not Used 9 blank Not Used 10 blank Not Used 11 blank Not Used 12 blank Special purpose field PROC_INTERVAL_ALIVE ---------------------------------- The number of seconds that the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) was alive during the interval. This may be less than the time of the interval if the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) was new or died during the interval. PROC_IO_BYTE ---------------------------------- On HP-UX, this is the total number of physical IO KBs (unless otherwise specified) that was used by this process or kernel thread, either directly or indirectly, during the interval. On all other systems, this is the total number of physical IO KBs (unless otherwise specified) that was used by this process during the interval. IOs include disk, terminal, tape and network IO. On HP-UX, indirect IOs include paging and deactivation/reactivation activity done by the kernel on behalf of the process or kernel thread. Direct IOs include disk, terminal, tape, and network IO, but exclude all NFS traffic. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On SUN, counts in the MB ranges in general can be attributed to disk accesses and counts in the KB ranges can be attributed to terminal IO. This is useful when looking for processes with heavy disk IO activity. This may vary depending on the sample interval length. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_IO_BYTE_CUM ---------------------------------- On HP-UX, this is the total number of physical IO KBs (unless otherwise specified) that was used by this process or kernel thread, either directly or indirectly, over the cumulative collection time. On all other systems, this is the total number of physical IO KBs (unless otherwise specified) that was used by this process over the cumulative collection time. IOs include disk, terminal, tape and network IO. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On HP-UX, indirect IOs include paging and deactivation/reactivation activity done by the kernel on behalf of the process or kernel thread. Direct IOs include disk, terminal, tape, and network IO, but exclude all NFS traffic. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_IO_BYTE_RATE ---------------------------------- On HP-UX, this is the number of physical IO KBs per second that was used by this process or kernel thread, either directly or indirectly, during the interval. On all other systems, this is the number of physical IO KBs per second that was used by this process during the interval. IOs include disk, terminal, tape and network IO. On HP-UX, indirect IOs include paging and deactivation/reactivation activity done by the kernel on behalf of the process or kernel thread. Direct IOs include disk, terminal, tape, and network IO, but exclude all NFS traffic. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On SUN, counts in the MB ranges in general can be attributed to disk accesses and counts in the KB ranges can be attributed to terminal IO. This is useful when looking for processes with heavy disk IO activity. This may vary depending on the sample interval length. Certain types of disk IOs are not counted by AIX at the process level, so they are excluded from this metric. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_IO_BYTE_RATE_CUM ---------------------------------- On HP-UX, this is the average number of physical IO KBs per second that was used by this process or kernel thread, either directly or indirectly, over the cumulative collection time. On all other systems, this is the average number of physical IO KBs per second that was used by this process over the cumulative collection time. IOs include disk, terminal, tape and network IO. The cumulative collection time is defined from the point in time when either: a) the process (or thread) was first started, or b) the performance tool was first started, or c) the cumulative counters were reset (relevant only to Glance, if available for the given platform), whichever occurred last. On HP-UX, all cumulative collection times and intervals start when the midaemon starts. On other Unix systems, non-process collection time starts from the start of the performance tool, process collection time starts from the start time of the process or measurement start time, which ever is older. Regardless of the process start time, application cumulative intervals start from the time the performance tool is started. On systems where the performance components are 32-bit or where the 64-bit model is LLP64 (Windows), all INTERVAL_CUM metrics will start reporting “o/f” (overflow) after the performance agent (or the midaemon on HPUX) has been up for 466 days and the cumulative metrics will fail to report accurate data after 497 days. On Linux, Solaris and AIX, if measurement is started after the system has been up for more than 466 days, cumulative process CPU data won’t include times accumulated prior to the performance tool’s start and a message will be logged to indicate this. On HP-UX, indirect IOs include paging and deactivation/reactivation activity done by the kernel on behalf of the process or kernel thread. Direct IOs include disk, terminal, tape, and network IO, but exclude all NFS traffic. On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. On SUN, counts in the MB ranges in general can be attributed to disk accesses and counts in the KB ranges can be attributed to terminal IO. This is useful when looking for processes with heavy disk IO activity. This may vary depending on the sample interval length. Linux release versions vary with regards to the amount of process-level IO statistics that are available. Some kernels instrument only disk IO, while some provide statistics for all devices together (including tty and other devices with disk IO). When it is available from your specific release of Linux, the PROC_DISK_PHYS* metrics will report pages of disk IO specifically. The PROC_IO* metrics will report the sum of all types of IO including disk IO, in Kilobytes or KB rates. These metrics will have “na” values on kernels that do not support the instrumentation. For multi-threaded processes, some Linux kernels only report IO statistics for the main thread. In that case, patches are available that will allow the process instrumentation to report the sum of all thread’s IOs, and will also enable per-thread reporting. PROC_IPC_SUBSYSTEM_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on the InterProcess Communication (IPC) subsystems (waiting for its interprocess communication activity to complete) during the interval. This is the sum of processes or kernel threads in the IPC, MSG, SEM, PIPE, SOCKT (that is, sockets) and STRMS (that is, streams IO) wait states. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_IPC_SUBSYSTEM_WAIT_TIME ---------------------------------- The time, in seconds, the process or kernel thread was blocked on the InterProcess Communication (IPC) subsystems (waiting for its interprocess communication activity to complete) during the interval. This is the sum of processes or kernel threads in the IPC, MSG, SEM, PIPE, SOCKT (that is, sockets) and STRMS (that is, streams IO) wait states. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_LAN_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on LAN (waiting for IO over the LAN to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_LAN_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on LAN (waiting for IO over the LAN to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_LS_ID ---------------------------------- PROC_LS_ID represents the zone-id of the zone, this process is running in. This metric is only available on Solaris 10 and above versions. PROC_MAJOR_FAULT ---------------------------------- Number of major page faults for this process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) during the interval. On HP-UX, major page faults and minor page faults are a subset of vfaults (virtual faults). Stack and heap accesses can cause vfaults, but do not result in a disk page having to be loaded into memory. PROC_MEM_LOCKED ---------------------------------- The number of KBs of virtual memory allocated by the process, marked as locked memory. This is the non-paged pool memory of the process. This memory is allocated from the system-wide non-paged pool, and is not affected by the pageout process. Device drivers may allocate memory from the non-paged pool, charging quota against the current (caller) thread. The kernel and driver code use the non-paged pool for data that should always be in the physical memory. The size of the non-paged pool is limited to approximately 128 MB on Windows NT systems and to 256 MB on Windows 2000 systems. The failure to allocate memory from the non-paged pool can cause a system crash. PROC_MEM_RES ---------------------------------- The size (in KB) of resident memory allocated for the process(or kernel thread, if HP-UX/Linux Kernel 2.6 and above). On HP-UX, the calculation of this metric differs depending on whether this process has used any CPU time since the midaemon process was started. This metric is less accurate and does not include shared memory regions in its calculation when the process has been idle since the midaemon was started. On HP-UX, for processes that use CPU time subsequent to midaemon startup, the resident memory is calculated as RSS = sum of private region pages + (sum of shared region pages / number of references) The number of references is a count of the number of attachments to the memory region. Attachments, for shared regions, may come from several processes sharing the same memory, a single process with multiple attachments, or combinations of these. This value is only updated when a process uses CPU. Thus, under memory pressure, this value may be higher than the actual amount of resident memory for processes which are idle because their memory pages may no longer be resident or the reference count for shared segments may have changed. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. A value of “na” is displayed when this information is unobtainable. This information may not be obtainable for some system (kernel) processes. It may also not be available for processes. On AIX, this is the same as the RSS value shown by “ps v”. On Windows, this is the number of KBs in the working set of this process. The working set includes the memory pages touched recently by the threads of the process. If free memory in the system is above a threshold, then pages are left in the working set even if they are not in use. When free memory falls below a threshold, pages are trimmed from the working set, but not necessarily paged out to disk from memory. If those pages are subsequently referenced, they will be page faulted back into the working set. Therefore, the working set is a general indicator of the memory resident set size of this process, but it will vary depending on the overall status of memory on the system. Note that the size of the working set is often larger than the amount of pagefile space consumed (PROC_MEM_VIRT). PROC_MEM_VIRT ---------------------------------- The size (in KB) of virtual memory allocated for the process(or kernel thread, if HP-UX/Linux Kernel 2.6 and above). On HP-UX, this consists of the sum of the virtual set size of all private memory regions used by this process, plus this process’ share of memory regions which are shared by multiple processes. For processes that use CPU time, the value is divided by the reference count for those regions which are shared. On HP-UX, this metric is less accurate and does not reflect the reference count for shared regions for processes that were started prior to the midaemon process and have not used any CPU time since the midaemon was started. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. On all other Unix systems, this consists of private text, private data, private stack and shared memory. The reference count for shared memory is not taken into account, so the value of this metric represents the total virtual size of all regions regardless of the number of processes sharing access. Note also that lazy swap algorithms, sparse address space malloc calls, and memory-mapped file access can result in large VSS values. On systems that provide Glance memory regions detail reports, the drilldown detail per memory region is useful to understand the nature of memory allocations for the process. A value of “na” is displayed when this information is unobtainable. This information may not be obtainable for some system (kernel) processes. It may also not be available for processes. On Windows, this is the number of KBs the process has used in the paging file(s). Paging files are used to store pages of memory used by the process, such as local data, that are not contained in other files. Examples of memory pages which are contained in other files include pages storing a program’s .EXE and .DLL files. These would not be kept in pagefile space. Thus, often programs will have a memory working set size (PROC_MEM_RES) larger than the size of its pagefile space. On Linux this value is rounded to PAGESIZE. PROC_MEM_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on memory (waiting for memory resources to become available) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_MEM_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on VM (waiting for virtual memory resources to become available) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_MINOR_FAULT ---------------------------------- Number of minor page faults for this process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) during the interval. On HP-UX, major page faults and minor page faults are a subset of vfaults (virtual faults). Stack and heap accesses can cause vfaults, but do not result in a disk page having to be loaded into memory. PROC_NFS_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on NFS (waiting for network file system IO to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_NFS_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on NFS (waiting for its network file system IO to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_OTHER_IO_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on “other IO” during the interval. “Other IO” includes all IO directed at a device (connected to the local computer) which is not a terminal or LAN. Examples of “other IO” devices are local printers, tapes, instruments, and disks. Time waiting for character (raw) IO to disks is included in this measurement. Time waiting for file system buffered IO to disks will typically been seen as IO or CACHE wait. Time waiting for IO to NFS disks is reported as NFS wait. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_OTHER_IO_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on other IO during the interval. “Other IO” includes all IO directed at a device (connected to the local computer) which is not a terminal or LAN. Examples of “other IO” devices are local printers, tapes, instruments, and disks. Time waiting for character (raw) IO to disks is included in this measurement. Time waiting for file system buffered IO to disks will typically been seen as IO or CACHE wait. Time waiting for IO to NFS disks is reported as NFS wait. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_OTHER_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on other (unknown) activities during the interval. This includes processes or kernel threads that were started and subsequently suspended before the midaemon was started and have not been resumed, or the block state is unknown. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_OTHER_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on other (unknown) activities during the interval. This includes processes or kernel threads that were started and subsequently suspended before the midaemon was started and have not been resumed, or the block state is unknown. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_PAGEFAULT ---------------------------------- The number of page faults that occurred during the interval for the process(or kernel threads, if HP-UX/Linux Kernel 2.6 and above). PROC_PAGEFAULT_RATE ---------------------------------- The number of page faults per second that occurred during the interval for the process(or kernel threads, if HP-UX/Linux Kernel 2.6 and above). PROC_PARENT_PROC_ID ---------------------------------- The parent process’ PID number. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_PRI ---------------------------------- On Unix systems, this is the dispatch priority of a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) at the end of the interval. The lower the value, the more likely the process is to be dispatched. On Windows, this is the current base priority of this process. On HP-UX, whenever the priority is changed for the selected process or kernel thread, the new value will not be reflected until the process or kernel thread is reactivated if it is currently idle (for example, SLEEPing). On HP-UX, the lower the value, the more the process or kernel thread is likely to be dispatched. Values between zero and 127 are considered to be “real- time” priorities, which the kernel does not adjust. Values above 127 are normal priorities and are modified by the kernel for load balancing. Some special priorities are used in the HP-UX kernel and subsystems for different activities. These values are described in /usr/include/sys/param.h. Priorities less than PZERO 153 are not signalable. Note that on HP-UX, many network-related programs such as inetd, biod, and rlogind run at priority 154 which is PPIPE. Just because they run at this priority does not mean they are using pipes. By examining the open files, you can determine if a process or kernel thread is using pipes. For HP-UX 10.0 and later releases, priorities between -32 and -1 can be seen for processes or kernel threads using the Posix Real-time Schedulers. When specifying a Posix priority, the value entered must be in the range from 0 through 31, which the system then remaps to a negative number in the range of -1 through -32. Refer to the rtsched man pages for more information. On a threaded operating system, such as HP-UX 11.0 and beyond, this metric represents a kernel thread characteristic. If this metric is reported for a process, the value for its last executing kernel thread is given. For example, if a process has multiple kernel threads and kernel thread one is the last to execute during the interval, the metric value for kernel thread one is assigned to the process. On AIX, values for priority range from 0 to 127. Processes running at priorities less than PZERO (40) are not signalable. On Windows, the higher the value the more likely the process or thread is to be dispatched. Values for priority range from 0 to 31. Values of 16 and above are considered to be “realtime” priorities. Threads within a process can raise and lower their own base priorities relative to the process’s base priority. PROC_PRI_WAIT_PCT ---------------------------------- The percentage of time during the interval the process or kernel thread was blocked on priority (waiting for its priority to become high enough to get the CPU). On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_PRI_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on PRI (waiting for its priority to become high enough to get the CPU) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_PRMID ---------------------------------- The PRM Group ID this process is assigned to. The PRM group configuration is kept in the PRM configuration file. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_PROC_ARGV1 ---------------------------------- The first argument (argv[1]) of the process argument list or the second word of the command line, if present. (For kernel threads, if HP-UX/Linux Kernel 2.6 and above this metric returns the value of the associated process). The HP Performance Agent logs the first 32 characters of this metric. For releases that support the parm file javaarg flag, this metric may not be the first argument. When javaarg=true, the value of this metric is replaced (for java processes only) by the java class or jar name. This can then be useful to construct parm file java application definitions using the argv1= keyword. PROC_PROC_CMD ---------------------------------- The full command line with which the process was initiated. (For kernel threads, if HP-UX/Linux Kernel 2.6 and above this metric returns the value of the associated process). On HP-UX, the maximum length returned depends upon the version of the OS, but typically up to 1020 characters are available. On other Unix systems, the maximum length is 4095 characters. On Linux, if the command string exceeds 4096 characters, the kernel instrumentation may not report any value. If the command line contains special characters, such as carriage return and tab, these characters will be converted to , , and so on. PROC_PROC_ID ---------------------------------- The process ID number (or PID) of this process(or associated process for kernel threads, if HPUX/LInux Kernel 2.6 and above) that is used by the kernel to uniquely identify the process. Process numbers are reused, so they only identify a process for its lifetime. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_PROC_NAME ---------------------------------- The process(or kernel thread, if HP-UX/Linux Kernel 2.6 and above) program name. It is limited to 16 characters. On Unix systems, this is derived from the 1st parameter to the exec(2) system call. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. On Windows, the “System Idle Process” is not reported by Perf Agent since Idle is a process that runs to occupy the processors when they are not executing other threads. Idle has one thread per processor. PROC_REVERSE_PRI ---------------------------------- The process priority in a range of 0 to 127, with a lower value interpreted as a higher priority. Since priority ranges can be customized, this metric provides a standardized way of interpreting priority that is consistent with other versions of Unix. This is the same value as reported in the PRI field by the ps command when the -c option is not used. PROC_RUN_TIME ---------------------------------- The elapsed time since a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) started, in seconds. This metric is less than the interval time if the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above) was not alive during the entire first or last interval. On a threaded operating system such as HP-UX 11.0 and beyond, this metric is available for a process or kernel thread. PROC_SEM_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on semaphores (waiting on a semaphore operation to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_SEM_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on semaphores (waiting on a semaphore operation to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_SLEEP_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on SLEEP (waiting to awaken from sleep system calls) during the interval. A process or kernel thread enters the SLEEP state by putting itself to sleep using system calls such as sleep, wait, pause, sigpause, sigsuspend, poll and select. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_SLEEP_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on SLEEP (waiting to awaken from sleep system calls) during the interval. A process or kernel thread enters the SLEEP state by putting itself to sleep using system calls such as sleep, wait, pause, sigpause, sigsuspend, poll and select. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_STARTTIME ---------------------------------- The creation date and time of the process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above). PROC_STOP_HISTOGRAM ---------------------------------- A bar chart of the process stop reasons. Shows breakout of the percent of time processes were in different wait states. The percent of time = PROC_CPU_TOTAL_UTIL_CUM + PROC_PRI_WAIT_PCT + PROC_DISK_SUBSYSTEM_WAIT_PCT + PROC_MEM_WAIT_PCT + PROC_LAN_WAIT_PCT ASCII and binary files contain a line of ASCII characters that make up one row of a printed histogram. This can be a quick way to get a graphical view of the wait states on a character mode terminal display. PROC_STOP_REASON ---------------------------------- A text string describing what caused the process (or kernel thread, if HP- UX/Linux Kernel 2.6 and above) to stop executing. For example, if the process is waiting for a CPU while higher priority processes are executing, then its block reason is PRI. A complete list of block reasons follows: HP-UX String Reason for Process Block ------------------------------------ CACHE Waiting at the buffer cache level trying to lock down a buffer cache structure, or waiting for an IO operation to or from a buffer cache to complete. File system access will block on IO more often than CACHE on HP-UX 11.x. CDFS Waiting for CD-ROM file system node structure allocation or locks while accessing a CD-ROM device through the file system. died Process terminated during the interval. DISK Waiting for an IO operation to complete at the logical device manager or disk driver level. Waits from raw disk IO and diagnostic requests can be seen here. Buffered IO requests can also block on DISK, but will more often be seen waiting on “IO”. CDFS access will block on “CDFS”. Virtual memory activity will block on “VM”. GRAPH Waiting for a graphics card or framebuf semaphore operation. INODE Waiting while accessing an inode structure. This includes inode gets and waiting due to inode locks. IO Waiting for IO to local disks, printers, tapes, or instruments to complete (above the driver, but below the buffer cache). Both file system and raw disk access can block in this state. CDFS access will block on “CDFS”. Virtual memory activity will block on “VM”. IPC Waiting for a process or kernel thread event (that is, waiting for a child to receive a signal). This includes both inter and intra process or kernel thread operations, such as IPC locks, kernel thread mutexes, and database IPC operations. System V message queue operations will block on “MESG”, while semaphore operations will block on “SEM”. JOBCL Waiting for tracing resume, debug resume, or job control start. A background process incurs this block when attempting to write to a terminal set with “stty tostop”. On HP-UX 11i, scheduler activation threads (user threads) will show this block. LAN Waiting for a network IO completion. This includes waiting on the LAN hardware and low level LAN device driver. It does not include waiting on the higher level network software such as the streams based transport or NFS, which has its own stop state. MESG Waiting for a System V message queue operation such as msgrcv or msgsnd. new Process was created (via the fork/vfork system calls) during the interval. NFS Waiting for a Networked File System request to complete. This includes both NFS V2 and V3 requests. This does not include stops where kernel threads or deamons are waiting for a NFS event or request (such as biod or nfsd). These will block on SLEEP to show they are waiting for some activity. NONE Zombie process - waiting to die. OTHER The process was started before the midaemon was started and has not been resumed, or the block state is unknown. PIPE Waiting for operations involving pipes. This includes opening, closing, reading, and writing using pipes. Named pipes will block on PIPE. PRI Waiting because a higher priority process is running, or waiting for a spinlock or alpha semaphore. RPC Waiting for remote procedure call operations to complete. This includes both NFS and DCE RPC requests. SEM Waiting for a System V semaphore operation (such as semop, semget, or semctl) or waiting for a memory mapped file semaphore operation (such as msem_init or msem_lock). SLEEP Waiting because the process put itself to sleep using system calls such as sleep, wait, pause, sigpause, poll, sigsuspend and select. This is the standard stop reason for idle system daemons. SOCKT Waiting for an operation to complete while accessing a device through a socket. This is used primarily in networking code and includes all protocols using sockets (X25, UDP, TCP, and so on). STRMS Waiting for an operation to complete while accessing a “streams” device. This is the normal stop reason for kernel threads and daemons waiting for a streams event. This includes the network transport and pseudo terminal IO requests. For example, waiting for a read on a streams device or waiting for an internal streams synchronization. SYSTM Waiting for access to a system resource or lock. These resources include data structures from the LVM, VFS, UFS, JFS, and Disk Quota subsystems. “SYSTM” is the “catch-all” wait state for blocks on system resources that are not common enough or long enough to warrant their own stop state. TERM Waiting for a non-streams terminal transfer (tty or pty). VM Waiting for a virtual memory operation to complete, or waiting for free memory, or blocked while creating/ accessing a virtual memory structure. For a process or kernel thread currently running, the last reason it was stopped before obtaining the CPU is shown. On HP-UX 11.0 and beyond, mikslp.text (located in /opt/perf/lib) contains the blocking functions and their corresponding block states for use by midaemon. On a threaded operating system, such as HP-UX 11.0 and beyond, this metric represents a kernel thread characteristic. If this metric is reported for a process, the value for its last executing kernel thread is given. For example, if a process has multiple kernel threads and kernel thread one is the last to execute during the interval, the metric value for kernel thread one is assigned to the process. SunOS SunOS 5.X String Reason for Process Block ------------------------------------ died Process terminated during the interval. new Process was created (via the exec() system call) during the interval. NONE Process is ready to run. It is not apparent that the process is blocked. OTHER Waiting for a reason not decipherable by the measurement software. PMEM Waiting for more primary memory. PRI Process is on the run queue. SLEEP Waiting for an event to complete. TRACE Received a signal to stop because parent is tracing this process. ZOMB Process has terminated and the parent is not waiting. On SunOS 5.X, instead of putting the scheduler to sleep and waking it up, the kernel just stops and continues the scheduler as needed. This is done by changing the state of the scheduler to ws_stop, which is when you see the TRACE state. This is for efficiency and happens every clock tick so the “sched” process will always appear to be in a “TRACE” state. AIX String Reason for Process Block ------------------------------------ died Process terminated during the interval. LOCK Waiting either for serialization or phys lock. new Process was created (via the exec() system call) during the interval. NONE Process is ready to run. It is not apparent that the process is blocked. OTHER Waiting for a reason not decipherable by the measurement software. PRI Process is on the run queue. SLEEP Waiting for an event to complete. TIMER Waiting for the timer. TRACE Received a signal to stop because parent is tracing this process. VM Waiting for a virtual memory operation to complete. ZOMB Process has terminated and the parent is not waiting. NCR Sinix String Reason for Process Block ------------------------------------ died Process terminated during the interval. new Process was created (via the exec() system call) during the interval. NONE Process is ready to run. It is not apparent that the process is blocked. OTHER Waiting for a reason not decipherable by the measurement software. PMEM Waiting for more primary memory. PRI Process is on the run queue. SLEEP Waiting for an event to complete. TRACE Received a signal to stop the process for tracing. This will occur when a process is stopped waiting on the tty device after having been backgrounded, or when the process is suspended by a debugger, or when a privileged process is accessing its proc structure to get process information. ZOMB Process has terminated and the parent is not waiting. DEC Linux String Reason for Process Block ------------------------------------ died Process terminated during the interval. new Process was created (via the exec() system call) during the interval. NONE Process is ready to run. It is not apparent that the process is blocked. OTHER Waiting for a reason not decipherable by the measurement software. PRI Process is on the run queue. SLEEP Waiting for an event to complete. TRACE Received a signal to stop because parent is tracing this process. ZOMB Process has terminated and the parent is not waiting. PROC_SYS_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on system resources during the interval. These resources include data structures from the LVM, VFS, UFS, JFS, and Disk Quota subsystems. “SYSTM” is the “catch-all” wait state for blocks on system resources that are not common enough or long enough to warrant their own stop state. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_SYS_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on SYSTM (that is, system resources) during the interval. These resources include data structures from the LVM, VFS, UFS, JFS, and Disk Quota subsystems. “SYSTM” is the “catch-all” wait state for blocks on system resources that are not common enough or long enough to warrant their own stop state. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_TERM_IO_WAIT_PCT ---------------------------------- The percentage of time the process or kernel thread was blocked on terminal IO (waiting for its terminal IO to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. A percentage of time spent in a wait state is calculated as the time a kernel thread (or all kernel threads of a process) spent waiting in this state, divided by the alive time of the kernel thread (or all kernel threads of the process) during the interval. If this metric is reported for a kernel thread, the percentage value is for that single kernel thread. If this metric is reported for a process, the percentage value is calculated with the sum of the wait and alive times of all of its kernel threads. For example, if a process has 2 kernel threads, one sleeping for the entire interval and one waiting on terminal input for the interval, the process wait percent values will be 50% on Sleep and 50% on Terminal. The kernel thread wait values will be 100% on Sleep for the first kernel thread and 100% on Terminal for the second kernel thread. For another example, consider the same process as above, with 2 kernel threads, one of which was created half-way through the interval, and which then slept for the remainder of the interval. The other kernel thread was waiting for terminal input for half the interval, then used the CPU actively for the remainder of the interval. The process wait percent values will be 33% on Sleep and 33% on Terminal (each one third of the total alive time). The kernel thread wait values will be 100% on Sleep for the first kernel thread and 50% on Terminal for the second kernel thread. PROC_TERM_IO_WAIT_TIME ---------------------------------- The time, in seconds, that the process or kernel thread was blocked on terminal IO (waiting for its terminal IO to complete) during the interval. On a threaded operating system, such as HP-UX 11.0 and beyond, process wait time is calculated by summing the wait times of its kernel threads. If this metric is reported for a kernel thread, the value is the wait time of that single kernel thread. If this metric is reported for a process, the value is the sum of the wait times of all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. For multi-threaded processes, the wait times can exceed the length of the measurement interval. PROC_THREAD_COUNT ---------------------------------- The total number of kernel threads for the current process. On Linux systems with Kernel 2.5 and below, every thread has its own process ID so this metric will always be 1. On Solaris systems, this metric reflects the total number of Light Weight Processes (LWPs) associated with the process. PROC_TTY ---------------------------------- The controlling terminal for a process(or kernel threads, if HP-UX/Linux Kernel 2.6 and above). This field is blank if there is no controlling terminal. On HP-UX, Linux, and AIX, this is the same as the “TTY” field of the ps command. On all other Unix systems, the controlling terminal name is found by searching the directories provided in the /etc/ttysrch file. See man page ttysrch(4) for details. The matching criteria field (“M”, “F” or “I” values) of the ttysrch file is ignored. If a terminal is not found in one of the ttysrch file directories, the following directories are searched in the order here: “/dev”, “/dev/pts”, “/dev/term” and “dev/xt”. When a match is found in one of the “/dev” subdirectories, “/dev/” is not displayed as part of the terminal name. If no match is found in the directory searches, the major and minor numbers of the controlling terminal are displayed. In most cases, this value is the same as the “TTY” field of the ps command. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_USER_NAME ---------------------------------- On Unix systems, this is real user name of a process or the login account (from /etc/passwd) of a process (or kernel thread, if HP-UX/Linux Kernel 2.6 and above). If more than one account is listed in /etc/passwd with the same user ID (uid) field, the first one is used. If an account cannot be found that matches the uid field, then the uid number is returned. This would occur if the account was removed after a process was started. On Windows, this is the process owner account name, without the domain name this account resides in. On HP-UX, this metric is specific to a process. If this metric is reported for a kernel thread, the value for its associated process is given. PROC_VOLUNTARY_CSWITCH ---------------------------------- The number of times a process (or kernel thread, if HP-UX) has given up the CPU before an external event preempted it during the interval. Examples of voluntary switches include calls to sleep(2) and select(2). On a threaded operating system, such as HP-UX 11.0 and beyond, process usage of a resource is calculated by summing the usage of that resource by its kernel threads. If this metric is reported for a kernel thread, the value is the resource usage by that single kernel thread. If this metric is reported for a process, the value is the sum of the resource usage by all of its kernel threads. Alive kernel threads and kernel threads that have died during the interval are included in the summation. RECORD_TYPE ---------------------------------- ASCII string that identifies the record. Possibilities include: GLOB for global 5 minute detail GSUM for global hourly summary APPL for application 5 minute detail ASUM for application hourly summary CONF for configuration TRAN for transaction tracker detail TSUM for transaction tracker summary Except for Windows Desktop, this also includes: PROC for process 1 minute detail DISK for disk device 5 minute detail DSUM for disk device summary On HP-UX, this also includes: VOLS for logical volume disk detail VSUM for logical volume disk summary STATDATE ---------------------------------- The end date timestamp of the interval for which the information in this record was captured, based on local time. The date is an ASCII field in mm/dd/yyyy format unless localized. If localized, the separators may be different and the subfield may be in a different sequence. In ASCII files this field will always contain 10 characters. Each subfield (mm, dd, yyyy) will contain a leading zero if the value is less than 10. This metric is extracted from GBL_STATTIME, which is obtained using the time() system call at the time of data collection. This field responds to language localization. For example, in Italy the field would appear as dd/mm/yyyy and in Japan it would be yyyy/mm/dd. In binary files this field is in MPE CALENDAR format in the least significant 16 bits of the field. The most significant 16 bits should all be zero. Dividing the field by 512 will isolate the year (that is, 94). This field MOD 512 will isolate the day of the year. STATTIME ---------------------------------- The local time of day for the end of the interval. The time is an ASCII field in hh:mm:ss 24-hour format. This field will always contain 8 characters in ASCII files. The three subfields (hh, mm, ss) will contain a leading zero if the value is less than 10. This metric is extracted from GBL_STATTIME, which is obtained using the time() system call at the end of the interval. This field responds to language localization. In binary files this field contains four byte size subfields. The most significant byte contains the hour, the next most significant byte contains the minute, then the seconds and finally the tenths of a second. The left two bytes can be isolated by dividing by 65536. HHMM = TIME/65536. Then HOUR = HHMM/256 and MINUTE = HHMM mod 256. SSTS = TIME mod 65536. Then SECOND = SSTS/256. TBL_BUFFER_CACHE_AVAIL ---------------------------------- The size (in KBs unless otherwise specified) of the file system buffer cache on the system. On HP-UX 11i v2 and below, these buffers are used for all file system IO operations, as well as all other block IO operations in the system (exec, mount, inode reading, and some device drivers). If dynamic buffer cache is enabled, the system allocates a percentage of available memory not less than dbc_min_pct nor more than dbc_max_pct, depending on the system needs at any given time. On systems with a static buffer cache, this value will remain equal to bufpages, or not less than dbc_min_pct nor more than dbc_max_pct. On HP-UX 11i v3 and above the limits of the file system buffer cache which is still being used for file system metadata are automatically set to certain percentages of filecache_min and filecache_max. On SUN, this value is obtained by multiplying the system page size times the number of buffer headers (nbuf). For example, on a SPARCstation 10 the buffer size is usually (200 (page size buffers) * 4096 (bytes/page) = 800 KB). NOTE: (For SUN systems with VERITAS File System installed) Veritas implemented their Direct I/O feature in their file system to provide mechanism for bypassing the Unix system buffer cache while retaining the on disk structure of a file system. The way in which Direct I/O works involves the way the system buffer cache is handled by the Unix OS. Once the VERITAS file system returns with the requested block, instead of copying the content to a system buffer page, it copies the block into the application’s buffer space. That’s why if you have installed vxfs on your system, the TBL_BUFFER_CACHE_AVAIL can exceed the TBL_BUFFER_CACHE_HWM metric. On SUN, the buffer cache is a memory pool used by the system to cache inode, indirect block and cylinder group related disk accesses. This is different from the traditional concept of a buffer cache that also holds file system data. On Solaris 5.X, as file data is cached, accesses to it show up as virtual memory IOs. File data caching occurs through memory mapping managed by the virtual memory system, not through the buffer cache. The “nbuf” value is dynamic, but it is very hard to create a situation where the memory cache metrics change, since most systems have more than adequate space for inode, indirect block, and cylinder group data caching. This cache is more heavily utilized on NFS file servers. On AIX, this cache is used for all block IO. On AIX System WPARs, this metric is NA. Win3x/95 The size of the disk cache (Windows 95 only). The disk cache size is adjusted automatically to compensate for memory demand and installed RAM. The data collector samples the size every 30 seconds and reports the average of the samples recorded during the measurement interval. TBL_BUFFER_CACHE_USED ---------------------------------- The size (in KBs unless otherwise specified) of the sum of the currently used buffers. On HP-UX 11i v2 and below, this is normally greater than the amount requested due to internal fragmentation of the buffer cache. Since this is a cache, it is normal for it to be filled. The buffer cache is used to stage all block IOs to disk. On a dynamic buffer cache configuration, this metric is always equal to TBL_BUFFER_CACHE_AVAIL. With dynamic buffer cache, the system allocates a percentage of available memory not less than dbc_min_pct nor more than dbc_max_pct, depending on the system needs at any given time. On systems with a static buffer cache, this value will remain equal to bufpages, or not less than dbc_min_pct nor more than dbc_max_pct. With a static buffer cache, this metric shows the amount of memory within the configured size that is actually used. On HP-UX 11i v3 and above this metric value represents the usage of the file system buffer cache which is still being used for file system metadata. On AIX, this is normally greater than the amount requested due to internal fragmentation of the buffer cache. Since this is a cache, it is normal for it to be filled. The buffer cache is used to stage all block IOs to disk. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_FILE_LOCK_AVAIL ---------------------------------- The configured number of file or record locks that can be allocated on the system. Files and/or records are locked by calls to lockf(2). On Linux kernel versions 2.4 and above, available file orrecord locks is a dynamic value which can grow upto max unsigned long. TBL_FILE_LOCK_USED ---------------------------------- The number of file or record locks currently in use. One file can have multiple locks. Files and/or records are locked by calls to lockf(2). On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. TBL_FILE_LOCK_UTIL ---------------------------------- The percentage of configured file or record locks currently in use. On Linux 2.4 and above kernel versions, this may not give correct picture as file or record locks available may change dynamically and can grow upto max unsigned long. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_FILE_TABLE_AVAIL ---------------------------------- The number of entries in the file table. On HP-UX and AIX, this is the configured maximum number of the file table entries used by the kernel to manage open file descriptors. On HP-UX, this is the sum of the “nfile” and “file_pad” values used in kernel generation. On SUN, this is the number of entries in the file cache. This is a size. All entries are not always in use. The cache size is dynamic. Entries in this cache are used to manage open file descriptors. They are reused as files are closed and new ones are opened. The size of the cache will go up or down in chunks as more or less space is required in the cache. On AIX, the file table entries are dynamically allocated by the kernel if there is no entry available. These entries are allocated in chunks. TBL_FILE_TABLE_USED ---------------------------------- The number of entries in the file table currently used by file descriptors. On SUN, this is the number of file cache entries currently used by file descriptors. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_FILE_TABLE_UTIL ---------------------------------- The percentage of file table entries currently used by file descriptors. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_INODE_CACHE_AVAIL ---------------------------------- On HP-UX, this is the configured total number of entries for the incore inode tables on the system. For HP-UX releases prior to 11.2x, this value reflects only the HFS inode table. For subsequent HP-UX releases, this value is the sum of inode tables for both HFS and VxFS file systems (ninode plus vxfs_ninode). On HP-UX, file system directory activity is done through inodes that are stored on disk. The kernel keeps a memory cache of active and recently accessed inodes to reduce disk IOs. When a file is opened through a pathname, the kernel converts the pathname to an inode number and attempts to obtain the inode information from the cache based on the filesystem type. If the inode entry is not in the cache, the inode is read from disk into the inode cache. On HP-UX, the number of used entries in the inode caches are usually at or near the capacity. This does not necessarily indicate that the configured sizes are too small because the tables may contain recently used inodes and inodes referenced by entries in the directory name lookup cache. When a new inode cache entry is required and a free entry does not exist, inactive entries referenced by the directory name cache are used. If after freeing inode entries only referenced by the directory name cache does not create enough free space, the message “inode: table is full” message may appear on the console. If this occurs, increase the size of the kernel parameter, ninode. Low directory name cache hit ratios may also indicate an underconfigured inode cache. On HP-UX, the default formula for the ninode size is: ninode = ((nproc+16+maxusers)+32+ (2*npty)+(4*num_clients)) On all other Unix systems, this is the number of entries in the inode cache. This is a size. All entries are not always in use. The cache size is dynamic. Entries in this cache are reused as files are closed and new ones are opened. The size of the cache will go up or down in chunks as more or less space is required in the cache. Inodes are used to store information about files within the file system. Every file has at least two inodes associated with it (one for the directory and one for the file itself). The information stored in an inode includes the owners, timestamps, size, and an array of indices used to translate logical block numbers to physical sector numbers. There is a separate inode maintained for every view of a file, so if two processes have the same file open, they both use the same directory inode, but separate inodes for the file. TBL_INODE_CACHE_USED ---------------------------------- The number of inode cache entries currently in use. On HP-UX, this is the number of “non-free” inodes currently used. Since the inode table contains recently closed inodes as well as open inodes, the table often appears to be fully utilized. When a new entry is needed, one can usually be found by reusing one of the recently closed inode entries. On HP-UX, file system directory activity is done through inodes that are stored on disk. The kernel keeps a memory cache of active and recently accessed inodes to reduce disk IOs. When a file is opened through a pathname, the kernel converts the pathname to an inode number and attempts to obtain the inode information from the cache based on the filesystem type. If the inode entry is not in the cache, the inode is read from disk into the inode cache. On HP-UX, the number of used entries in the inode caches are usually at or near the capacity. This does not necessarily indicate that the configured sizes are too small because the tables may contain recently used inodes and inodes referenced by entries in the directory name lookup cache. When a new inode cache entry is required and a free entry does not exist, inactive entries referenced by the directory name cache are used. If after freeing inode entries only referenced by the directory name cache does not create enough free space, the message “inode: table is full” message may appear on the console. If this occurs, increase the size of the kernel parameter, ninode. Low directory name cache hit ratios may also indicate an underconfigured inode cache. On HP-UX, the default formula for the ninode size is: ninode = ((nproc+16+maxusers)+32+ (2*npty)+(4*num_clients)) On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_MSG_TABLE_AVAIL ---------------------------------- The configured maximum number of message queues that can be allocated on the system. A message queue is allocated by a program using the msgget(2) call. Refer to the ipcs(1) man page for more information. On SUN, the InterProcess Communication facilities are dynamically loadable. If the amount available is zero, this facility was not loaded when data collection began, and its data is not obtainable. The data collector is unable to determine that a facility has been loaded once data collection has started. If you know a new facility has been loaded, restart the data collection, and the data for that facility will be collected. See ipcs(1) to report on interprocess communication resources. TBL_MSG_TABLE_USED ---------------------------------- On HP-UX, this is the number of message queues currently in use. On all other Unix systems, this is the number of message queues that have been built. A message queue is allocated by a program using the msgget(2) call. See ipcs(1) to list the message queues. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_MSG_TABLE_UTIL ---------------------------------- The percentage of configured message queues currently in use. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_PROC_TABLE_AVAIL ---------------------------------- The configured maximum number of the proc table entries used by the kernel to manage processes. This number includes both free and used entries. On HP-UX, this is set by the NPROC value during system generation. AIX has a “dynamic” proc table, which means that AVAIL has been set higher than should ever be needed. On AIX System WPARs, this metric is NA. TBL_PROC_TABLE_USED ---------------------------------- The number of entries in the proc table currently used by processes. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_PROC_TABLE_UTIL ---------------------------------- The percentage of proc table entries currently used by processes. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. On Solaris non-global zones, this metric is N/A. TBL_SEM_TABLE_AVAIL ---------------------------------- The configured number of semaphore identifiers (sets) that can be allocated on the system. On SUN, the InterProcess Communication facilities are dynamically loadable. If the amount available is zero, this facility was not loaded when data collection began, and its data is not obtainable. The data collector is unable to determine that a facility has been loaded once data collection has started. If you know a new facility has been loaded, restart the data collection, and the data for that facility will be collected. See ipcs(1) to report on interprocess communication resources. TBL_SEM_TABLE_USED ---------------------------------- On HP-UX, this is the number of semaphore identifiers currently in use. On all other Unix systems, this is the number of semaphore identifiers that have been built. A semaphore identifier is allocated by a program using the semget(2) call. See ipcs(1) to list semaphores. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_SEM_TABLE_UTIL ---------------------------------- The percentage of configured semaphores identifiers currently in use. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_SHMEM_ACTIVE ---------------------------------- The size (in KBs unless otherwise specified) of the shared memory segments that have running processes attached to them. This may be less than the amount of shared memory used on the system because a shared memory segment may exist and not have any process attached to it. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_SHMEM_TABLE_AVAIL ---------------------------------- The configured number of shared memory segments that can be allocated on the system. On SUN, the InterProcess Communication facilities are dynamically loadable. If the amount available is zero, this facility was not loaded when data collection began, and its data is not obtainable. The data collector is unable to determine that a facility has been loaded once data collection has started. If you know a new facility has been loaded, restart the data collection, and the data for that facility will be collected. See ipcs(1) to report on interprocess communication resources. TBL_SHMEM_TABLE_USED ---------------------------------- On HP-UX, this is the number of shared memory segments currently in use. On all other Unix systems, this is the number of shared memory segments that have been built. This includes shared memory segments with no processes attached to them. A shared memory segment is allocated by a program using the shmget(2) call. Also refer to ipcs(1). On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_SHMEM_TABLE_UTIL ---------------------------------- The percentage of configured shared memory segments currently in use. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TBL_SHMEM_USED ---------------------------------- The size (in KBs unless otherwise specified) of the shared memory segments. Additionally, it includes memory segments to which no processes are attached. If a shared memory segment has zero attachments, the space may not always be allocated in memory. See ipcs(1) to list shared memory segments. On Unix systems, this metric is updated every 30 seconds or the sampling interval, whichever is greater. TIME ---------------------------------- The local time of day for the start of the interval. The time is an ASCII field in hh:mm:ss 24-hour format. This field will always contain 8 characters in ASCII files. The three subfields (hh, mm, ss) will contain a leading zero if the value is less than 10. This metric is extracted from GBL_STATTIME, which is obtained using the time() system call at the start of the interval. This field responds to language localization. In binary files this field contains four byte size subfields. The most significant byte contains the hour, the next most significant byte contains the minute, then the seconds and finally the tenths of a second. The left two bytes can be isolated by dividing by 65536. HHMM = TIME/65536. Then HOUR = HHMM/256 and MINUTE = HHMM mod 256. SSTS = TIME mod 65536. Then SECOND = SSTS/256. TTBIN_TRANS_COUNT_1 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_10 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_2 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_3 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_4 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_5 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_6 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_7 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_8 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_TRANS_COUNT_9 ---------------------------------- The number of completed transactions in this range during the last interval. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_1 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_10 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_2 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_3 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_4 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_5 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_6 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_7 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_8 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TTBIN_UPPER_RANGE_9 ---------------------------------- The upper range (transaction time) for this bin. There are a maximum of nine user-defined transaction response time bins (TTBIN_UPPER_RANGE). The last bin, which is not specified in the transaction configuration file (ttdconf.mwc on Windows or ttd.conf on UNIX platforms), is the overflow bin and will always have a value of -2 (overflow). Note that the values specified in the transaction configuration file cannot exceed 2147483.6, which is the number of seconds in 24.85 days. If the user specifies any values greater than 2147483.6, the numbers reported for those bins or Service Level Objectives (SLO) will be -2. On SUN systems, this metric is only available on 5.X or later. TT_ABORT ---------------------------------- The number of aborted transactions during the last interval for this transaction. TT_ABORT_WALL_TIME_PER_TRAN ---------------------------------- The average time, in seconds, per aborted transaction during the last interval. On SUN systems, this metric is only available on 5.X or later. TT_APP_NAME ---------------------------------- The registered ARM Application name. TT_APP_TRAN_NAME ---------------------------------- A concatenation of TT_APP_NAME and TT_NAME. This provides a way to uniquely identify a specific transaction. The field is limited to 60 characters. TT_CLIENT_ADDRESS ---------------------------------- The correlator address. This is the address where the child transaction originated. TT_CLIENT_ADDRESS_FORMAT ---------------------------------- The correlator address format. This shows the protocol family for the client network address. Refer to the ARM API Guide for the list and description of supported address formats. TT_CLIENT_TRAN_ID ---------------------------------- A numerical ID that uniquely identifies the transaction class in this correlator. TT_COUNT ---------------------------------- The number of completed transactions during the last interval for this transaction. TT_CPU_TOTAL_TIME_PER_TRAN ---------------------------------- The average total CPU time, in seconds, consumed by each completed instance of the transaction during the interval. Total CPU time is the sum of the CPU time components for a process or kernel thread, including system, user, context switch, interrupt processing, realtime, and nice utilization values. Per-transaction performance resource metrics represent an average for all completed instances of the given transaction during the interval. If there are no completed transaction instances during an interval, then there are no resources accounted, even though there may be in-progress transactions using resources which have not completed. Resource metrics for in-progress transactions will be shown in the interval after they complete (that is, after the process has called arm_stop). If there is only one completed transaction instance during an interval, then the resources attributed to the transaction will represent the resources used by the process between its call to arm_start and arm_stop, even if arm_start was called before the current interval. Thus, the resource usage time or wall time per transaction can exceed the current collection interval time. If there are several completed transaction instances during an interval for a given transaction, then the resources attributed to the transaction will represent an average for all completed instances during the interval. To obtain the total accumulated resource consumption for all completed transactions during an interval, multiply the resource metric by the number of completed transaction instances during the interval (TT_COUNT). TT_DISK_LOGL_IO_PER_TRAN ---------------------------------- The average number of logical IOs made by (or for) each completed instance of the transaction during the interval. NFS mounted disks are not included in this list. “Disk” refers to a physical drive (that is, “spindle”), not a partition on a drive (unless the partition occupies the entire physical disk). On many Unix systems, logical disk IOs are measured by counting the read and write system calls that are directed to disk devices. Also counted are read and write system calls made indirectly through other system calls, including readv, recvfrom, recv, recvmsg, ipcrecvcn, recfrom, writev, send, sento, sendmsg, and ipcsend. Per-transaction performance resource metrics represent an average for all completed instances of the given transaction during the interval. If there are no completed transaction instances during an interval, then there are no resources accounted, even though there may be in-progress transactions using resources which have not completed. Resource metrics for in-progress transactions will be shown in the interval after they complete (that is, after the process has called arm_stop). If there is only one completed transaction instance during an interval, then the resources attributed to the transaction will represent the resources used by the process between its call to arm_start and arm_stop, even if arm_start was called before the current interval. Thus, the resource usage time or wall time per transaction can exceed the current collection interval time. If there are several completed transaction instances during an interval for a given transaction, then the resources attributed to the transaction will represent an average for all completed instances during the interval. To obtain the total accumulated resource consumption for all completed transactions during an interval, multiply the resource metric by the number of completed transaction instances during the interval (TT_COUNT). TT_DISK_PHYS_IO_PER_TRAN ---------------------------------- The average number of physical disk IOs per second made by each completed instance of the transaction during the interval. For transactions which run for less than the measurement interval, this metric is normalized over the measurement interval. For example, a transaction ran for 1 second and did 50 IOs during its life. If the measurement interval is 5 seconds, it is reported as having done 10 IOs per second. If the measurement interval is 60 seconds, it is reported as having done 50/60 or 0.83 IOs per second. “Disk” in this instance refers to any locally attached physical disk drives (that is, “spindles”) that may hold file systems and/or swap. NFS mounted disks are not included in this list. On HP-UX, since this value is reported by the drivers, multiple physical requests that have been collapsed to a single physical operation (due to driver IO merging) are only counted once. Per-transaction performance resource metrics represent an average for all completed instances of the given transaction during the interval. If there are no completed transaction instances during an interval, then there are no resources accounted, even though there may be in-progress transactions using resources which have not completed. Resource metrics for in-progress transactions will be shown in the interval after they complete (that is, after the process has called arm_stop). If there is only one completed transaction instance during an interval, then the resources attributed to the transaction will represent the resources used by the process between its call to arm_start and arm_stop, even if arm_start was called before the current interval. Thus, the resource usage time or wall time per transaction can exceed the current collection interval time. If there are several completed transaction instances during an interval for a given transaction, then the resources attributed to the transaction will represent an average for all completed instances during the interval. To obtain the total accumulated resource consumption for all completed transactions during an interval, multiply the resource metric by the number of completed transaction instances during the interval (TT_COUNT). TT_FAILED ---------------------------------- The number of Failed transactions during the last interval for this transaction name. TT_INFO ---------------------------------- The registered ARM Transaction Information for this transaction. TT_NAME ---------------------------------- The registered transaction name for this transaction. TT_NUM_BINS ---------------------------------- The number of distribution ranges. On SUN systems, this metric is only available on 5.X or later. TT_SLO_COUNT ---------------------------------- The number of completed transactions that violated the defined Service Level Objective (SLO) by exceeding the SLO threshold time during the interval. TT_SLO_PERCENT ---------------------------------- The percentage of transactions which violate service level objectives. TT_SLO_THRESHOLD ---------------------------------- The upper range (transaction time) of the Service Level Objective (SLO) threshold value. This value is used to count the number of transactions that exceed this user-supplied transaction time value. TT_TERM_TRAN_1_HR_RATE ---------------------------------- For this transaction name, the number of completed transactions calculated to a 1 hour rate. For example, if you completed five of these transactions in a 5 minute window, the rate is 60 transactions per hour. On SUN systems, this metric is only available on 5.X or later. TT_TRAN_1_MIN_RATE ---------------------------------- For this transaction name, the number of completed transactions calculated to a 1 minute rate. For example, if you completed five of these transactions in a 5 minute window, the rate is one transaction per minute. TT_TRAN_ID ---------------------------------- The registered ARM Transaction ID for this transaction class as returned by arm_getid(). A unique transaction id is returned for a unique application id (returned by arm_init), tran name, and meta data buffer contents. TT_UNAME ---------------------------------- The registered ARM Transaction User Name for this transaction. If the arm_init function has NULL for the appl_user_id field, then the user name is blank. Otherwise, if “*” was specified, then the user name is displayed. For example, to show the user name for the armsample1 program, use: appl_id = arm_init(“armsample1”,”*”,0,0,0); To ignore the user name for the armsample1 program, use: appl_id = arm_init(“armsample1”,NULL,0,0,0); TT_USER_MEASUREMENT_AVG ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval. TT_USER_MEASUREMENT_AVG_2 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. HP-UX SunOS AIX WinNT If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval. Sinix If the measurement type is a counter, this metric returns the average counter differences over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_AVG_3 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval. TT_USER_MEASUREMENT_AVG_4 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval. TT_USER_MEASUREMENT_AVG_5 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval. TT_USER_MEASUREMENT_AVG_6 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the average counter differences of the transaction or transaction instance during the last interval. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this returns the average of the values passed on any ARM call for the transaction or transaction instance during the last interval. TT_USER_MEASUREMENT_COUNT ---------------------------------- This returns the total number of times the associated user defined metric (UDM) was sampled during the last interval. TT_USER_MEASUREMENT_COUNT_2 ---------------------------------- This returns the total number of times the associated user defined metric (UDM) was sampled during the last interval. TT_USER_MEASUREMENT_COUNT_3 ---------------------------------- This returns the total number of times the associated user defined metric (UDM) was sampled during the last interval. TT_USER_MEASUREMENT_COUNT_4 ---------------------------------- This returns the total number of times the associated user defined metric (UDM) was sampled during the last interval. TT_USER_MEASUREMENT_COUNT_5 ---------------------------------- This returns the total number of times the associated user defined metric (UDM) was sampled during the last interval. TT_USER_MEASUREMENT_COUNT_6 ---------------------------------- This returns the total number of times the associated user defined metric (UDM) was sampled during the last interval. TT_USER_MEASUREMENT_MAX ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MAX_2 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MAX_3 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MAX_4 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MAX_5 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MAX_6 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the highest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the highest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MIN ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MIN_2 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MIN_3 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MIN_4 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MIN_5 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_MIN_6 ---------------------------------- If the measurement type is a numeric or a string, this metric returns “na”. If the measurement type is a counter, this metric returns the lowest measured counter value over the life of the transaction or transaction instance. The counter value is the difference observed from a counter between the start and the stop (or last update) of a transaction. If the measurement type is a gauge, this metric returns the lowest value passed on any ARM call over the life of the transaction or transaction instance. TT_USER_MEASUREMENT_NAME ---------------------------------- The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string). TT_USER_MEASUREMENT_NAME_2 ---------------------------------- The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string). TT_USER_MEASUREMENT_NAME_3 ---------------------------------- The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string). TT_USER_MEASUREMENT_NAME_4 ---------------------------------- The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string). TT_USER_MEASUREMENT_NAME_5 ---------------------------------- The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string). TT_USER_MEASUREMENT_NAME_6 ---------------------------------- The name of the user defined transactional measurement. The length of the string complies with the ARM 2.0 standard, which is 44 characters long (there are 43 usable characters since this is a NULL terminated character string). TT_WALL_TIME_PER_TRAN ---------------------------------- The average transaction time, in seconds, during the last interval for this transaction. YEAR ---------------------------------- The year, including the century, the data in this record was captured. This metric will contain 4 digits, such as 2002.