Monitoring Agent for Unix OS Version Reference IBM

Transcription

1 Monitoring Agent for Unix OS Version Reference IBM

2

3 Monitoring Agent for Unix OS Version Reference IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 223. This edition applies to version of the Monitoring Agent for Unix OS and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2010, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Monitoring Agent for Unix OS 1 Chapter 2. Dashboards Default dashboards Group widgets for the Default dashboards Custom charts and tables Chapter 3. Eventing thresholds Predefined eventing thresholds Customized eventing thresholds Chapter 4. Attributes Data sets for the monitoring agent Attribute descriptions Agent Active Runtime Status data set Agent Availability Management Status data set 46 AIX AMS data set AIX Defined Users data set AIX Devices data set AIX Logical Volumes data set AIX LPAR data set AIX Memory Per Page (AIX) data set AIX MPIO Attributes data set AIX MPIO Status data set AIX Network Adapters data set AIX Physical Volumes data set AIX System IO data set AIX Volume Groups data set AIX WPAR CPU data set AIX WPAR File System data set AIX WPAR Information data set AIX WPAR Network data set AIX WPAR Physical Memory data set Alerts Table data set Configuration Information data set Data Collection Status data set Disk data set Disk Performance data set FCP Daemon Status data set File Information data set Log File Profile Events data set Log File Profiles data set Log File Regex Statistics data set Log File Status data set Machine Information data set Managed UNIX OS Profiles data set Network data set NFS and RPC Statistics data set Process data set SMP CPU data set Solaris Zones data set System data set TCP Statistics data set Top CPU Processes data set Top Memory Processes data set Unix All Users data set UNIX Devices data set Unix File Comparison data set Unix File Pattern data set Unix Group data set UNIX IP Address data set Unix Memory data set Unix Ping data set Unix Print Queue data set User data set Accessibility features Notices Trademarks Terms and conditions for product documentation 225 IBM Online Privacy Statement Index Copyright IBM Corp. 2010, 2016 iii

6 iv Monitoring Agent for Unix OS Reference

7 Chapter 1. Monitoring Agent for Unix OS The Monitoring Agent for Unix OS offers a central point of management for your Unix OS environment or application. The software provides a comprehensive means for gathering the information that is required to detect problems early and to prevent them. Information is standardized across the system. You can monitor multiple servers from a single console. By using the BegiN_PAC_SHORT_NAME_EnD you can easily collect and analyze Unix OS specific information. Installing and configuring the agent Install the monitoring agent on the system where the application that you want to monitor is located. For more information, see the following documentation in IBM Knowledge Center: v IBM Performance Management v IBM Performance Management on Cloud Copyright IBM Corp. 2010,

8 2 Monitoring Agent for Unix OS Reference

9 Chapter 2. Dashboards Open the Application Performance Dashboard in the Cloud APM console to see a status summary of all your applications. As you drill down to dashboards for specific applications and their supporting elements, more details are available about the selected item. Use the BegiN_PAC_SHORT_NAME_EnD dashboards to proactively monitor your Unix OS deployment. Each dashboard contains one or more group widgets with key performance indicators. After you select an application that includes Unix OS managed systems, you can see Unix OS KPIs in the application dashboard: v At the application level, the Current Component Status stacked bar chart shows an average of the critical, warning, and normal status severities from all the Unix OS managed systems in the application. v Click the Unix OS bar in the Current Component Status chart or expand Components in the navigator Groups section and click Unix OS to see a summary group widget for each Unix OS managed system in the application. v Click inside a Unix OS summary group widget or click a Unix OS managed system from the navigator Unix OS instances section to open a dashboard with details from the selected managed system. For more information about the KPIs, click in the group widget or click in the upper-right corner of the dashboard. Default dashboards UNIX OS The UNIX OS dashboard presents a high level status of the UNIX system. If any metrics have a critical or warning status, click inside the group widget to drill down to a dashboard with more details. AIX LPAR The dashboard presents group widgets of LPAR, detailed CPU usage and memory details. CPU Details The dashboard presents group widgets of selected CPU information, detailed CPU usage and usage details of the selected CPU. CPU Overview The dashboard presents groups widgets of list of machine CPUs, aggregate CPU usage and usage details of aggregate CPU. Look for specific CPU information by clicking on a CPU listed in the table Disk Details The dashboard presents group widgets of selected disk information, detailed disk usage and operations details of a selected disk. Disks Overview The dashboard presents group widgets that list machine disks, aggregate disk operations per second and usage details of aggregate disk. Look for specific disk information by clicking on a disk listed in the table. Events In Monitored Log The dashboard presents group widgets of list events received for that monitored log file Copyright IBM Corp. 2010,

10 File System Detail The dashboard presents groups widgets of selected file system information and detailed file system usage File Systems Overview The dashboard presents group widgets that list machine file systems and aggregate file systems usage. Look for specific file system information by clicking on a file system listed in the table. Memory The dashboard presents group widgets of the memory utilization, proving information on real memory, virtual memory, swap memory and paging information. Monitored Logs The dashboard presents group widgets of list of monitored log files Network Interface Detail The dashboard presents groups widgets of selected network interface, network interface usage and network interface associated errors Network Interfaces Overview The dashboard presents group widgets that list machine network interfaces and aggregate network interfaces usage and error information. Look for specific network interface information by clicking on a network interface listed in the table. Overview The dashboard presents group widgets of CPUs, memory, disks, network utilization on the UNIX system and information on running processes, LPAR and WPARs. Look for detailed information on each metric by clicking inside a group widget. Processes The dashboard presents group widgets of the processes with the highest CPU, memory, virtual memory and CPU time on the UNIX system. Processes details The dashboard presents groups widgets of the processes with the highest CPU, memory, and disk utilization on the UNIX system. Also shown is the status of each network interface and transmission rates over time. Look for correlating processes in the group widgets, and review the utilization over time to help identify the source. WPAR Details The dashboard presents group widgets of selected WPAR information, detailed WPAR usage and detailed WPAR memory usage. WPARs Overview The dashboard presents group widgets that list WPARs, aggregate WPARs CPU and memory usage. Look for specific WPAR information by clicking on a WPAR listed in the table. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. Group widgets for the Default dashboards UNIX OS The UNIX OS dashboard presents a high level status of the UNIX system. If any metrics have a critical or warning status, click inside the group widget to drill down to a dashboard with more details. The following group widgets are available in this dashboard: 4 Monitoring Agent for Unix OS Reference

11 UNIX OS The UNIX OS Status group widget provides a summary of the UNIX OS system status. When you click on this widget, you open the UNIX OS details dashboard. The following KPIs for the group widget are derived from the attributes as described: v Aggregate CPU usage (%): The sum of the System CPU and User CPU attributes in percent. This data is derived from the CPU Busy attribute in the SMP CPU data set. v Memory usage (%): Percent of physical memory in use as non computational memory (AIX only). This represents the percentage of physical memory reserved for filesystem cache. Note: the value -10 indicates Not Available and -20 indicates Not Collected. This data is derived from the Non Comp Mem Pct attribute in the Unix Memory data set. v Network usage (Pkts/sec): The number of packets received and transmitted on all network interfaces per second over the last 30 minutes. The graph shows the data in the last 30 minutes only and is not affected by the historical data time setting. v Number of online CPU Status Critical: The total number of offline processors. v Number of online CPU Status Normal: The total number of online processors. v Number of processes: The number of processes running on the system, including both system and user processes. This data is derived from the System Procs Number attribute in the System data set. v Total disk space (GB): The total size of a file system, expressed in gigabytes. v Total disk usage (%): The total storage space calculated by dividing the total space used by the total space, expressed in gigabytes. v Total real memory (MB): The total number of megabytes of physical memory on a monitored system. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Total Real Mem MB attribute in the Unix Memory data set. AIX LPAR The dashboard presents group widgets of LPAR, detailed CPU usage and memory details. The following group widgets are available in this dashboard: LPAR The LPAR group widget shows detailed information about LPAR configuration. The following KPIs for the group widget are derived from the attributes as described: v Capped Mode: The capped Logical Partition mode: uncapped or capped (and donating if LPAR is configured as dedicated and donating). Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Capped Mode attribute in the AIX LPAR data set. v Donation: The status of the willingness of this LPAR to allow unused CPU cycles to be used by other LPARs. Note: the value -1 indicates Not Collected, 0 indicates disabled, 1 indicates capable, and 2 indicates enabled. This data is derived from the Donation Enablement attribute in the AIX LPAR data set. v Entitlement: The number of entitlement units assigned to this LPAR. Note: the value -10 indicates Not Available, -02 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Entitlement attribute in the AIX LPAR data set. v Name: The name of the logical partition. Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the LPAR Name attribute in the AIX LPAR data set. v Number: The LPAR identification number assigned to this LPAR. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the LPAR Number attribute in the AIX LPAR data set. Chapter 2. Dashboards 5

12 v Number of CPU: The number of active licensed physical CPUs. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Number of Physical CPUs attribute in the AIX LPAR data set. v Shared Mode: The shared Logical Partition mode (dedicated or shared). Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Shared Mode attribute in the AIX LPAR data set. v SMT Mode: The simultaneous multi-threading mode (off or on). Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the SMT Mode attribute in the AIX LPAR data set. v SMT Threads: The number of threads per CPU. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the SMT Threads attribute in the AIX LPAR data set. v Up time: The period of time this LPAR is operational. Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Uptime attribute in the AIX LPAR data set. LPAR CPU Utilization The LPAR CPU Utilization group widget provides detailed information about the CPU usage of an LPAR. The following KPIs for the group widget are derived from the attributes as described: v CPU Busy Time: The logical busy time percentage. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Busy Pct attribute in the AIX LPAR data set. v Entitlement Used: The percentage of the given CPU Entitlement used by this LPAR. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Entitlement Used Pct attribute in the AIX LPAR data set. v Max CPU Used: The percentage of maximum physical CPU available to this LPAR that is actually used. For capped LPARs, this value is the same as CPU Phys Ent Pct. Note: the value -100 indicates Not Available, -200 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Max CPU Cap Used Pct attribute in the AIX LPAR data set. v Timestamp: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the AIX LPAR data set. v Total System CPU Used: The percentage of the Total System CPU used by this LPAR. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Total Used Pct attribute in the AIX LPAR data set. LPAR Memory Utilization The LPAR Memory Utilization group widget provides detailed information about memory usage of an LPAR. The following KPIs for the group widget are derived from the attributes as described: v % Computational Memory Pages: Percent of physical memory in use as computational memory (AIX only). Note: the value -10 indicates Not Available and -20 indicates Not Collected. This data is derived from the Comp Mem Pct attribute in the Unix Memory data set. 6 Monitoring Agent for Unix OS Reference

13 v % Non-Computational Memory Pages: Percent of physical memory in use as non computational memory (AIX only). This represents the percentage of physical memory reserved for filesystem cache. Note: the value -10 indicates Not Available and -20 indicates Not Collected. This data is derived from the Non Comp Mem Pct attribute in the Unix Memory data set. v Timestamp: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Unix Memory data set. CPU Details The dashboard presents group widgets of selected CPU information, detailed CPU usage and usage details of the selected CPU. The following group widgets are available in this dashboard: CPU Usage Details for Processor The CPU Usage Details for Processor group widget provides detailed consumption information in relation to the selected CPU. The following KPIs for the group widget are derived from the attributes as described: v % I/O Wait: The percent of wait I/O CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use Wait I/O to indicate how effectively the system or a processor is using disks. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platform. This data is derived from the Wait I/O attribute in the SMP CPU data set. v % System: Percent of system CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine the percentage of system or per processor CPU time devoted to executing UNIX system kernel code. System CPU time includes time spent executing system calls and performing administrative functions. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the System CPU attribute in the SMP CPU data set. v % User: Percent of user CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine the percentage of system or per processor CPU time devoted to user processes. User CPU time includes time spent executing both user program and library functions. It does not include CPU time spent executing system calls. The ratio between user and system CPU time varies, depending on the kinds of programs executing. If user CPU is extremely high and adversely affecting system performance, you might want to determine which user programs are preventing the CPU from functioning at its normal speed. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the User CPU attribute in the SMP CPU data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the SMP CPU data set. CPU Usage Percentage The CPU Usage Percentage group widget provides detailed percentage information about the selected CPU. The following KPIs for the group widget are derived from the attributes as described: v % Busy: The sum of the System CPU and User CPU attributes in percent. Valid entries in the range 0 to 100. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use to determine system workload or per processor workload of the SMP system. Note that the attribute value is averaged in synch with the situation or historical collection interval. This data is derived from the CPU Busy attribute in the SMP CPU data set. Chapter 2. Dashboards 7

14 v % Idle: The percentage of idle CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine how efficiently the entire system or each processor of the SMP system is operating. The Idle CPU value must be low if the system load is heavy, and high if the system load is light. If the system load is heavy and the Idle CPU value is high, an I/O problem might exist. If the Idle CPU value is small, or zero, and the User percentage is larger (greater than 30%), the system might be compute-bound or in a loop. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the Idle CPU attribute in the SMP CPU data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the SMP CPU data set. Processor The Processor group widget shows detailed information about the selected CPU. The following KPIs for the group widget are derived from the attributes as described: v ID: The processor ID. Use this attribute to determine the processor ID. In an SMP system with more than one processor, the CPU report shows CPU ID as aggregate on the first row. This means the data row return aggregated CPU statistics. This data is derived from the CPU ID attribute in the SMP CPU data set. v Physical Consumption: The number of physical CPU units consumed by this logical CPU. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Physical Consumption attribute in the SMP CPU data set. v Status: The current status of the processor. CPU Overview The dashboard presents groups widgets of list of machine CPUs, aggregate CPU usage and usage details of aggregate CPU. Look for specific CPU information by clicking on a CPU listed in the table The following group widgets are available in this dashboard: Aggregate CPU Usage Details The Aggregate CPU Usage Details group widget provides detailed information about the CPU utilization on the machine. The following KPIs for the group widget are derived from the attributes as described: v % I/O Wait: The percent of wait I/O CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use Wait I/O to indicate how effectively the system or a processor is using disks. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platform. This data is derived from the Wait I/O attribute in the SMP CPU data set. v % System: Percent of system CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine the percentage of system or per processor CPU time devoted to executing UNIX system kernel code. System CPU time includes time spent executing system calls and performing administrative functions. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the System CPU attribute in the SMP CPU data set. v % User: Percent of user CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine the percentage of system or per processor CPU time devoted to user processes. User CPU time includes time spent executing both user program and library functions. It 8 Monitoring Agent for Unix OS Reference

15 does not include CPU time spent executing system calls. The ratio between user and system CPU time varies, depending on the kinds of programs executing. If user CPU is extremely high and adversely affecting system performance, you might want to determine which user programs are preventing the CPU from functioning at its normal speed. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the User CPU attribute in the SMP CPU data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the SMP CPU data set. Processors The Processors group widget lists the available CPUs on the UNIX machine. The following KPIs for the group widget are derived from the attributes as described: v ID: The processor ID. Use this attribute to determine the processor ID. In an SMP system with more than one processor, the CPU report shows CPU ID as aggregate on the first row. This means the data row return aggregated CPU statistics. This data is derived from the CPU ID attribute in the SMP CPU data set. v Physical Consumption: The number of physical CPU units consumed by this logical CPU. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Physical Consumption attribute in the SMP CPU data set. v Status: The current status of the processor. Top 5 CPUs by Usage The Top 5 CPUs by Usage group widget shows the five CPUs with the highest utilization. The following KPIs for the group widget are derived from the attributes as described: v % Idle Time: The percentage of idle CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine how efficiently the entire system or each processor of the SMP system is operating. The Idle CPU value must be low if the system load is heavy, and high if the system load is light. If the system load is heavy and the Idle CPU value is high, an I/O problem might exist. If the Idle CPU value is small, or zero, and the User percentage is larger (greater than 30%), the system might be compute-bound or in a loop. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the Idle CPU attribute in the SMP CPU data set. v % System Time: Percent of system CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine the percentage of system or per processor CPU time devoted to executing UNIX system kernel code. System CPU time includes time spent executing system calls and performing administrative functions. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the System CPU attribute in the SMP CPU data set. v % User Time: Percent of user CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use this attribute to determine the percentage of system or per processor CPU time devoted to user processes. User CPU time includes time spent executing both user program and library functions. It does not include CPU time spent executing system calls. The ratio between user and system CPU time varies, depending on the kinds of programs executing. If user CPU is extremely high and adversely affecting system performance, you might want to determine which user programs are preventing the CPU from functioning at its normal Chapter 2. Dashboards 9

16 speed. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platforms. This data is derived from the User CPU attribute in the SMP CPU data set. v % Wait I/O Time: The percent of wait I/O CPU time during the sampling period. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use Wait I/O to indicate how effectively the system or a processor is using disks. Note that the attribute value is averaged in synch with the situation or historical collection interval. Available on all platform. This data is derived from the Wait I/O attribute in the SMP CPU data set. v CPU ID: The processor ID. Use this attribute to determine the processor ID. In an SMP system with more than one processor, the CPU report shows CPU ID as aggregate on the first row. This means the data row return aggregated CPU statistics. This data is derived from the CPU ID attribute in the SMP CPU data set. Disk Details The dashboard presents group widgets of selected disk information, detailed disk usage and operations details of a selected disk. The following group widgets are available in this dashboard: Disk The Disk group widget shows detailed information about the selected disk. The following KPIs for the group widget are derived from the attributes as described: v Name: The name of the physical disk which might be partitioned. Valid entries are up to 32 letters or numbers. This data is derived from the Disk Name attribute in the Disk Performance data set. v Parent: The parent device name. Valid entries are up to 96 letters or numbers. Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Parent attribute in the Disk Performance data set. v Type: The type of device. Valid entries are up to 96 letters or numbers. This data is derived from the Type attribute in the Disk Performance data set. v Volume Group Name: The name of the volume group. Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Volume Group Name attribute in the Disk Performance data set. Disk I/O Usage The Disk I/O Usage group widget provides detailed usage information about the selected disk. The following KPIs for the group widget are derived from the attributes as described: v Disk I/O Read(bytes per sec): The number of bytes per second transferred from the disk during read operations over the previous 30-second interval. HP-UX systems do not measure this attribute and a value of -1 will be reported. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Disk Read Bytes Sec attribute in the Disk Performance data set. v Disk I/O Write(bytes per sec): The number of bytes per second transferred to the disk during write operations over the previous 30-second interval. HP-UX systems do not measure this attribute and a value of -1 will be reported. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Disk Write Bytes Sec attribute in the Disk Performance data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Disk Performance data set. 10 Monitoring Agent for Unix OS Reference

17 Disk Operations per Seconds The Disk Operations per Seconds group widget provides detailed read/write operations information about the selected disk. The following KPIs for the group widget are derived from the attributes as described: v Read Operations per sec.: The number of read transfers per second that is valid for all storage device types except an adapter. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Read Transfers per Sec attribute in the Disk Performance data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Disk Performance data set. v Write Operations per sec.: The number of write transfers per second that is valid for all storage device types except an adapter. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Write Transfers per Sec attribute in the Disk Performance data set. Disks Overview The dashboard presents group widgets that list machine disks, aggregate disk operations per second and usage details of aggregate disk. Look for specific disk information by clicking on a disk listed in the table. The following group widgets are available in this dashboard: Aggregate Disk I/O Usage The Aggregate Disk I/O Usage group widget provides aggregate information about the disk I/O utilization on the machine. The following KPIs for the group widget are derived from the attributes as described: v Disk I/O Read(bytes per sec): The sum of the number of bytes per second transferred from the disk during read operations over the previous 30-second interval. v Disk I/O Write(bytes per sec): The sum of the number of bytes per second transferred to the disk during write operations over the previous 30-second interval. v TIMESTAMP: The date and time the agent collects information as set on the monitored system. Aggregate Disk Operations per Seconds The Aggregate Disk Operations per Seconds group widget provides aggregate information about the disk operations on the machine. Disks The following KPIs for the group widget are derived from the attributes as described: v Read Operations per sec.: The sum of the number of bytes per second transferred from the disk during read operations over the previous 30-second interval. v TIMESTAMP: The local time at the agent when the data was collected. v Write Operations per sec.: The sum of the number of bytes per second transferred to the disk during write operations over the previous 30-second interval. The Disks group widget lists the available disks on the UNIX machine. The following KPIs for the group widget are derived from the attributes as described: v Name: The name of the physical disk which might be partitioned. Valid entries are up to 32 letters or numbers. This data is derived from the Disk Name attribute in the Disk Performance data set. v Parent: The parent device name. Valid entries are up to 96 letters or numbers. Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Parent attribute in the Disk Performance data set. Chapter 2. Dashboards 11

18 v Type: The type of device. Valid entries are up to 96 letters or numbers. This data is derived from the Type attribute in the Disk Performance data set. v Volume Group Name: The name of the volume group. Note: the value -1 indicates Not Available and -2 indicates Not Collected. This data is derived from the Volume Group Name attribute in the Disk Performance data set. Events In Monitored Log The dashboard presents group widgets of list events received for that monitored log file The following group widgets are available in this dashboard: Log File Entries The Log Entries group widget shows the events that are collected for the selected log file. The following KPIs for the group widget are derived from the attributes as described: v Event Type: A flag indicating whether the current event is a flood control summary event. This data is derived from the Event Type attribute in the Kux LogfileProfileEvents data set. v Message: The contents of the msg slot from the EIF event. This data is derived from the msg attribute in the Kux LogfileProfileEvents data set. v Occurrence: The number of times this event occurred over the current flood control summary interval. This data is derived from the Occurrence Count attribute in the Kux LogfileProfileEvents data set. v Timestamp: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Kux LogfileProfileEvents data set. Monitored Log The Monitored Logs group widget shows the list of log files monitored by the selected configuration. The following KPIs for the group widget are derived from the attributes as described: v Codepage: The language codepage of the monitored file. This data is derived from the Codepage attribute in the Kux Log File Status data set. v Configuration: The Resource Name of the subnode agent. This data is derived from the Subnode Resource Name attribute in the Kux Log File Status data set. v Current Position: The current position in bytes into the monitored file. Data up to this has been processed, after it has not. Not applicable to pipes. This data is derived from the Current File Position attribute in the Kux Log File Status data set. v File Name: The full path name of the monitored file. The file name will be null if the row represents a file pattern to be matched during the next scan. This data is derived from the File Name attribute in the Kux Log File Status data set. v File Size: The current size of the monitored file. Not applicable to pipes. This data is derived from the Current File Size attribute in the Kux Log File Status data set. v File Status: The current status of this file. This data is derived from the File Status attribute in the Kux Log File Status data set. v File Type: The type of this file (regular file or pipe). This data is derived from the File Type attribute in the Kux Log File Status data set. v Last Modification Time: The time when the monitored file was last written to. Not applicable to pipes. This data is derived from the Last Modification Time attribute in the Kux Log File Status data set. v Matched Records: The number of processed records from this log which matched one of the specified patterns. This data is derived from the Num Records Matched attribute in the Kux Log File Status data set. 12 Monitoring Agent for Unix OS Reference

19 v Processed Records: The number of records processed from this log since agent start (including ones that are not matches/events). This data is derived from the Num Records Processed attribute in the Kux Log File Status data set. File System Detail The dashboard presents groups widgets of selected file system information and detailed file system usage The following group widgets are available in this dashboard: File System The File System group widget shows detailed information about the selected file system. The following KPIs for the group widget are derived from the attributes as described: v Disk: The name of the physical disk partition where the file system is mounted. This is the physical location of the disk. Valid entries are up to 32 letters or numbers. This data is derived from the Name attribute in the Disk data set. v Name: The path name of the directory to which a file system is mounted. This is the virtual name for the directory. This data is derived from the Mount Point U attribute in the Disk data set. v Size (GB): The total size of a file system, expressed in gigabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Size GB Decimal attribute in the Disk data set. v Status: The availability status of the remote file system (NFS). Note: the value 2 indicates Up, 1 indicates Down, 0 indicates Not Available, and -2 indicates Not Collected. This data is derived from the File System Status attribute in the Disk data set. v Type: The filesystem type name, for example jfs and gpfs. Values that include up to eight letters or numbers are valid. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Any query, applied to an agent prior to V , containing this attribute displays a blank in the File System Type column. This data is derived from the File System Type attribute in the Disk data set. v Usage (GB): The amount of disk space currently in use on a file system, expressed in gigabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Space Used GB Decimal attribute in the Disk data set. File System Space Usage The File System Space Usage group widget provides detailed usage information about the selected file system. The following KPIs for the group widget are derived from the attributes as described: v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Disk data set. v Total: The total size of a file system, expressed in megabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Size MB Decimal attribute in the Disk data set. v Used: The amount of disk space currently in use on a file system, expressed in megabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Space Used MB Decimal attribute in the Disk data set. Chapter 2. Dashboards 13

20 File System Usage The File System Usage group widget provides detailed percentage usage information about the selected file system. The following KPIs for the group widget are derived from the attributes as described: v % Avail: The percentage of space available for a given dataset on the entire ZFS space. v % Used: The percentage of space used for a given dataset on the entire ZFS space. This attribute reflects the percentage of disk space which is available to non-superusers. A high value in this column alerts you to critical disk space conditions. This data is derived from the Space Used Percent attribute in the Disk data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Disk data set. File Systems Overview The dashboard presents group widgets that list machine file systems and aggregate file systems usage. Look for specific file system information by clicking on a file system listed in the table. The following group widgets are available in this dashboard: Aggregate File Systems Space Usage The File Systems Space Usage group widget provides aggregate information abuot file systems utilization on the machine. The following KPIs for the group widget are derived from the attributes as described: v TIMESTAMP: The date and time the agent collects information as set on the monitored system. v Total: The total size of a file system, expressed in megabytes. v Used: The amount of disk space currently in use on a file system, expressed in megabytes. Aggregate File Systems Usage The File Systems Usage group widget provides aggregate usage information about the file systems on the UNIX machine. The following KPIs for the group widget are derived from the attributes as described: v % Avail: The percent of disk space available. v % Used: The percent of disk space used. v TIMESTAMP: The date and time the agent collects information as set on the monitored system. File Systems The File Systems group widget shows the list of available file systems on the UNIX machine. The following KPIs for the group widget are derived from the attributes as described: v Disk: The name of the physical disk partition where the file system is mounted. This is the physical location of the disk. Valid entries are up to 32 letters or numbers. This data is derived from the Name attribute in the Disk data set. v Name: The path name of the directory to which a file system is mounted. This is the virtual name for the directory. This data is derived from the Mount Point U attribute in the Disk data set. v Size (GB): The total size of a file system, expressed in gigabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Size GB Decimal attribute in the Disk data set. 14 Monitoring Agent for Unix OS Reference

21 v Status: The availability status of the remote file system (NFS). Note: the value 2 indicates Up, 1 indicates Down, 0 indicates Not Available, and -2 indicates Not Collected. This data is derived from the File System Status attribute in the Disk data set. v Type: The filesystem type name, for example jfs and gpfs. Values that include up to eight letters or numbers are valid. Note: the value -1 indicates Not Available and -2 indicates Not Collected. Any query, applied to an agent prior to V , containing this attribute displays a blank in the File System Type column. This data is derived from the File System Type attribute in the Disk data set. v Usage (GB): The amount of disk space currently in use on a file system, expressed in gigabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Space Used GB Decimal attribute in the Disk data set. Memory The dashboard presents group widgets of the memory utilization, proving information on real memory, virtual memory, swap memory and paging information. The following group widgets are available in this dashboard: Paging The Paging group widget provides detailed information about the memory paging activity. The following KPIs for the group widget are derived from the attributes as described: v Page-in per sec.: The number of pages per second that are paged-in from disk to system memory averaged over the previous 30-second interval. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Page Ins attribute in the Unix Memory data set. v Page-out per sec.: The number of pages per second paged-out from system memory to disk averaged over the previous 30-second interval. A page-out might include multiple pages and indicates the I/O rate on the paging file. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Page Outs attribute in the Unix Memory data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Unix Memory data set. Real Memory Usage The Real Memory Usage group widget provides detailed information about real memory utilization. The following KPIs for the group widget are derived from the attributes as described: v Computational: The number of computational 4K pages resident in memory (AIX only). v Non computational: The number of non-computational 4K pages resident in memory (AIX only). v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Unix Memory data set. v Total: The total number of megabytes of physical memory on a monitored system. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Total Real Mem MB attribute in the Unix Memory data set. Chapter 2. Dashboards 15

22 v Used: The amount of physical memory, in megabytes, currently used on the system. The amount of real memory in use by user programs and the system. It is not unusual for the amount of in use memory to be very high, because the system uses available real memory for caching of system information. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Used Real Mem MB attribute in the Unix Memory data set. Swap Memory Usage The Swap Memory Usage group widget provides detailed information about swap memory utilization. The following KPIs for the group widget are derived from the attributes as described: v Free: The number of megabytes of secondary storage available to host virtual memory. This is any part of memory available for additional paging (pseudo-swap) that is free is also included. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Avail Swap Space MB attribute in the Unix Memory data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Unix Memory data set. v Total: The total number of megabytes of secondary storage dedicated to hosting virtual memory. This is any part of memory available for the system to use for additional paging (pseudo-swap) is also included. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Total Swap Space MB attribute in the Unix Memory data set. v Used: The number of megabytes of secondary storage currently hosting virtual memory. This is any part of memory used for additional paging (pseudo-swap) is also included. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Used Swap Space MB attribute in the Unix Memory data set. Virtual Memory Usage The Virtual Memory Usage group widget provides detailed information about virtual memory utilization. The following KPIs for the group widget are derived from the attributes as described: v Free: The total number of megabytes available for paging that is not currently being used. This includes primary memory and secondary storage. This includes primary memory and secondary storage. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Avail Virtual Storage MB attribute in the Unix Memory data set. v TIMESTAMP: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the Unix Memory data set. v Total: The total number of megabytes of storage available for hosting virtual memory. This includes primary memory and secondary backing store. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates Value_Exceeds_Maximum, and indicates Value_Exceeds_Minimum. This data is derived from the Total Virtual Storage MB attribute in the Unix Memory data set. v Used: The number of megabytes of virtual memory currently in use by the system. This includes primary memory and secondary backing store. Note: the value -1 indicates Not Available, -2 indicates Not Collected, indicates 16 Monitoring Agent for Unix OS Reference