Monitoring Agent for Linux OS

+

Search Tips   |   Advanced Search

1. Overview of the Monitoring Agent for Linux
   1. Features of the Monitoring Agent for Linux OS
   2. New in this release
   3. Monitoring Agent for Linux OS components
   4. User interface options
2. Requirements for the monitoring agent
   1. Naming instances
   2. Running as a non-Administrator user
   3. Using Agent Management Services
   4. Filtering capabilities on the names of processes
3. Workspaces reference
   1. About workspaces
   2. More information about workspaces
   3. Predefined workspaces
   4. Agent Management Services workspace
   5. Agents' Management Log workspace
   6. All Files workspace
   7. Capacity Usage Information workspace
   8. CPU Averages workspace
   9. Disk I/O Extended Rate workspace
   10. Disk I/O Rate workspace
   11. Disk Usage workspace
   12. File Information workspace
   13. Historical Summarized Availability workspace
   14. Historical Summarized Availability Daily workspace
   15. Historical Summarized Availability Hourly workspace
   16. Historical Summarized Availability Weekly workspace
   17. Historical Summarized Capacity workspace
   18. Historical Summarized Capacity Daily workspace
   19. Historical Summarized Capacity Hourly workspace
   20. Historical Summarized Capacity Weekly workspace
   21. Historical Summarized Performance workspace
   22. Historical Summarized Performance Daily workspace
   23. Historical Summarized Performance Hourly workspace
   24. Historical Summarized Performance Weekly workspace
   25. Linux workspace
   26. Network workspace
   27. NFS Statistics workspace
   28. Process workspace
   29. Process CPU Usage workspace
   30. Process User Information workspace
   31. RPC Statistics workspace
   32. Sockets Information workspace
   33. Specific File Information workspace
   34. System Configuration workspace
   35. System Information workspace
   36. Users Workspace
   37. Virtual Memory Statistics workspace
   38. Virtual Memory Usage Trends workspace
4. Attributes reference
   1. About attributes
   2. More information about attributes
   3. Attribute groups and attributes for the Monitoring Agent for Linux
   4. Agent Availability Management Status Attributes
   5. Agent Active Runtime Status Attributes
   6. Alerts Table Attributes
   7. All Users Attributes
   8. Configuration Information Attributes
   9. CPU Attributes
   10. CPU Attributes (superseded)
   11. CPU Averages Attributes
   12. CPU Averages Attributes (superseded)
   13. CPU Configuration Attributes
   14. Disk Attributes
   15. Disk Attributes (superseded)
   16. Disk IO Attributes
   17. Disk IO Attributes (superseded)
   18. Disk Usage Trends Attributes
   19. Disk Usage Trends Attributes (superseded)
   20. File Comparison Group Attributes
   21. File Information Attributes
   22. File Pattern Group Attributes
   23. I/O Ext Attributes
   24. I/O Ext Attributes (superseded)
   25. IP Address Attributes
   26. Linux Group Attributes
   27. Linux Host Availability Attributes
   28. Linux TCP Statistics Attributes
   29. LPAR Attributes
   30. Machine Information attributes
   31. Network Attributes
   32. Network Attributes (superseded)
   33. NFS Statistics Attributes
   34. NFS Statistics Attributes (superseded)
   35. OS Configuration Attributes
   36. Process Attributes
   37. Process Attributes (superseded)
   38. Process User Info Attributes
   39. Process User Info Attributes (superseded)
   40. RPC Statistics Attributes
   41. RPC Statistics Attributes (superseded)
   42. Sockets Detail Attributes
   43. Sockets Detail Attributes (superseded)
   44. Sockets Status Attributes
   45. Sockets Status Attributes (superseded)
   46. Swap Rate Attributes
   47. Swap Rate Attributes (superseded)
   48. System Statistics Attributes
   49. System Statistics Attributes (superseded)
   50. User Login Attributes
   51. User Login Attributes (superseded)
   52. VM Stats Attributes
   53. VM Stats Attributes (superseded)
   54. Disk capacity planning for historical data
5. Situations reference
   1. About situations
   2. More information about situations
   3. Predefined situations
   4. Linux_AMS_Alert_Critical situation
   5. Linux_BP_AvgCpuBusyPct1h_Critic situation
   6. Linux_BP_CpuBusyPct_Critical situation
   7. Linux_BP_CpuWaitIOPct_Warning situation
   8. Linux_BP_LoadAvg5min_Critical situation
   9. Linux_BP_NetTotalErrPct_Warning situation
   10. Linux_BP_NumberZombies_Warning situation
   11. Linux_BP_ProcHighCpu_Critical situation
   12. Linux_BP_ProcMissing_Critical situation
   13. Linux_BP_SpaceUsedPct_Critical situation
   14. Linux_BP_SpaceUsedPctCustom_Cri situation
   15. Linux_BP_SwapSpaceUsedPct_Criti situation
   16. Linux_Fragmented_File_System situation
   17. Linux_Fragmented_File_System_2 situation
   18. Linux_High_CPU_Overload situation
   19. Linux_High_CPU_Overload_2 situation
   20. Linux_High_CPU_System situation
   21. Linux_High_CPU_System_2 situation
   22. Linux_High_Packet_Collisions situation
   23. Linux_High_Packet_Collisions_2 situation
   24. Linux_High_RPC_Retransmit situation
   25. Linux_High_RPC_Retransmit_2 situation
   26. Linux_High_Zombies situation
   27. Linux_High_Zombies_2 situation
   28. Linux_Low_Pct_Inodes situation
   29. Linux_Low_Pct_Inodes_2 situation
   30. Linux_Low_percent_space situation
   31. Linux_Low_percent_space_2 situation
   32. Linux_Low_Space_Available situation
   33. Linux_Low_Space_Available_2 situation
   34. Linux_Network_Status situation
   35. Linux_Network_Status_2 situation
   36. Linux_NFS_Buffer_High situation
   37. Linux_NFS_Buffer_High_2 situation
   38. Linux_NFS_Getattr_High situation
   39. Linux_NFS_Getattr_High_2 situation
   40. Linux_NFS_rdlink_high situation
   41. Linux_NFS_rdlink_high_2 situation
   42. Linux_NFS_Read_High situation
   43. Linux_NFS_Read_High_2 situation
   44. Linux_NFS_Writes_High situation
   45. Linux_NFS_Writes_High_2 situation
   46. Linux_Packets_Error situation
   47. Linux_Packets_Error_2 situation
   48. Linux_Process_High_Cpu situation
   49. Linux_Process_High_Cpu_2 situation
   50. Linux_Process_High_Instant_CPU situation
   51. Linux_Process_stopped situation
   52. Linux_Process_stopped_2 situation
   53. Linux_RPC_Bad_Calls situation
   54. Linux_RPC_Bad_Calls_2 situation
   55. Linux_System_Thrashing situation
   56. Linux_System_Thrashing_2 situation
6. Take Action commands reference
   1. About Take Action commands
   2. More information about Take Action commands
   3. Predefined Take Action commands
   4. AMS Recycle Agent Instance
   5. AMS Reset Agent Daily Restart Count
   6. AMS Start Agent action
   7. AMS Start Agent Instance action
   8. AMS Stop Agent action
   9. AMS Start Management action
   10. AMS Stop Management action
   11. Sample_kill_Process action
7. Policies reference
   1. About policies
   2. More information about policies
   3. Predefined policies
   4. Tivoli Common Reporting for the monitoring agent
   5. Utilization Details for Single Resource report
   6. Utilization Details for Multiple Resources report
   7. Utilization Comparison for Single Resource report
   8. Utilization Comparison for Multiple Resources report
   9. Utilization Heat Chart for Single Resource report
   10. Memory Utilization for Single Resource report
   11. Memory Utilization for Multiple Resources Comparison report
   12. Top Resources Utilization report
   13. Top Situations by Status report
   14. Enterprise Resources List report
   15. Enterprise Daily Utilization Heat Chart report
   16. Enterprise Summary report
   17. Top Resources by Availability
   18. Top Resources Utilization Summary Heat Chart report
   19. Top Resources by Availability (MTTR/MTBSI)
   20. Resource Availability Comparison
   21. Availability Heat Chart for Single Resource
   22. CPU Utilization Comparison for Multiple Resources
   23. CPU Utilization for Single Resource
   24. Disk Utilization for Single Resource
   25. Disk Utilization Comparison for Multiple Resources
   26. Situations History report
   27. Creating custom queries and reports
8. Troubleshooting
   1. Gathering product information for IBM Software Support
   2. Built-in troubleshooting features
   3. Problem classification
   4. Trace logging
   5. Principal trace log files
   6. Examples: using trace logs
   7. Setting RAS trace parameters
   8. Objective
   9. Background Information
   10. Before you begin
   11. After you finish
   12. Procedure
   13. Problems and workarounds
   14. Installation and configuration troubleshooting
   15. Agent upgrade and restart using non-root
   16. Unique names for monitoring components
   17. Agent troubleshooting
   18. PureApplication Monitoring Portal troubleshooting
   19. Troubleshooting for remote deployment
   20. Situation troubleshooting
   21. General situation problems
   22. Problems with configuration of situations
   23. Support information
   24. Accessing terminology online
   25. Accessing publications online
   26. Ordering publications
   27. Tivoli technical training
   28. Tivoli user groups
9. Upgrading for warehouse summarization
   1. Tables in the warehouse
   2. Effects on summarized attributes
   3. Upgrading your warehouse with limited user permissions
   4. Types of table changes
   5. Table summary
   6. Upgrading your warehouse for primary key and tablespace changes
   7. Affected attribute groups and supporting scripts
   8. Procedures
   9. DB2 warehouse database procedure
   10. Oracle warehouse database procedure
   11. MS SQL warehouse database procedure
10. IBM Tivoli Enterprise Console event mapping
11. Monitoring Agent for Linux OS data collection
12. Discovery Library Adapter for the monitoring agent
    1. About the DLA
    2. More information about DLAs
    3. Linux data model class types represented in CDM
       • Linux class
       • ComputerSystem class
       • IpInterface class
       • IpV4Address class
       • IpV6Address class
       • Fqdn class
       • TMSAgent class

Overview of the Monitoring Agent for Linux

As part of the PureApplication Monitoring Portal for Distributed Systems, the Monitoring Agent for Linux OS offers a central point of management of Linux-based environments

IBM PureApplication Monitoring is the base software for the Monitoring Agent for Linux OS. IBM PureApplication Monitoring provides a way to monitor the availability and performance of all the systems in your enterprise from one or several designated workstations. It also provides useful historical data that you can use to track trends and to troubleshoot system problems.

You can use IBM PureApplication Monitoring to do the following:

• Monitor for alerts on the systems that you are managing by using predefined situations or custom situations.
• Establish your own performance thresholds.
• Trace the causes leading to an alert.
• Gather comprehensive data about system conditions.
• Use policies to perform actions, schedule work, and automate manual tasks.

The PureApplication Monitoring Portal is the interface for IBM PureApplication Monitoring products. By providing a consolidated view of your environment, the PureApplication Monitoring Portal permits you to monitor and resolve performance issues throughout the enterprise.

1.2. Features of the Monitoring Agent for Linux OS

As part of the PureApplication Monitoring Portal, the Monitoring Agent for Linux OS offers a central point of management of Linux-based environments. It provides a comprehensive means for gathering exactly the information you need to detect problems early and to prevent them. Information is standardized across all systems, and you can monitor servers from a single workstation.

The Monitoring Agent for Linux OS is an intelligent, remote monitoring agent that resides on managed resources. It assists you in anticipating trouble and warns systems administrators when critical events take place on their systems. With the Monitoring Agent for Linux OS, systems administrators can set threshold levels and flags as desired to alert them when the system reaches these thresholds.

For PureApplication Monitoring Portal, information is displayed in named workspaces. PureApplication Monitoring Portal refers to this tabular format for information as a table view. Information can also be displayed in the workspace as charts, graphs, or other formats that you can specify.

The Monitoring Agent for Linux OS provides the following benefits:

• Simplifies application and system management by managing applications, platforms, and resources across your environment.
• Helps to increase profits by providing you with real-time access to reliable, up-to-the-minute data that allows you to make faster, better-informed operating decisions.
• Scales and ports to new platforms by supporting a wide variety of platforms.
• Improves system performance by letting you integrate, monitor, and manage your system, network, console, and mission-critical applications. A monitoring agent alerts the PureApplication Monitoring Server when conditions on the system network meet threshold-based conditions. These alerts notify your systems administrator to limit and control database usage. You can view data gathered by the PureApplication Monitoring Server in tables and charts for the status of your distributed database systems.
• Enhances efficiency by monitoring diverse platforms and networks from a single PC screen. Depending on your PureApplication Monitoring Portal configuration, you can collect and monitor data across platforms. Management agents gather and filter status information at the managed resource rather than at the hub, eliminating unnecessary data transmission and sending only data that is relevant to changes in status conditions. The Monitoring Agent for Linux OS helps you monitor and gather the consistent, accurate, and timely information you require to effectively perform your job.

1.3. New in this release

For version 6.2.3 of the Monitoring Agent for Linux OS, the following enhancements have been made:

• Support for self-describing agents.
• Enhanced reporting capabilities, including a redesigned installer for OS Agent reports and new reports for Tivoli Common Reporting.
• A new Tivoli Monitoring capability allows you to perform prerequisite checking for agents before performing an installation. The two mechanisms available are a manually executed stand-alone prerequisite scanner, or a remote prerequisite scanner facility that extends the capabilities of PureApplication System Monitoring Server's remote deployment component. See the PureApplication System Monitoring Server: Installation and Setup Guide and the PureApplication System Monitoring Server: Command Reference for more information.
• Additional filtering capabilities (exploiting regular expressions) on names of processes (full command line). This enhancement is useful for those names that are truncated because of the 768 character limit.
• Capability to be alerted about a space availability shortage in the environment, including disks that are assigned to GPFS (general parallel file systems) file systems. This capability includes the File System Type attribute.
• Linux TCP Statistics attribute group
• LPAR attribute group. This attribute group is only supported for Linux PPC on P5 or greater with the following minumum OS versions: RHEL 5.2 and SLES 10sp2.
• Linux_Process_High_Instant_CPU situation
• Process CPU Usage workspace
• Additions to the support of monitoring file systems of the NFS (network file system) type to monitor file systems on systems where the OS agent is not installed, but that are NFS mounted from systems where the OS agent is present.
  • The following environment variable is introduced to enable or disable NFS monitoring at the agent side:

    KBB_SHOW_NFS=true|false
    

    The default value is false.

  • The following environment variable is introduced to enable a timeout:

    KBB_NFS_TIMEOUT
    

    The default value is 2 seconds. The allowed range is 1-30 seconds.

• A new attribute, File System Status, has been added to the Disk attribute group.
• A new attribute, Steal CPU (Percent), has been added to the CPU attribute group. This attribute is only supported for Linux PPC on P5 or greater with the following minumum OS versions: RHEL 5.2 and SLES 10sp2.
• New attributes, Process Busy CPU (Time), Process Filter, Process Instant Busy CPU (Percent), Process System CPU (Time), Process User CPU (Time), and CPU Seconds added to the Process attribute group.
  • The sampling interval for the Process Instant Busy CPU (Percent) attribute is configured using the KLZ_PROCESS_SAMPLE_SECS environment variable. The default value is 30 seconds. The value 0 specifies that the Instant Busy CPU calculation is disabled.

• New attributes, Memory Cached Percent, Net Memory Used (MB), Net Memory Used (Percent), Total Memory Free (MB) and Total Memory Free (Percent) added to the VM Stats attribute group.
• The Enterprise Summary report was added.
• The LPAR Information view in the System Configuration workspace.
• The following new situations:
  • Linux_BP_AvgCpuBusyPct1h_Critic
  • Linux_BP_CpuBusyPct_Critical
  • Linux_BP_CpuWaitIOPct_Warning
  • Linux_BP_LoadAvg5min_Critical
  • Linux_BP_NetTotalErrPct_Warning
  • Linux_BP_NumberZombies_Warning
  • Linux_BP_ProcHighCpu_Critical
  • Linux_BP_ProcMissing_Critical
  • Linux_BP_SwapSpaceUsedPct_Criti
  • Linux_BP_SpaceUsedPct_Critical
  • Linux_BP_SpaceUsedPctCustom_Cri

  Note: These predefined situations are based on best practices. While they might not prove perfectly suited to every monitoring environment, they offer a useful starting point for many users.

1.4. Monitoring Agent for Linux OS components

After you install the Monitoring Agent for Linux OS (product code "klz" or "lz") as directed in the IBM PureApplication System Monitoring Server Installation and Setup Guide, you have an environment with a client, server, and monitoring agent implementation for IBM PureApplication Monitoring that contains the following components:

• PureApplication Monitoring Portal client with a Java-based user interface for viewing and monitoring your enterprise.
• PureApplication Monitoring Portal Server that is placed between the client and the PureApplication Monitoring Server and enables retrieval, manipulation, and analysis of data from the monitoring agents.
• PureApplication Monitoring Server, which acts as a collection and control point for alerts received from the monitoring agents, and collects their performance and availability data.
• Monitoring Agent for Linux OS, which collects and distributes data to a PureApplication Monitoring Server. This component also embeds the Agent Management Services function.
• Operating system agents and application agents installed on the systems or subsystems you want to monitor. These agents collect and distribute data to the PureApplication Monitoring Server.
• Tivoli Data Warehouse for storing historical data collected from agents in your environment. The data warehouse is located on a DB2, Oracle, or Microsoft SQL database. To collect information to store in this database, you must install the Warehouse Proxy agent. To perform aggregation and pruning functions on the data, install the Warehouse Summarization and Pruning agent.
• Tivoli Enterprise Console event synchronization component for synchronizing the status of situation events that are forwarded to the event server. When the status of an event is updated because of IBM Tivoli Enterprise Console rules or operator actions, the update is sent to the monitoring server, and the updated status is reflected in both the Situation Event Console and the Tivoli Enterprise Console event viewer. For more information, see IBM PureApplication System Monitoring Server Installation and Setup Guide.

1.5. User interface options

Installation of the base software and other integrated applications provides the following interfaces that you can use to work with your resources and data:

PureApplication Monitoring Portal browser client interface

The browser interface is automatically installed with PureApplication Monitoring Portal. To start PureApplication Monitoring Portal in your Internet browser, enter the URL for a specific PureApplication Monitoring Portal browser client installed on your Web server.

PureApplication Monitoring Portal desktop client interface

The desktop interface is a Java-based graphical user interface (GUI) on a Windows or Linux workstation.

IBM Tivoli Enterprise Console

Event management application

Manage Tivoli Enterprise Monitoring Services window

The window for the Manage Tivoli Enterprise Monitoring Services utility is used for configuring the agent and starting Tivoli services not already designated to start automatically.

Requirements for the monitoring agent

To install and configure the Monitoring Agent for Linux, use the procedures in the IBM Tivoli Monitoring Installation and Setup Guide .

2.1. Naming instances

If you have multiple instances of a monitoring agent, you must decide how to name the monitoring agents. This name is intended to uniquely identify that monitoring agent. The agent's default name is composed of three qualifiers:

• Optional instance name
• Machine network host name
• Agent product node type

An agent name truncation problem can occur when the network domain name is included in the network host name portion of the agent name. For example, instead of just the host name myhost1 being used, the resulting host name might be myhost1.acme.north.prod.com. Inclusion of the network domain name causes the agent name in the example above to expand to SERVER1:myhost1.acme.north.prod.com:KXX. This resulting name is 39 characters long. It is truncated to 32 characters resulting in the name SERVER1:myhost1.acme.north.prod.

The agent name truncation is only a problem if there is more than one monitoring agent on the same system. In this case, the agent name truncation can result in collisions between agent products attempting to register by using the same truncated name value. When truncated agent names collide on the same system, this can lead to Tivoli Enterprise Monitoring Server problems with corrupted EIB tables. The agent name collision in the Tivoli Enterprise Monitoring Server might cause a registered name to be associated with the wrong product.

In general, create names that are short but meaningful within your environment. Use the following guidelines:

• Each name must be unique. One name cannot match another monitoring agent name exactly.
• Each name must begin with an alpha character.
• Do not use blanks or special characters, including $, #, and @.
• Each name must be between 2 and 32 characters in length.
• Monitoring agent naming is case-sensitive on all operating systems.

2.2. Running as a non-Administrator user

The Monitoring Agent for Linux OS can be run by a non-Administrator user (a non-root user), however some functionality becomes unavailable. The Machine BIOS information uses the dmidecode executable to extract the relevant information. This Linux provided executable must be run by the Administrator user to extract BIOS information. This attribute group does not report data if the agent is not run by the Administrator user. This information is also used by Tivoli Application Dependency Discovery Manager.

A non-Administrator user can only access the directories that it has permissions to read. Therefore, functionality of the File Information attribute group might be reduced.

For Agent Management Services, data reported in the Agent Active Runtime Status attribute group, for example the PID, the command line, the CPU, and the memory, might also be affected when the non-Administrator user is monitoring agents running as a different non-Administrator user.

Also for Agent Management Services, the watchdog cannot stop or start any agent that it does not have privileges to stop or start. If the OS agent is running as a user other than Administrator but you would still like to use it to stop and start other agents, the sudo facility on UNIX and Linux provides one way of supporting this capability. In the example that follows, the OS agent user is a member of a group called 'itm'. Also, it is assumed that Agent Management Services will not be prompted for a password to perform these operations and that the target agents' user IDs are 'user1' and 'user2':

# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
# Failure to use 'visudo' may result in syntax or file permission errors
# that prevent sudo from running.
#
# See the sudoers man page for the details on how to write a sudoers file.
#

# Host alias specification

# User alias specification

# Cmnd alias specification

Cmnd_Alias AMSAGENTSTART = /opt/PAS/ITMTEST/bin/itmcmd agent -[po] [[\:alnum\:]_]* 
start [[\:alnum\:]][[\:alnum\:]],/opt/PAS/ITMTEST/bin/itmcmd agent start 
[[\:alnum\:]][[\:alnum\:]]

Cmnd_Alias AMSAGENTSTOP = /opt/PAS/ITMTEST/bin/itmcmd agent -[po] [[\:alnum\:]_]* 
stop [[\:alnum\:]][[\:alnum\:]],/opt/PAS/ITMTEST/bin/itmcmd agent stop 
[[\:alnum\:]][[\:alnum\:]]

Cmnd_Alias ITMAMSCMD = AMSAGENTSTART,AMSAGENTSTOP

# Defaults specification

# Runas alias specification

Runas_Alias ITMAGENTIDS = user1,user2

# Same thing without a password %itmusers ALL=( ITMAGENTIDS ) NOPASSWD: ITMAMSCMD

This is just one possible example. The sudo facility has many advanced capabilities including the ability to audit and to alert administrators of usage of the sudo command by unauthorized users. See your operating system's sudo man pages for more information.

In the agentInstanceCommand.sh script, replace calls to 'su' with calls to 'sudo'. For example:

if [  -z "$USR" ]; then 	$START_CMD
else
	# su - $USR -c "$START_CMD"
   sudo -u $USR $START_CMD
fi
...
if [ -z "$USR" ]; then 	$STOP_CMD
else
   # su - $USR -c "$STOP_CMD"
	sudo -u $USR $STOP_CMD	
fi

Ensure that the user1 and user2 users also have write permission to any files to which an application agent needs to write.

2.3. Using Agent Management Services

There are two watchdog monitors that run as part of the Monitoring Agent for Linux. One monitor runs as part of the OS Monitoring Agent process, which is referred to as the Agent Watchdog. The other watchdog monitor runs as a separate process named 'kcawd'. The kcawd process is also called the Agent Management Services Watchdog. This watchdog watches the OS Agent, so as long as its Availability Status is showing 'Running' in the Agents' Runtime Status view of the Agent Management Services workspace. No setup or configuration is required.

The Agent Watchdog monitors agent processes other than the OS Agent. By using the communication facility of the OS Agent, it is able to respond to Tivoli Enterprise Portal Desktop queries and Take Actions performed against these other agent processes. This is the data that is seen in the Agent Management Services workspace. In the Tivoli Enterprise Portal Desktop, the Agent Management Services workspace lists the agents that can be monitored by this watchdog running as part of the OS Agent. These are non-OS agents, so the Monitoring Agent for Linux is not listed in the workspace, except for in the Agents' Management Definitions view. One of the agents listed in the workspace is the Agent Management Services Watchdog. Its purpose is to monitor the OS Agent's availability.

The Agent Management Services Watchdog monitor is responsible for watching just the OS Monitoring Agent and restarting it if it goes down. It is enabled by default and does not need to be configured. It is started automatically when the Monitoring Agent for Linux is started. This watchdog does not have a communication facility, so it cannot report information to the Tivoli Enterprise Portal or respond to Take Actions. It is not an agent per se, but a separate process that always monitors the OS Monitoring Agent.

You can temporarily disable the Agent Management Services Watchdog by using the InstallDir/bin/itmcmd execute lz disarmWatchdog.sh command. This disables the Watchdog process for the OS Monitoring Agent and all Agent Management Services managed agents. If there is local administrative work to be performed, and you do not want the auto-restart of the agents to interfere with it, run the InstallDir/bin/itmcmd execute lz disarmWatchdog.sh command before proceeding. When the work is complete, recycle the OS Monitoring Agent to reenable Agent Management Services, or use the InstallDir/bin/itmcmd execute lz rearmWatchdog.sh command.

If you use the itmcmd interface to stop or start an Agent Management Services managed agent, its watchdog will be disabled if stopping the agent and enabled if starting the agent.

2.4. Filtering capabilities on the names of processes

You can now distinguish process names that are longer than 768 characters, so that situations can be defined on the relevant part of the name. You can also use this enhancement for filtering processes of any length.

To improve filtering on the processes, a Process Filter has been added to the Process attribute group. Its content, a regular expression, is sent to the agent as a filter object and is intended to act only on the Process Command (Unicode) attribute. For example, the agent uses the value provided in the Process Filter attribute to match with the process name, and then fills the Process Command Unicode attribute.

In a IBM PureApplication System Monitoring Portal view, you see only the processes whose names match the specified regular expression. The Process Command (Unicode) column is filled with the matching patterns separated by blanks, as defined in the regular expression. The Process Filter column is filled with the regular expression that matches it.

To use this enhancement, create queries and situations on the Process attribute group containing the Process Filter attribute and define a regular expression in it. More rows and more regular expressions are allowed. Use the query in a workspace view or distribute the situation to the target managed systems.

There are a few predefined regular expressions for the Process Filter attribute when you use it in the query or situation editor:

• Java processes (.*java.*)
• IBM_Java_processes_entry_method_only_(.*java.*(com.ibm.*))
• System Admin installed processes_(/usr.*)

Workspaces reference

This chapter contains an overview of workspaces, references for detailed information about workspaces, and descriptions of the predefined workspaces included in this monitoring agent.

3.1. About workspaces

A workspace is the working area of the PureApplication Monitoring Portal application window. At the left of the workspace is a Navigator that you use to select the workspace you want to see.

As you select items in the Navigator, the workspace presents views pertinent to your selection. Each workspace has at least one view. Every workspace has a set of properties associated with it.

This monitoring agent provides predefined workspaces. You cannot modify or delete the predefined workspaces, but you can create new workspaces by editing them and saving the changes with a different name.

3.2. More information about workspaces

For more information about creating, customizing, and working with workspaces, see the IBM PureApplication System Monitoring Server User's Guide.

3.3. Predefined workspaces

The following list shows the organization of the predefined workspaces provided with IBM Tivoli Monitoring: Linux OS Agent.

This agent also includes the following linked workspaces:

• Historical Summarized Availability
• Historical Summarized Availability Daily
• Historical Summarized Availability Hourly
• Historical Summarized Availability Weekly
• Historical Summarized Capacity
• Historical Summarized Capacity Daily
• Historical Summarized Capacity Hourly
• Historical Summarized Capacity Weekly
• Historical Summarized Performance
• Historical Summarized Performance Daily
• Historical Summarized Performance Hourly
• Historical Summarized Performance Weekly

Some predefined workspaces are not available from the Navigator tree item, but are accessed by selecting the link indicator next to a row of data in a view. Left-clicking a link indicator selects the default workspace associated with that link. Right-clicking a link indicator displays all linked workspaces that can be selected.

The remaining sections of this chapter contain descriptions of each of these predefined workspaces, which are organized alphabetically within the group.

3.3.1. Agent Management Services workspace

The Agent Management Services workspace contains views of data collected by the Agent Management Services component of the Monitoring Agent for Linux.

This workspace includes an Agents' Management Status view, an Agents' Runtime Status view, an Agents' Alerts view, and an Agents' Management Definitions view.

3.3.2. Agents' Management Log workspace

The Agents' Management Log workspace contains a list of monitoring agent log entries filtered on the Agent Management Services component. Use this workspace to see the operations being executed by Agent Management Services.

Log messages generated by the physical watchdog are displayed in the Agents' Management Log workspace view. By using these log messages, you can track OS Agent restarts and availability. The limitations of this function are that the physical watchdog must be running.

Alerts that are seen in the Alerts view in the default workspace are cached for 24 hours, by default. The time can be overridden by changing the environment variable KCA_CACHE_LIMIT found in the lz.ini file. The variable is specified in hours. This functionality is not available to previous versions of the agents.

The workspace includes the following operation messages:

• Agent added to system - CAP file found.
• Agent CAP file initialization completed.
• Agent daily restart count reset.
• Agent exceeded policy defined CPU threshold.
• Agent exceeded policy defined memory threshold.
• Agent exceeded restart tries.
• Agent initial start.
• Agent Management Services watchdog not reliable.
• Agent manual start failed.
• Agent manual stop failed.
• Agent not configured.
• Agent not found.
• Agent now managed.
• Agent now unmanaged.
• Agent recycle command received.
• Agent removed from system - CAP file removed.
• Agent restart disabled - disarm mode active
• Agent restart failed.
• Agent start command received.
• Agent started successfully.
• Agent stop command received.
• Agent stopped abnormally.
• Agent stopped successfully.
• Disarm completed successfully.
• Rearm completed successfully.

This workspace includes an Agents' Management Log view.

3.3.3. All Files workspace

The All Files workspace is reached by right-clicking the File Information navigator item in the IBM PureApplication System Monitoring Portal The views are:

• File Size - Top Ten (bar chart)
• All Files (table view)

The File Size - Top Ten bar chart displays the sizes of the largest files. The All Files table provides file information.

3.3.4. Capacity Usage Information workspace

The Capacity Usage Information workspace reflects the .health. of your system by providing CPU, disk, and swap space usage statistics. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of three views. The views are:

• Disk Usage Averages (table view)
• Disk Space Usage (bar chart)
• Disk Usage Averages (bar chart)

The Disk Usage Averages table provides information on the system's current disk usage. The Disk Space Usage bar chart displays the system's current disk usage. The Disk Usage Averages bar chart displays average disk usage information. With the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.5. CPU Averages workspace

The CPU Averages workspace is reached by right-clicking the Capacity Usage Information navigator item in the IBM PureApplication System Monitoring Portal This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). The workspace is comprised of 3 views. The views are Current Overall CPU Usage bar chart, CPU Averages (Hourly Updates) chart, and CPU Usage Trends table.

3.3.6. Disk I/O Extended Rate workspace

The Disk I/O Extended Rate workspace is reached by right-clicking the System Information navigator item in the IBM PureApplication System Monitoring Portal The Disk I/O Extended Rate workspace provides detailed input/output statistics and "calculations", including the queue length and size in sectors of read and write requests, the rate of those requests, and wait times associated with requests. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of two views. The views are:

• Disk I/O Extended Rate (table view)
• Disk Service Time (bar chart)
• Disk Activity (bar chart)

The Disk I/O Extended Rate table details the input/out data and calculated values associated with disk activity. The Disk Service Time chart displays average services time in minutes. The Disk Activity chart displays read and write sectors in seconds. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

Note: The attributes associated with this workspace are only available for systems with a 2.4 (or higher) kernel.

3.3.7. Disk I/O Rate workspace

The Disk I/O Rate workspace is reached by right-clicking the System Information navigator item in the IBM PureApplication System Monitoring Portal The Disk I/O Rate workspace provides input/output statistics, including the transfer rates, block read rates, and block write rates of your monitored systems. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of two views. The views are:

• Disk I/O Rate (table view)
• Disk I/O Rate (bar chart)

The Disk I/O Rate table includes transfer rates, block read rates, and block write rates for your monitored systems. The Disk I/O Rate chart provides .at a glance. rate details associated with disk reads, writes, and transfers. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

Note: The attributes associated with this workspace are only available for systems with a 2.4 (or higher) kernel.

3.3.8. Disk Usage workspace

The Disk Usage workspace reflects the health of storage space within your monitored systems. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of four views. The views are:

• Space Used Percent (bar chart)
• Inodes Used Percent (bar chart)
• Disk Space (bar chart)
• Disk Usage (table view)

The three charts that comprise this workspace provide .at a glance. percentages of the space used, percentages of the inodes used, and amounts of disk space used/available for each monitored disk. The Disk Usage table captures this information, as well as mount point and file system data, in tabular form. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.9. File Information workspace

The File Information workspace displays file information statistics. The views are:

• File Size - Top Ten (bar chart)
• File Size - Top Ten (table view)

3.3.10. Historical Summarized Availability workspace

The Historical Summarized Availability workspace shows the percentage of time that a managed resource was available during the number of months that you specify in the Time Span dialog. This workspace consists of the following two graphical views:

• Availability (average over months), which shows the percentage of time that managed resources were available, grouped by server
• Process Summary (average over months), which shows the percentage of time per system that each process was used by the server

3.3.11. Historical Summarized Availability Daily workspace

The Historical Summarized Availability Daily workspace shows availability information, a process summary, and a system summary for a managed server by day. This workspace consists of the following three graphical views:

• Availability (daily), which shows the percentage of the day that the server was available, summarized by day
• Process Summary (daily), which shows details such as memory and processor usage for processes that were running on the server, summarized by day
• System Summary (daily), which shows system information for the server, such as the operating system type, name, version, and manufacturer, summarized by day

3.3.12. Historical Summarized Availability Hourly workspace

The Historical Summarized Availability Hourly workspace shows availability information, a process summary, and a system summary for a managed server by hour. This workspace consists of the following three graphical views:

• Availability (hourly), which shows the percentage of the hour that the server was available, summarized by hour
• Process Summary (hourly), which shows details such as memory and processor usage for processes that were running on the server, summarized by hour
• System Summary (hourly), which shows system information for the server, such as the operating system type, name, version, and manufacturer, summarized by hour

3.3.13. Historical Summarized Availability Weekly workspace

The Historical Summarized Availability Weekly workspace shows availability information, a process summary, and a system summary for a managed server by week. This workspace consists of the following three graphical views:

• Availability (weekly), which shows the percentage of system time that the server was available, summarized by week
• Process Summary (weekly), which shows processes that kept the server busy, summarized by week
• System Summary (weekly), which shows system information such as the operating system type, name, version, and manufacturer, summarized by week

3.3.14. Historical Summarized Capacity workspace

The Historical Summarized Capacity workspace shows usage of system resources during the time span that you specify in the Time Span dialog. This workspace consists of the following 5 graphical views:

• Network Interface Activity (average over months), which shows network traffic for the server for all network interfaces on the system during the time span that you specify in the Time Span dialog
• Processor Utilization (average over months), which shows CPU usage, including idle CPU time, for all processors that are associated with the server during the specified time period
• Memory Utilization (average over months), which shows memory used, free memory, and swapped memory use during the specified time period
• Disk Utilization (maximum over months), which shows the maximum percentage of space used on the system's logical disks during the specified time period
• Disk Capacity (minimum over months), which shows information about the remaining number of days until the disk is full based on the current rate of disk usage, and the remaining number of days until the disk is full based on peak rate of disk usage, for all disks that are associated with the server

3.3.15. Historical Summarized Capacity Daily workspace

The Historical Summarized Capacity Daily workspace shows system usage summarized by day. This workspace consists of the following four graphical views:

• Network Interface Activity, which shows network traffic for the server, including packet collision rates, during the specified time period, summarized by day
• Processor Utilization, which shows CPU usage (including an idle, busy, or waiting CPU), for all processors that are associated with the server during the specified time period, summarized by day
• Memory Utilization, which shows memory used, free memory, and swapped memory use during the specified time period, summarized by day
• Disk Utilization, which shows percentage of space used or available on the system's logical disks during the specified time period, summarized by day

3.3.16. Historical Summarized Capacity Hourly workspace

The Historical Summarized Capacity Hourly workspace shows system resources used, summarized by hour. This workspace consists of the following four graphical views:

• Network Interface Activity, which shows network traffic, including collisions, packet transmittal and count transmittal for the server during the specified time period, summarized by hour
• Processor Utilization, which shows average CPU usage (idle, busy, and waiting), for all processors that are associated with the server during the specified time period, summarized by hour
• Memory Utilization, which shows memory used, free memory, and swapped memory use during the specified time period, summarized by hour
• Disk Utilization, which shows percentages of space used and available on all the system's logical disks during the specified time period, summarized by hour

3.3.17. Historical Summarized Capacity Weekly workspace

The Historical Summarized Capacity Weekly workspace shows system resources used, summarized by week. This workspace consists of the following 5 graphical views:

• Network Interface Activity, which shows network traffic for the server during the specified time period, summarized by week
• Processor Utilization, which shows CPU usage, especially idle CPU time, for all processors that are associated with the server during the specified time period, summarized by week
• Maximum Memory Utilization, which shows maximum memory used, free memory, and swapped memory during the specified time period, summarized by week
• Average Memory Utilization, which shows average memory that the server used during the specified time period, summarized by week
• Disk Utilization, which shows the maximum percentage of space used on all the system's logical disks during the specified time period, summarized by week

3.3.18. Historical Summarized Performance workspace

The Historical Summarized Performance workspace shows the average performance of system resources for the time span that you specify in the Time Span dialog. This workspace consists of the following 5 graphical views:

• Network Activity (maximum over months), which shows (in the sample period) percentages of errors and collisions in network traffic for all networks that are associated with the system during the time span that you specify in the Time Span dialog
• System Load (average over months), which shows the system workload during the specified time period
• Disk I/O Traffic (average over months), which shows the average percentage of time that the disk was busy during the specified time period
• Memory Page Faults (average over months), which shows the average rate of page in and page out for the system during the specified time period
• Processor Performance (average over months), which shows the average percentage of usage that users consumed and the average processor waiting time for the server during the specified time period

3.3.19. Historical Summarized Performance Daily workspace

The Historical Summarized Performance Daily workspace shows the performance of system resources, summarized by day. This workspace consists of the following 5 graphical views:

• Network Activity (daily), which shows the average network activity for a server, including transmittals, packet collisions, carrier losses, and so on, summarized by day
• System Load (daily), which shows the system workload during the specified time period, summarized by day
• Disk I/O Traffic (daily), which shows the average percentage of time that the disk was busy during the specified time period, summarized by day
• Memory Page Faults (daily), which shows the average rate of page in and page out for the system during the specified time period, summarized by day
• Processor Performance (daily), which shows the percentage of processor time that users consumed, as well as the waiting time that the CPU spent during the specified time period, summarized by day

3.3.20. Historical Summarized Performance Hourly workspace

The Historical Summarized Performance Hourly workspace shows the performance of system resources, summarized by hour. This workspace consists of the following 5 graphical views:

• Network Activity (hourly), which shows the network activity for a server, including transmittals, packet collisions, carrier losses, and so on, summarized by hour
• System Load (hourly), which shows the system workload during the specified time period, summarized by hour
• Disk I/O Traffic (hourly), which shows the average percentage of time that the disk was busy during the specified time period, summarized by hour
• Memory Page Faults (hourly), which shows the average rate of page in and page out for the system during the specified time period, summarized by hour
• Processor Performance (hourly), which shows the percentage of processor time that users consumed, as well as the waiting time that the CPU spent during the specified time period, summarized by hour

3.3.21. Historical Summarized Performance Weekly workspace

The Historical Summarized Performance Weekly workspace shows the performance of system resources, summarized by week. This workspace consists of the following 5 graphical views:

• Network Activity (weekly), which shows the network activity for a server, including errors and packet collisions, for all networks associated with the server, summarized by week
• System Load (weekly), which shows the system workload during the specified time period, summarized by week
• Memory Page Faults (weekly), which shows the average rate of page in and page out for the system during the specified time period, summarized by week
• Disk I/O Traffic (weekly), which shows the average percentage of time that the disk was busy during the specified time period, summarized by week
• Processor Performance (weekly), which shows the percentage of processor time that users consumed, as well as the waiting time that the CPU spent during the specified time period, summarized by week

3.3.22. Linux workspace

The Linux workspace reflects the health of the system. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of three views. The views are:

• System CPU Usage (bar chart)
• Disk IO Transfers (bar chart)
• System Load Averages (bar chart)

3.3.23. Network workspace

The Network workspace reflects the health of the network components within your monitored systems. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of four views. The views are:

• Network Errors (bar chart)
• Network Activity (bar chart)
• Network Devices (table view)
• IP Addresses (table view)

The Network Errors chart shows the number of input errors, output errors, and collisions for the sampling period. The Network Activity chart shows the number of packets received and transmitted per second. The Network Devices table reflects your network's performance based on its transmission, reception, and collision data. The IP Addresses table shows the IP addresses of the network interface names. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.24. NFS Statistics workspace

The NFS Statistics workspace is reached by right-clicking the Network navigator item in the IBM PureApplication System Monitoring Portal The NFS Statistics workspace provides statistics on the operations involving the Network File System, such as the number and type of calls being made, and the percentages those types of calls make up in relation to total calls. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). The views are:

• Network Errors (bar chart)
• RPC Network Activity (bar chart)
• NFS Statistics (table view)

Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.25. Process workspace

The Process workspace reflects the health of specific processes within your monitored systems. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of three views. The views are:

• Process CPU Percent Usage (bar chart)
• Process + Child CPU Percent Usage (bar chart)
• Process Information Detail (table view)

The Process CPU Percent Usage chart displays the percentage of CPU time spent in kernel mode and spent in user mode by process. The Process + Child CPU Percent Usage chart displays the cumulative percentage of CPU time spent in kernel mode and spent in user mode. The Process Information Detail table lists in tabular form a wide range of process characteristics such as data set size, kernel scheduling priority, the number of pages of memory, and the number of page faults. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.26. Process CPU Usage workspace

The Process CPU Usage workspace reflects the CPU consumption of specific processes within your monitored systems. Use this workspace to check systems performances that could be at risk in case of processes consuming too much CPU. Existing percentages of CPU usage are computed on the lifetime of the processes and are unable to report sudden peaks. The views are:

• Process Instant CPU Percent Usage
• Process CPU Usage Detail

3.3.27. Process User Information workspace

The Process User Information workspace is reached by right-clicking the Process navigator item in the IBM PureApplication System Monitoring Portal The Process User Information workspace identifies process owners of your monitored Linux system and details their usage. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of three views. The views are:

• Process CPU Percent Usage (bar chart)
• Process + Child CPU Percent Usage (bar chart)
• Process User Information (table view)

The Process CPU Percent Usage chart displays the percentage of CPU time spent in kernel mode and spent in user mode by process. The Process + Child CPU Percent Usage chart displays the cumulative percentage of CPU time spent in kernel mode and spent in user mode. The Process User Information table provides in tabular form the names of effective groups, file system groups, real groups, and saved groups for your monitored systems. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.28. RPC Statistics workspace

The RPC Statistics workspace is reached by right-clicking the Network navigator item in the IBM PureApplication System Monitoring Portal The RPC (remote procedure call) workspace provides statistics on the number and type of calls being made to the server and clients, including statistics on the number of calls that are not valid or had to be retransmitted. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). The views are:

• Network Errors (bar chart)
• RPC Network Activity (bar chart)
• RPC Statistics (table view)

Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.29. Sockets Information workspace

The Sockets Information workspace is reached by right-clicking the Network navigator item in the IBM PureApplication System Monitoring Portal The Sockets Information workspace reflects the health of the socket connections within your monitored systems. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of three views. The views are:

• Sockets Used by Protocol (bar chart)
• Network Activity (bar chart)
• Socket Services Information (table view)

The Sockets Used by Protocol chart shows a count of the sockets currently in use and the high water mark for each protocol during the sampling period. The Network Activity chart shows the number of packets received and transmitted per second. The Socket Services Information table provides a detailed perspective of each socket that you are monitoring. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.30. Specific File Information workspace

The Specific File Information workspace can be accessed by right-clicking the link on either the File Information workspace or the All Files workspace. The Specific File Information workspace contains detailed information about a specific file or directory. You can access this information down through the lowest directory structure. This workspace is comprised of two views. The views are:

• File Information (table view)
• Take Action view

3.3.31. System Configuration workspace

The System Configuration workspace is reached by right-clicking the System Information workspace in the IBM PureApplication System Monitoring Portal The System Configuration workspace displays information about CPU usage, the processor's configuration, and operating system level. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). It contains the following views:

• CPU Usage (bar chart)
• Processor Configuration Information (table view)
• OS Version Information (table view)
• LPAR Information (table view)

3.3.32. System Information workspace

The System Information workspace reflects the health of your monitored systems by displaying data associated with system loads, context switching, and process creation. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of the following views:

• CPU Usage (bar chart)
• Paging Rates (bar chart)
• System Load (bar chart)
• Virtual Memory Statistics (bar chart)
• System Statistics (table view)

The CPU Usage bar chart shows the percentage of idle CPU time, system CPU time, user CPU time, user nice CPU time, and steal CPU time of the monitored processor. The System Load chart depicts the load on your monitored system's processor during the previous one, five, and 15 minutes. The paging rates chart displays information about paging in and out as well as swapping in and out trends in seconds. The Virtual Memory Statistics chart depicts the current usage and availability of a variety of memory categories (buffered, cached, shared, and swapped). The System Statistics table lists in tabular form the source data of these charts and gauge. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

The System Configuration workspace is reached by right-clicking the System Information navigator item in the IBM PureApplication System Monitoring Portal

3.3.33. Users Workspace

The Users workspace identifies logged in users. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of three views. The views are:

• Process User Information (table view)
• Total User Logins (needle gauge)
• User Login Information (table view)

The Process User Information table provides in tabular form the names of effective groups, file system groups, real groups, and saved groups for your monitored systems. The Total User Logins gauge displays the number of users logged on to the monitored system during the monitoring period. The User Login Information table lists users, their log in time, and their idle time. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.34. Virtual Memory Statistics workspace

The Virtual Memory Statistics workspace is reached by right-clicking the System Information navigator item in the IBM PureApplication System Monitoring Portal The Virtual Memory Statistics workspace provides a snapshot of your monitored systems memory usage. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). This workspace is comprised of four views. The views are:

• Context Switches Percent Change (needle gauge)
• Context Switches Per Second (needle gauge)
• Virtual Memory Statistics (bar chart)
• Virtual Memory Information (table view)

The Context Switches Percent Change gauge reflects the percentage change in the number of context switches per second. The Context Switches Per Second gauge shows the number of context switches per second. The Virtual Memory Statistics chart depicts the current usage and availability of a variety of memory categories (buffered, cached, shared, and swapped). The Virtual Memory Information table presents the Virtual Memory Usage information in tabular form. Based on the information that this workspace provides, you can recommend changes, set up situations, and verify that your recommended changes improve performance.

3.3.35. Virtual Memory Usage Trends workspace

The Virtual Memory Usage Trends workspace is reached by right-clicking the Capacity Usage Information navigator item in the Tivoli Enterprise Portal. This workspace has a superseded version that displays queries with signed 32-bit maximum value (2,147,483,647) and a version with the same name (minus .superseded.) with queries that support values up to signed 64-bit max (9,223,372,036,854,775,807). The views are:

• Current Virtual Memory Usage (bar chart)
• Virtual Memory Averages (bar chart)
• Swap Space Usage Trends (table view)

The Current Virtual Memory Usage bar chart displays memory usage information. The Virtual Memory Averages bar chart displays virtual memory usage trend information. The Swap Space Usage Trends table provides several types of swap space information.

Attributes reference

This chapter contains an overview of attributes, references for detailed information about attributes, and descriptions of the attributes for each attribute group included in this monitoring agent.

4.1. About attributes

Attributes are the application properties being measured and reported by Monitoring Agent for Linux.

Attributes are organized into groups according to their purpose. The attributes in a group can be used in the following two ways:

• Chart or table views

  Attributes are displayed in chart and table views. The chart and table views use queries to specify which attribute values to request from a monitoring agent. You use the Query editor to create a new query, modify an existing query, or apply filters and set styles to define the content and appearance of a view based on an existing query.

• Situations

  You use attributes to create situations that monitor the state of your operating system, database, or application. A situation describes a condition you want to test. When you start a situation, the PureApplication Monitoring Portal compares the values you have assigned to the situation attributes with the values collected by Monitoring Agent for Linux and registers an event if the condition is met. You are alerted to events by indicator icons that are displayed in the Navigator.

4.2. More information about attributes

For more information about using attributes and attribute groups, see the IBM PureApplication System Monitoring Server User's Guide.

4.3. Attribute groups and attributes for the Monitoring Agent for Linux

This monitoring agent contains the following attribute groups. The table name depends on the maximum table name limits of the target database being used for the Tivoli Data Warehouse. If the maximum name is 30 characters, then any warehouse table name longer than 30 characters is shortened to 30 characters.

• Attribute group name: Config
  • Table name: KHDCONF
  • Warehouse table name: KHDCONF or KHD_CONFIG

• Attribute group name: DB Info
  • Table name: KHDDBINFO
  • Warehouse table name: KHDDBINFO or KHD_DB INFO

• Attribute group name: Last Error Details
  • Table name: KHDLASTERR
  • Warehouse table name: KHDLASTERR or KHD_LAST ERROR DETAILS

• Attribute group name: Load Statistics
  • Table name: KHDLOADST
  • Warehouse table name: KHDLOADST or KHD_LOAD STATISTICS

• Attribute group name: Node List
  • Table name: KHDNODELST
  • Warehouse table name: KHDNODELST or KHD_NODE LIST

• Attribute group name: Registration Address List
  • Table name: KHDRGADLST
  • Warehouse table name: KHDRGADLST or KHD_REGISTRATION ADDRESS LIST

• Attribute group name: RPCSource Statistics
  • Table name: KHDRPCS
  • Warehouse table name: KHDRPCS or KHD_RPCSOURCE STATISTICS

• Attribute group name: Warehouse TEMS List
  • Table name: KHDTEMSLST
  • Warehouse table name: KHDTEMSLST or KHD_WAREHOUSE TEMS LIST

• Attribute group name: Work Queue
  • Table name: KHDWORKQ
  • Warehouse table name: KHDWORKQ or KHD_WORK QUEUE

The remaining sections of this chapter contain descriptions of these attribute groups, which are listed alphabetically. The following information is provided for each attribute group:

Historical group

Whether the attribute group is a historical type that you can roll off to a data warehouse

Attribute descriptions

Description, type, and Warehouse name for each attribute in the attribute group

Some attributes are designated as key attributes. A key attribute is an attribute that is used in warehouse aggregation to identify rows of data that represent the same object.

4.3.1. Agent Availability Management Status Attributes

Use Agent Availability Management Status attributes to view the current management status of an agent relative to Agent Management Services.

Agent Management Status The watched agent management status. The following values are valid: Unmanaged (0), Managed (1), Watchdog (2). A value of 'Managed' means that the agent is under the management of Agent Management Services. A value of 'Unmanaged' means it is known, but not under the management of Agent Management Services.

Agent Name The watched agent name.

Agent Type The watched agent type. The following values are valid: Unknown (0), ITM_Unix (1), Console (2), Windows_Service (3), Discover_ITM (4), Discover_Bin (5), Linux_Service (6), ITM_Windows (7).

Agent Version The VRM information for the agent.

Build Date The build date information for the agent. Superseded by the Build Number attribute.

Build Number The build number information for the agent.

Manager Type The enum defining the manager type. The following values are valid: Unknown (0), Not_Managed (1), Agent_Management Services (2), Watchdog (3), External (4). A value of 'Agent Management Services' means that Agent Management Services is responsible. A value of 'NotManaged' means that the agent is not under availability monitoring by any application. A value of 'Externally' means that some other application besides Agent Management Services is responsible for availability monitoring of the agent, for example Tivoli System Automation.

Operating System The operating system identification. The following values are valid: Win2000 (0), Win2003 (1), Win2008 (2), AIX (3), Linux (4), UNKNOWN (5), NA (-1).

Server Name The origin node of the collecting agent.

Service Name The service name.

Timestamp The date and time the Tivoli Enterprise Monitoring Server samples the data. This information is displayed in the standard 16-character date/time format (CYYMMDDHHMMSSmmm), where:

C	Century (0 for 20th, 1 for 21st)
YY	Year
MM	Month
DD	Day
HH	Hour
MM	Minute
SS	Second
mmm	Millisecond

Use simple text strings as described above. For example, 1101009130500000 expresses October 9, 2010, 1:05:00 pm.

4.3.2. Agent Active Runtime Status Attributes

Use the Agent Active Runtime Status attributes to view the current availability status of an agent: Running, Not present, Unknown, Stopped, Manually Stopped. You can view the frequency at which the agent's availability and runtime properties are queried and also the agent's Daily Restart Count.

Agent Availability Status The watched agent availability status. The following values are valid: Unknown (0), Not_found (1), Stopped (2), Start_Pending (3), Running (4), Manually_Stopped (5), Stop_Pending (6), Not_Configured (7). For agents that have an Availability Status of 'Running', use the attribute group to see runtime properties of the agent such as its Process ID and Thread Count.

Agent Host Name The host name of the agent.

Agent Name The watched agent name.

Agent Type The watched agent type. The following values are valid: Unknown (0), ITM_Unix (1), Console (2), Win_Service (3), Discover_ITM (4), Discover_Bin (5), Linux_Service (6), ITM_Windows (7).

Check Frequency The frequency to check status in seconds.

Command Line The command line.

Daily Restart Count The restarts within a period of a day.

Instance Name The instance name of the running IBM Tivoli Monitoring agent.

IP Address The IP address of the agent.

Last Health Check The last health check timestamp.

Number of Threads The thread count.

Operating System The operating system identification. The following values are valid: Unknown (0), Windows (1), Linux (2).

Page Faults Per Second The total page faults.

Parent Process ID The parent process ID.

Process ID The process ID.

Process Name The process name.

Process System CPU (Percent) The system CPU.

Process User CPU (Percent) The user CPU time.

Resident Size The process resident size.

Server Name The origin node of the collecting agent.

Timestamp The date and time the Tivoli Enterprise Monitoring Server samples the data. This information is displayed in the standard 16-character date/time format (CYYMMDDHHMMSSmmm), where:

C	Century (0 for 20th, 1 for 21st)
YY	Year
MM	Month
DD	Day
HH	Hour
MM	Minute
SS	Second
mmm	Millisecond

Use simple text strings as described above. For example, 1101009130500000 expresses October 9, 2010, 1:05:00 pm.

Total Size (Pages) The total memory size in pages.

User Name The user name of running managed agent.

4.3.3. Alerts Table Attributes

Use the Alerts Table attributes to view exceptional Warning and Critical level events surfaced by Agent Management Services. These events have to do with the operation of Agent Management Services or conditions affecting its ability to manage agents. They include the following:

• Agent stopped abnormally.
• Agent restart failed.
• Agent exceeded restart tries.
• Agent not found.
• Agent exceeded policy defined memory threshold.
• Agent exceeded policy defined CPU threshold.
• Agent manual stop failed.
• Agent removed from system - CAP file removed.

Agent Name The watched agent name.

Agent Status The agent status. The following values are valid: Unknown (0), Not_found (1), Stopped (2), Start_Pending (3), Running (4), Manually_Stopped (5), Stop_Pending (6), Not_Configured (7).

Agent Type The watched agent type. The following values are valid: Unknown (0), ITM_Unix (1), Console (2), Windows_Service (3), Discover_ITM (4), Discover_Bin (5), Linux_Service (6), ITM_Windows (7).

Alert Details The alert message details.

Alert Message The alert message. The following values are valid: Availability_policy_removed (1), Managed_agent_removed_from_system (2), Unmanaged_agent_removed_from_system (3), Agent_abnormally_stopped (4), Agent_exceeded_restart_count (5), Agent_restart_failed (6), Agent_overutilizing_memory (7), Agent_overutilizing_CPU (8), Agent_manual_stop_failed (9), Agent_Management_Services_watchdog_not_reliable (11).

Operating System The operating system identification. The following values are valid: Unknown (0), Windows (1), Linux (2).

Process ID The process ID.

Process Name The process name.

Server Name The origin node of the collecting agent.

Timestamp The date and time the Tivoli Enterprise Monitoring Server samples the data. This information is displayed in the standard 16-character date/time format (CYYMMDDHHMMSSmmm), where:

C	Century (0 for 20th, 1 for 21st)
YY	Year
MM	Month
DD	Day
HH	Hour
MM	Minute
SS	Second
mmm	Millisecond

Use simple text strings as described above. For example, 1101009130500000 expresses October 9, 2010, 1:05:00 pm.

4.3.4. All Users Attributes

The All Users attributes refer to user characteristics such as name, user sessions, and user ID.

Duplicate User Name True if the user name is listed more than once in /etc/passwd. The following values are valid: False and True.

Name The full name of a user.

No Password True if no password is assigned to the user. The following values are valid: Unknown (-1), False (0), and True (1).

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

User ID The numeric ID the system assigned to a user. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

User ID (Superseded) The numeric ID the system assigned to a user. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

User Sessions The number of log in sessions this user currently has established. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

4.3.5. Configuration Information Attributes

Use Configuration Information attributes to monitor agent configuration like Memory Threshold and Operating System.

Agent Name The sub agent name.

Agent Path The fully qualified path to agent.

Agent Type The watched agent type. The following values are valid: Unknown (0), ITM_Unix (1), Console (2), Windows_Service (3), Discover_ITM (4), Discover_Bin (5), Linux_Service (6), ITM_Windows (7).

Check Frequency The frequency to check status in seconds.

Configuration Script The agent configuration script.

% CPU Threshold The maximum CPU allowed.

Dependencies The dependent agents.

Manager Type The enum defining the manager type. The following values are valid: Unknown (0), Not_Managed (1), Agent_Management Services (2), Watchdog (3), External (4).

Maximum Daily Restarts The maximum number of restarts allowed. The clock begins at midnight.

Memory Threshold The maximum memory allowed.

Memory Unit The maximum memory allowed units. The following values are valid: Bytes (0), KB (1), MB (2), GB (3).

Operating System The operating system identification. The following values are valid: Unknown (0), Windows (1), Linux (2).

Operating System Name The operating system name.

Operating System Version The operating system version.

PAS_ID The PAS sub agent ID.

Policy File Timestamp The date and time of CAP file.

Process Name The process name of the managed agent.

Server Name The origin node of the collecting agent.

Service Name The service name.

Startup Script The agent startup script.

Status Script The agent status script.

Stop Script The agent stop script.

Timestamp The date and time the Tivoli Enterprise Monitoring Server samples the data. This information is displayed in the standard 16-character date/time format (CYYMMDDHHMMSSmmm), where:

C	Century (0 for 20th, 1 for 21st)
YY	Year
MM	Month
DD	Day
HH	Hour
MM	Minute
SS	Second
mmm	Millisecond

Use simple text strings as described above. For example, 1101009130500000 expresses October 9, 2010, 1:05:00 pm.

4.3.6. CPU Attributes

The CPU attributes refer to processor characteristics such as idle time, system CPU time, and user CPU time.

Busy CPU (Percent) The percentage of time the CPU was busy. The following values are valid: integers in the range 0 to 100.

CPU ID The processor ID. The following values are valid: integers in the range 0 to 999. Use this attribute to determine the processor ID. In a SMP system with more than one processor, the CPU report will show CPU ID as .aggregate. on the first row. This means the data row return aggregated CPU statistics. For example, the following value is valid: Aggregate=-1.

Idle CPU (Percent) Percentage of idle CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. 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.

I/O Wait (Percent) The percentage of time the CPU was in a wait input/output state. The following values are valid: integers in the range of 0 to 100.

Steal CPU (Percent) The percentage of time spent in involuntary wait by the virtual CPU while the hypervisor is servicing another virtual processor (applies only to Linux on PPC P5 or greater). Note: -1 indicates Not Available and -2 indicates Not Collected.

System CPU (Percent) Percentage of system CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. Use this attribute to determine the percentage of system or per processor CPU time devoted to executing Linux system kernel code. System CPU time includes time spent executing system calls and performing administrative functions.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

User CPU (Percent) Percentage of user CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. 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.

User Nice CPU (Percent) Percentage of user nice CPU time during the sampling period. The following values are valid: integers in the range 0 to 100.

User to System CPU (Percent) Of the total CPU time, the percentage consumed by users. The following values are valid: -10000 to + 10000.

4.3.7. CPU Attributes (superseded)

The CPU attributes refer to processor characteristics such as idle time, system CPU time, and user CPU time. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Busy CPU (Percent) The percentage of time the CPU was busy. The following values are valid: integers. The following values are valid: integers in the range 0 to 100. (Superseded.)

CPU ID The processor ID. The following values are valid: integers in the range 0 to 999. Use this attribute to determine the processor ID. In a SMP system with more than one processor, the CPU report will show CPU ID as .aggregate. on the first row. This means the data row return aggregated CPU statistics. For example, the following value is valid: Aggregate=-1. (Superseded.)

Idle CPU (Percent) Percentage of idle CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. 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. (Superseded.)

I/O Wait (Percent) The percentage of time the CPU was in a wait input/output state. The following values are valid: integers in the range of 0 to 100. (Superseded.)

System CPU (Percent) Percentage of system CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. Use this attribute to determine the percentage of system or per processor CPU time devoted to executing Linux system kernel code. System CPU time includes time spent executing system calls and performing administrative functions. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

User CPU (Percent) Percentage of user CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. 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. (Superseded.)

User Nice CPU (Percent) Percentage of user nice CPU time during the sampling period. The following values are valid: integers in the range 0 to 100. (Superseded.)

User to System CPU (Percent) Of the total CPU time, the percentage consumed by users. The following values are valid: -10000 to + 10000. (Superseded.)

4.3.8. CPU Averages Attributes

The CPU Averages attributes refer to CPU usage, System CPU time, idle CPU time, user CPU time, and user nice CPU time characteristics.

Estimated Days Until CPU Upgrade The number of days until CPU Usage Moving average hits 100% Rate. The following values are valid: integers. Note: -1 indicates Not Available and -2 indicates Not Collected.

Idle CPU Moving Average (Percent) The moving average of the idle CPU time for the system, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

Idle CPU (Percent) The current average of the idle CPU time for the system, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

System CPU Current Average (Percent) The current average of the System CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

System CPU Moving Average (Percent) The moving average of the System CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total CPU Used Current Average (Percent) The current average of CPU usage, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

Total CPU Used Moving Average (Percent) The moving average of CPU usage, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

User CPU Current Average (Percent) The current average of the user CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

User CPU Moving Average (Percent) The moving average of the user CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

User Nice CPU Current Average (Percent) The current average of the user nice CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

User Nice CPU Moving Average (Percent) The moving average of the user nice CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly.

Wait CPU Moving Average (Percent) The moving current average of the wait CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100. This average is calculated hourly.

Wait CPU (Percent) The current average of the wait CPU time, expressed as a percentageage. The following values are valid: integers between 0 and 100. This average is calculated hourly.

4.3.9. CPU Averages Attributes (superseded)

The CPU Averages attributes refer to CPU usage, System CPU time, idle CPU time, user CPU time, and user nice CPU time characteristics. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Estimated Days Until CPU Upgrade The number of days until CPU Usage Moving average hits 100% Rate. The following values are valid: integers. Note: -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Idle CPU Moving Average (Percent) The moving average of the idle CPU time for the system, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

Idle CPU (Percent) The current average of the idle CPU time for the system, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

System CPU Current Average (Percent) The current average of the System CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

System CPU Moving Average (Percent) The moving average of the System CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ. (Superseded.)

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total CPU Used Current Average (Percent) The current average of CPU usage, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

Total CPU Used Moving Average (Percent) The moving average of CPU usage, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

User CPU Current Average (Percent) The current average of the user CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

User CPU Moving Average (Percent) The moving average of the user CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

User Nice CPU Current Average (Percent) The current average of the user nice CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

User Nice CPU Moving Average (Percent) The moving average of the user nice CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100, such as 85 for 85%. This average is calculated hourly. (Superseded.)

Wait CPU Moving Average (Percent) The moving current average of the wait CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100. This average is calculated hourly. (Superseded.)

Wait CPU (Percent) The current average of the wait CPU time, expressed as a percentage. The following values are valid: integers between 0 and 100. This average is calculated hourly. (Superseded.)

4.3.10. CPU Configuration Attributes

The CPU Configuration attributes refer to configuration characteristics such as CPU ID, CPU Family, and Clock Speed.

Model Name The process model name.

Processor Cache Size (KB) The processor cache size (Kb). Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Processor Clock Speed (MHz) The processor clock speed (MHz). Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Processor Family Number The process family number. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Processor ID The processor ID.

Processor Model Number The process model number. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Processor Vendor ID The Processor Vendor ID.

4.3.11. Disk Attributes

The Disk attributes refer to disk characteristics such as inode size, inodes used, mount point, and space available. Only mounted file systems are monitored by this agent.

Disk Free (MB) The amount of free space on a disk, expressed in megabytes. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Disk Free Percent The amount of free space on a disk, expressed as a percentage. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected.

Disk Name The name of the physical disk partition where the file system is mounted. This is the physical location of the disk. The following values are valid: alphanumeric text strings with a maximum length of 32 characters.

Disk Used (MB) The amount of used space on a disk, expressed in megabytes. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Disk Used Percent The amount of used space on a disk, expressed as a percentage. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected.

File System 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.

File System Type The file system type, such as hsfs, nfs, tmpfs, and ufs.

Inodes Free The number of inodes currently available on your file system . Use this attribute to avoid a pending crisis. Corrective action might include freeing up unneeded space or deleting temporary files. If the value for Inodes Free is less than 100, this is a critical condition. Notify your system administrator immediately. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Inodes Free Percent The number of inodes currently available on your file system , expressed as a percentage. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected.

Inodes Used The number of inodes currently allocated to files on the file system . This value equals the Total Inodes value minus the Inodes Free value. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Inodes Used Percent The percentage of inodes currently allocated to files, calculated by dividing the Inodes Used value by the Total Inodes value. The following values are valid: integers between 0 and 100, such as 85 for 85%. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Mount Point The path name of the directory to which a file system is mounted. This is the virtual name for the directory. The following values are valid: up to 256 letters or numbers representing a directory path.

Size (MB) The total size of a file system , expressed in megabytes. For example, 1000 represents one gigabyte. The following values are valid: integers of up to 99999999. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Inodes The number of inodes allocated on a file system . For example, a value of 163817 indicates that the number of inodes allocated is 163,817. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Use this attribute when a file system needs additional or fewer inodes assigned to it. Viewing the current number of inodes assigned helps you determine the number of inodes you need to add or subtract to optimize performance in your system.

4.3.12. Disk Attributes (superseded)

The Disk attributes refer to disk characteristics such as inode size, inodes used, mount point, and space available. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Disk Mount Point The path name of the directory to which a file system is mounted. This is the virtual name for the directory. The following values are valid: up to 32 letters or numbers representing a directory path. (Superseded.)

Disk Name The name of the physical disk partition where the file system is mounted. This is the physical location of the disk. The following values are valid: alphanumeric text strings with a maximum length of 32 characters. (Superseded.)

File System Type The file system type, such as hsfs, nfs, tmpfs, and ufs. The following values are valid: up to eight letters or numbers. (Superseded.)

Inodes Available Percent The percentage of inodes currently available. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Inodes Free The number of inodes currently available on your file system . Use this attribute to avoid a pending crisis. Corrective action might include freeing up unneeded space or deleting temporary files. If the value for Inodes Free is less than 100, this is a critical condition. Notify your system administrator immediately. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Inodes Used The number of inodes currently allocated to files on the file system . This value equals the Total Inodes value minus the Inodes Free value. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Inodes Used Percent The percentage of inodes currently allocated to files, calculated by dividing the Inodes Used value by the Total Inodes value. The following values are valid: integers between 0 and 100, such as 85 for 85%. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Mount Point (Unicode) The path name of the directory to which a file system is mounted. (Superseded.)

Size (MB) The total size of a file system , expressed in megabytes. For example, 1000 represents one gigabyte. The following values are valid: integers of up to 99999999. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Space Available (MB) The amount of unused space currently available to non-superusers on a file system , expressed in megabytes. For example, 40000 represents 40 megabytes. The following values are valid: integers of up to 99999999. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

This disk space does not include any space which is reserved for superuser. A low value in this column, relative to the disk size, alerts you to critical disk space conditions.

If this value is low for one or more file system s, relative to the disk size, you might need to evaluate reconfiguring the file system to distribute the files more evenly across disks.

Space Available Percent The percentage of space available. The following values are valid: integers between 0 and 100, such as 10 for 10%. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Space Used (MB) The amount of disk space currently in use on a file system , expressed in megabytes. For example, 5000 represents 5 gigabytes. The following values are valid: integers of up to 99999999. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Space Used Percent The space currently used on the file system, expressed as a percentage of the sum of used and available space. The Space Used Percent 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. The following values are valid: integers between 0 and 100, such as 80 for 80%. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Inodes The number of inodes allocated on a file system . For example, a value of 163817 indicates that the number of inodes allocated is 163,817. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Use this attribute when a file system needs additional or fewer inodes assigned to it. Viewing the current number of inodes assigned helps you determine the number of inodes you need to add or subtract to optimize performance in your system.

4.3.13. Disk IO Attributes

The Disk IO attributes refer to disk input/output characteristics, including transfer rates, block read rates, and block write rates.

Note: These attributes are only available for systems with a 2.4 (or higher) kernel.

Blocks Reads Per Second Indicates the amount of data read from the drive expressed in a number of blocks per second. A block is of indeterminate size. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Blocks Written Per Second Indicates the amount of data written to the drive expressed in a number of blocks per second. A block is of indeterminate size. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Blocks Read The total number of blocks read. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Blocks Written The total number of blocks written. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Device Major Number Major number of the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

Device Minor Number Distinctive minor number for device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

Device Name Name of the device as is displayed under the /dev directory.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Transfers Per Second Indicates the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Multiple logical requests can be combined into a single I/O request to the device. A transfer is of indeterminate size. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

4.3.14. Disk IO Attributes (superseded)

The Disk IO attributes refer to disk input/output characteristics, including transfer rates, block read rates, and block write rates. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Note: These attributes are only available for systems with a 2.4 (or higher) kernel.

Block Reads Per Second Indicates the amount of data read from the drive expressed in a number of blocks per second. A block is of indeterminate size. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Blocks Written Per Second Indicates the amount of data written to the drive expressed in a number of blocks per second. A block is of indeterminate size. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Blocks Read The total number of blocks read. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Blocks Written The total number of blocks written. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Device Major Number Major number of the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Device Minor Number Distinctive minor number for device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Device Name Name of the device as is displayed under the /dev directory. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Transfers Per Second Indicates the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Multiple logical requests can be combined into a single I/O request to the device. A transfer is of indeterminate size. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

4.3.15. Disk Usage Trends Attributes

The Disk Usage Trends attributes refer to disk usage characteristics, such as high water / low water usage rates and days until the disk is full.

Disk Name The name of the physical disk partition where the file system is mounted. This is the physical location of the disk. The following values are valid: alphanumeric text strings with a maximum length of 32 characters.

Days Until Full Disk Current Rate The number of days until the disk is full based on the current rate of disk usage. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Days Until Full Disk Moving Avg The number of days until the disk is full based on the moving average rate of disk usage. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Days Until Full Disk Low Water Mark The number of days until the disk is full based on the disk usage rate that represents the low water mark. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Days Until Full Disk Peak Rate Days until full disk based on the Peak Rate. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Disk Usage Moving Avg (Bytes/Hr) The bytes/hour of disk usage averaged over all previous samples. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Disk Usage Rate (Bytes/Hr) The bytes/hour of disk usage over the last hour. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

High Water Mark Disk Usage Rate (Bytes/Hr) The bytes/hour rate that represents the highwater mark of disk usage. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

High Water Mark Time Stamp The date and time that the disk usage reaches a highwater mark. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Space Free (MB) The amount of unused space currently available to non-superusers on a file system , expressed in megabytes. For example, 40,000 represents 40 megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

This disk space does not include any space which is reserved for superuser. A low value in this column, relative to the disk size, alerts you to critical disk space conditions.

If this value is low for one or more file system s, relative to the disk size, you might need to evaluate reconfiguring the file system to distribute the files more evenly across disks.

Space Used (MB) The amount of disk space currently in use on a file system , expressed in megabytes. Valid entries For example, 5000 represents 5 gigabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.16. Disk Usage Trends Attributes (superseded)

The Disk Usage Trends attributes refer to disk usage characteristics, such as high water / low water usage rates and days until the disk is full. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Disk Name The name of the physical disk partition where the file system is mounted. This is the physical location of the disk. The following values are valid: alphanumeric text strings with a maximum length of 32 characters. (Superseded.)

Days Until Full Disk Current Rate The number of days until the disk is full based on the current rate of disk usage. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Days Until Full Disk Moving Avg The number of days until the disk is full based on the moving average rate of disk usage. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Days Until Full Disk Low Water Mark The number of days until the disk is full based on the disk usage rate that represents the low water mark. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Days Until Full Disk Peak Rate Days until full disk based on the Peak Rate. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Disk Usage Moving Avg (Bytes/Hr) The bytes/hour of disk usage averaged over all previous samples. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Disk Usage Rate (Bytes/Hr) The bytes/hour of disk usage over the last hour. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

High Water Mark Disk Usage Rate (Bytes/Hr) The bytes/hour rate that represents the highwater mark of disk usage. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Minimum=-2147483648. (Superseded.)

High Water Mark Time Stamp The date and time that the disk usage reaches a highwater mark. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Space Available (MB) The amount of unused space currently available to non-superusers on a file system , expressed in megabytes. For example, 40,000 represents 40 megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

This disk space does not include any space which is reserved for superuser. A low value in this column, relative to the disk size, alerts you to critical disk space conditions.

If this value is low for one or more file system s, relative to the disk size, you might need to evaluate reconfiguring the file system to distribute the files more evenly across disks.

Space Used (MB) The amount of disk space currently in use on a file system , expressed in megabytes. Valid entries For example, 5000 represents 5 gigabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.17. File Comparison Group Attributes

File Comparison Group Attributes refer to File Comparison Group characteristics. This attribute group is not available for historical data collection.

File Compare Option The File compare option is used to specify which type of comparison is used. The following values are valid: Plain (1), Ignore_Whitespace (2), Ignore_Case (3), Ignore_Case_Whitespace (4), and Binary (5). The default is Plain.

File Compare Result The result of the file comparison between File_Name_1 and File_Name_2. The following values are valid: Same (0) and Different (1). Note: -1 indicates Not_Available and -2 indicates Not_Collected.

File Name 1 Fully-qualified file name of one of the files to be compared. Required.

File Name 2 Fully-qualified file name of the other of the files to be compared. Required.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.18. File Information Attributes

The File Information attributes refer to file information characteristics. This attribute group is not available for historical data collection.

Access The access rights of the file expressed as 4-digit octal number.

Attribute Last Change Time The date and time of the last file attributes change.

Checksum Checksum or hash string based on hashing algorithm. The default algorithm is CRC32.

Checksum Algorithm Only used in situations in conjunction with the Checksum attribute to specify the algorithm to be used to calculate the hash string. Note: -1 indicates Not_Applicable. Other possible values are CRC32 (0), MD5 (1), and SHA1 (2), Not_Available (-1). The default is CRC32.

File The name of file or directory. If the file is a symbolic link, the link name is shown in Link_Name attribute.

File Content Changed A numeric indicator that the content of a file has changed. It is equivalent to noting a change in checksum between two samples. The following values are valid: No (0), Yes (1), and Not Available (-1).

File Mode Mode is the string representation of the access rights of the file. This is related to the Access attribute. The access attribute is the octal representation of the access rights of the file. The mode of a file would be rwxr-xr-x if the access was 755.

Group The logical group to which the file belongs.

Last Accessed Time The date and time of the last file access.

Last Changed Time The date and time of the last change to a file.

Link Name The name of the file for which this file is a symbolic link. If this field is blank, the file is not a link.

Links The number of links to a file.

Owner The name of the file owner.

Path The full path containing a particular file or directory.

Size (MB) The size, in MB, of the file. This attribute displays as a floating point with a scale of 3. For example 55.255. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Size (MB) (Superseded) The size, in MB, of the file. This attribute displays as a floating point with a scale of 3. For example 55.255.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Type The type of file. Possible values are:

• Dir (= directory)
• DirLink (=directory link)
• File (= file)
• FileLink (=file link)
• Sock (= socket)
• Link (= link)
• Spec (= special file)
• Unknown (=unknown)

4.3.19. File Pattern Group Attributes

The File Pattern Group attributes refer to file pattern group characteristics. This attribute group is not available for historical data collection.

File Name Fully qualified file name which will be searched for lines matching a pattern.

Match Count The number of matches for the specified pattern in the specified file. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Match Option Options that affect how the search is performed. The following values are valid: Normal (1), Ignore_Case (2), Inverse_Search (3), and Match_Whole_Words (4).

Match Pattern The grep regular expression used to search for matching lines in File Name.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.20. I/O Ext Attributes

The I/O Ext attributes refer to a wide variety of disk input/output characteristics, including read request rates, write request rates, and service time measures.

Note: These attributes are only available for systems with a 2.4 (or higher) kernel.

Average Request Queue Length The average queue length of the requests that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Average Request Size (Sectors) The average size (in sectors) of the requests that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Average Service time (ms) The average service time (in milliseconds) for I/O requests that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Average Wait Time (ms) The average time (in milliseconds) for I/O requests issued to the device to be served. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Bytes Transferred Per Second The number of bytes transferred per second. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Device Name Name of the device as is displayed under the /dev directory. The following values are valid: alphanumeric text strings with a maximum length of 64 characters.

Disk Read Percent The percentage of time spent in read operations.

Disk Write Percent The percentage of time spent in write operations.

Percent CPU Time Used Percentage of CPU time during which I/O requests were issued to the device. Saturation occurs at 100%.

Read Bytes Per Second The number of bytes read from the device per second. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Read Requests Per Second The number of read requests that were issued, per second, to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Read Requests Merged Per Second The number of read requests merged, per second, that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Read Sectors Per Second The number of sectors read, per second, from the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Write Bytes Per Second The number of bytes written to the device per second. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Write Requests Per Second The number of write requests that were issued, per second, to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Write Requests Merged Per Second The number of write requests merged that were issued, per second, to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Write Sectors Per Second The number of sectors written to the device, per second. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

4.3.21. I/O Ext Attributes (superseded)

The I/O Ext attributes refer to a wide variety of disk input/output characteristics, including read request rates, write request rates, and service time measures. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Note: These attributes are only available for systems with a 2.4 (or higher) kernel.

Average Request Queue Length The average queue length of the requests that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Average Request Size (Sectors) The average size (in sectors) of the requests that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Average Service time (ms) The average service time (in milliseconds) for I/O requests that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Average Wait Time (ms) The average time (in milliseconds) for I/O requests issued to the device to be served. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Bytes Transferred Per Second The number of bytes transferred per second. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Device Name Name of the device as is displayed under the /dev directory. The following values are valid: alphanumeric text strings with a maximum length of 64 characters. (Superseded.)

Disk Read Percent The percentage of time spent in read operations. (Superseded.)

Disk Write Percent The percentage of time spent in write operations. (Superseded.)

Percent CPU Time Used Percentage of CPU time during which I/O requests were issued to the device. Saturation occurs at 100%. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Read Bytes Per Second The number of bytes read from the device per second. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Read Requests Per Second The number of read requests that were issued, per second, to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Read Requests Merged Per Second The number of read requests merged, per second, that were issued to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Read Sectors Per Second The number of sectors read, per second, from the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Write Bytes Per Second The number of bytes written to the device per second. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Write Requests Per Second The number of write requests that were issued, per second, to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Write Requests Merged Per Second The number of write requests merged that were issued, per second, to the device. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Write Sectors Per Second The number of sectors written to the device, per second. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

4.3.22. IP Address Attributes

The IP Address attributes refer to network characteristics, including IP address and network interface name.

DNS Name The Domain Name Server (DNS) entry associated with the IP network address. The following values are valid: alphanumeric text strings with a maximum length of 384 characters. Note that the value No_DNS_Entry indicates NO_DNS_ENTRY.

IP Address An IP address associated with the network interface. The following values are valid: alphanumeric text strings with a maximum length of 46 characters.

IP Version An indicator as to whether the IP address is version 4 or version 6. The following values are valid:

• IPv4=4
• IPv6=6

Network Interface Name The name of the network interface. The following values are valid: alphanumeric text strings with a maximum length of 32 characters.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.23. Linux Group Attributes

The Linux Group attributes refer to group characteristics.

Duplicate Group Name True if the group name is listed more than once in /etc/group. The following values are valid: False (0) and True (1).

Group ID The ID of this group. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Group ID (Superseded) The ID of this group. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

Group Name The name of the group.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.24. Linux Host Availability Attributes

The Linux Host Availability attributes refer to Linux host availability characteristics. The attributes in this group can only be used in a situation. Historical information is available for the Host Availability table for users interested in trending server response times. However, to enable history collection for this attribute group, a list of monitored (pinged) servers must be specified. The list is specified through an environment variable - "KLZ_PINGHOSTLIST" in the lz.ini file in the PureApplication System Monitoring Server config directory. For example:

KLZ_PINGHOSTLIST='/opt/ibm/itm/config/klzpinghosts'

sample content of klzpinghosts:
#
# hosts pinged for availability from this agent #
server1.domain.com
server2
server4

Host Status Result of the "ping" operation. The following values are valid: Successful (1), Unsuccessful (0), and Error (-1).

Server Response Time Ping operation response time in milliseconds. Note: -1000 indicates Not Available.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Target Host The host name or IP Address of the target of the ping operation. The following values are valid: alphanumeric text strings with a maximum length of 128 characters.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.25. Linux TCP Statistics Attributes

The Linux TCP Statistics attributes include the number of TCP data packets retransmitted per second, the managed system name, and time stamp. The sampling interval is configurable by means of the KLZ_TCPSTAT_SAMPLE_SECS environment variable. The default value is 30 seconds, and the minimum value is 5 seconds.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

TCP Data Packets Retransmitted Per Second The number of TCP data packets retransmitted per second. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.26. LPAR Attributes

The LPAR attributes refer to LPAR characteristics such as entitlement, capacity weight, and shared pool idle time.

Capacity Weight The priority of the LPAR when running in uncapped mode. Used to prioritize partitions competing for CPU resources. If zero is specified, this essentially sets the partition to capped. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Capped Specifies whether the LPAR can exceed or not its entitled capacity. Note: the value 0 indicates false, the value 1 indicates true, the value -1 indicates Not Available, and the value -2 indicates Not Collected.

Entitlement The entitled capacity of the LPAR in terms of units of physical processors. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Entitlement Used (Percent) The percentage of the entitled CPU Units that are in use. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

LPAR ID The identifier of the LPAR. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Max Capacity Used (Percent) The percentage of the max capacity units that are in use. For capped LPARs, this value is equal to Entitlement Used (Percent). Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Number of Virtual CPUs The number of virtual processors of the LPAR. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Physical CPU Units Used The average number of physical CPU units used in the last sampling interval. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and 9223372036854775807 indicates Value Exceeds Maximum.

Shared Specifies whether the LPAR is configured for sharing or not-sharing its free CPU resources with other LPARs. Note: the value 0 indicates false, the value 1 indicates true, the value -1 indicates Not Available, and the value -2 indicates Not Collected.

Shared Pool Idle Time The average number of CPU units left unused in the shared processor pool over the last sampling interval. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and 9223372036854775807 indicates Value Exceeds Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Steal Time (Percent) The total Steal time reported by all the virtual CPUs defined in the LPAR, as percent over the last sampling interval. Note: the value -1 indicates Not Available, and the value -2 indicates Not Collected.

4.3.27. Machine Information attributes

The Machine Information attribute group contains various items required by other Tivoli products. They include system hardware information.

Note: This Monitoring Agent for Linux gathers the following attributes in this group by using the command /usr/sbin/dmidecode:

• BIOS Version
• BIOS Release
• Hardware Brand
• Hardware Model
• Machine Serial Number

The Monitoring Agent for Linux must be running as root in order to execute this command. If not, "Unknown" is returned for the dmidecode metrics. Further, this program is not available for zLinux or pSeries systems. Hardware Brand will report as "IBM." Hardware Model will report as "zSeries," and the remaining metrics will report as "Unknown." Further information on dmidecode is available at the following website:

http://www.nongnu.org/dmidecode

BIOS Release The BIOS vendor release date. Note: the value unknown = UNKNOWN.

BIOS Version The BIOS vendor version. Note: the value unknown = UNKNOWN.

Hardware Brand The brand of hardware on which the agent is running. Note: the value unknown = UNKNOWN.

Hardware Model The specific hardware model underlying the monitored operating system. Note: the value unknown = UNKNOWN.

Machine Serial Number The serial number of the computer. Note: the value unknown = UNKNOWN.

Number of Processors Configured The number of processors configured for this computer. This number excludes secondary processor contexts, but might include virtual processors in some virtual environments. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Number of Processors Online The number of processors online the computer. This number excludes secondary processor contexts, but might include virtual processors in some virtual environments. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Server Host Name The host name for the computer. Note: the value unknown = UNKNOWN.

System Board UUID The Universally Unique Identifier burned in to the system board.

System Name The managed system name. The form should be hostname:agent_code. Note: the value unknown = UNKNOWN.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system.

4.3.28. Network Attributes

The Network attributes refer to network characteristics such as received count, sent count, network interface name, and interface status.

Bytes Received Per Second The number of bytes received per second by the interface. The following values are valid: integers in the range 0 to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Bytes Transmitted Per Second The number of bytes transmitted per second by the interface. The following values are valid: integers in the range 0 to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Carrier Losses The number of carrier losses that occurred in the interface. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Collisions (Percent) Of the total number of packets transmitted in this sample period, the percentage involved in a collision. The following values are valid: integers.

Collisions Per Minute The number of times a packet collided with another packet per minute. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Device Type The device type. The following values are valid: NETROM, ETHER, EETHER, AX25, PRONET, CHAOS, IEEE802_TR, ARCNET, APPLETLK, DLCI, ATM, METRICOM, IEEE1394, SLIP, CSLIP, SLIP6, CSLIP6, RSRVD, ADAPT, ROSE, X25, HWX25, PPP, HDLC, LAPB, DDCMP, RAWHDLC, TUNNEL, TUNNEL6, FRAD, SKIP, LOOPBACK, LOCALTLK, FDDI, BIF, SIT, IPDDP, IPGRE, PIMREG, HIPPI, ASH, ECONET, IRDA, FCPP, FCAL, FCPL, FCFABRIC, IEEE802, IEEE80211, UNKNOWN.

Errors (Percent) Of the total number of packets received and transmitted, the percentage that were in error during this sample period. The following values are valid: integers.

This information can help you determine the data transfer capabilities of various network interfaces, and alleviate bottlenecks by re-routing traffic from devices that appear to be overloaded, to other network interfaces that might be able to handle additional data traffic.

Input Error (Percent) The number of input packet errors as a percentage of the total number of packets received in this sample.

Input Errors The number of packets with errors received on the interface. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Input Errors Per Minute The number of packets with errors received per minute by the interface. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Input FIFO Buffer Overruns The number of input FIFO buffer overruns that occurred during the sampling period. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Input Packets Dropped The number of input packets dropped by the device driver. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Example: www.company.com indicates that the DNS will resolve the name www.company.com to mean the IP address for the interface.

IPv4 Address The Internet Protocol (IP) address of the network interface. A gateway system might have more than one interface, each with a separate address. The following values are valid: Internet protocol addresses in the form a.b.c.d. where a, b, c, and d are integers in the range 0 to 255.

Example: 197.128.55.55 indicates the network interface uses the IP address 197.128.55.55.

Interface Status This attribute indicates if a network interface is currently available. Valid entries for each Network interface are displayed in the following table:

UP	Indicates the interface is in service
DOWN	Indicates the interface is not in service
UP_NOT_RUNNING	Indicates the interface is in service but not running
UNKNOWN	Indicates the interface is in unknown

These values are case-sensitive.

Example:UP means an interface is in service.

MAC Address The MAC address of the Network Interface Card. NOT_AVAILABLE is a valid value. It is typically 6 bytes, but can be up to 14. The value is formatted with a colon between each byte.

Maximum Transmission Unit The maximum packet size (in bytes) for the specified network interface. This is a fixed value. The following values are valid: integers in the range 0 to 99999999. Use this attribute to determine the minimum, maximum or average packet size used by a network interface. This information can help you determine the size used by a network interface.

Network Interface Name Identifies the network interface adapter. The following values are valid: simple text string, alphanumeric comprised of .Interface Name, Unit Number. where:

• The name is a two-character representation of the adapter, based on the hardware, operating system, and installation procedure.
• The unit represents the physical adapter number installed in the system with a typical range 0 to 7.

Output Errors The number of packet transmission errors by the network interface. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Output Error (Percent) The total number of output errors as a percentage of the total number of packets transmitted in this sample.

Output Errors Per Minute The number of packet transmission errors per minute during the monitoring interval. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Output FIFO Buffer Overruns The number of output FIFO buffer overruns that occurred during the sampling period. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Output Packets Dropped The number of output packets dropped by the device driver. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Packet Framing Errors The number of packet framing errors that occurred in the interface. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Packets Received The number of packets received by the interface during the sampling period. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Packets Received Per Second The number of packets received per second by the interface. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Packets Transmitted The number of packets transmitted by the interface during the sampling period. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Packets Transmitted Per Second The number of packets transmitted per second by the interface. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. The value -1 indicates Not_Available.

Received Count (KB) The number of kilobytes received since the network interface was configured. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Example: If a low number of packets are being received, data traffic might need to be re-routed.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Collisions The number of times during the sampling period that a packet transmitted by the network interface collided with another packet. This occurs when another interface on the same local network transmits a packet at nearly the same time. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Use this attribute to determine if a network interface has an unacceptable number of packet collisions. Packet collisions cause the interface to retransmit the packet. With this increased traffic, the likelihood of future collisions increases. This can result in a steady increase of network traffic to critical levels.

Transmitted Count (KB) The number of kilobytes transmitted by an interface since boot time. Valid entry is an integer in the range zero to 9223372036854775807. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Example: A high value might indicate an overloaded interface. A low value might indicate a device that is not being used much, which can carry an additional load, if required.

4.3.29. Network Attributes (superseded)

The Network attributes refer to network characteristics such as received count, sent count, network interface name, and interface status. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Bytes Received Per Second The number of bytes received per second by the interface. The following values are valid: integers in the range 0 to 2147483647. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Bytes Transmitted Per Second The number of bytes transmitted per second by the interface. The following values are valid: integers in the range 0 to 2147483647. For example, the following value is valid: Value_Exceeds_Minimum=-2147483648 and the value Value_Exceeds_Maximum=2147483647. (Superseded.)

Carrier Losses The number of carrier losses that occurred in the interface. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Collisions (Percent) Of the total number of packets transmitted in this sample period, the percentage involved in a collision. The following values are valid: integers. (Superseded.)

Collisions Per Minute The number of times a packet collided with another packet per minute. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Device Type The device type. The following values are valid: NETROM, ETHER, EETHER, AX25, PRONET, CHAOS, IEEE802_TR, ARCNET, APPLETLK, DLCI, ATM, METRICOM, IEEE1394, SLIP, CSLIP, SLIP6, CSLIP6, RSRVD, ADAPT, ROSE, X25, HWX25, PPP, HDLC, LAPB, DDCMP, RAWHDLC, TUNNEL, TUNNEL6, FRAD, SKIP, LOOPBACK, LOCALTLK, FDDI, BIF, SIT, IPDDP, IPGRE, PIMREG, HIPPI, ASH, ECONET, IRDA, FCPP, FCAL, FCPL, FCFABRIC, IEEE802, IEEE80211, UNKNOWN. (Superseded.)

Errors (Percent) Of the total number of packets received and transmitted, the percentage that were in error during this sample period. The following values are valid: integers. (Superseded.)

This information can help you determine the data transfer capabilities of various network interfaces, and alleviate bottlenecks by re-routing traffic from devices that appear to be overloaded, to other network interfaces that might be able to handle additional data traffic.

Input Error (Percent) The number of input packet errors as a percentage of the total number of packets received in this sample. (Superseded.)

Input Errors The number of packets with errors received on the interface. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Input Errors Per Minute The number of packets with errors received per minute by the interface. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Input FIFO Buffer Overruns The number of input FIFO buffer overruns that occurred during the sampling period. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Input Packets Dropped The number of input packets dropped by the device driver. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Example: www.company.com indicates that the DNS will resolve the name www.company.com to mean the IP address for the interface.

IPv4 Address The Internet Protocol (IP) address of the network interface. A gateway system might have more than one interface, each with a separate address. The following values are valid: Internet protocol addresses in the form a.b.c.d. where a, b, c, and d are integers in the range 0 to 255. (Superseded.)

Example: 197.128.55.55 indicates the network interface uses the IP address 197.128.55.55.

Interface Status This attribute indicates if a network interface is currently available. (Superseded.) Valid entries for each Network interface are displayed in the following table:

UP	Indicates the interface is in service
DOWN	Indicates the interface is not in service
UP_NOT_RUNNING	Indicates the interface is in service but not running
UNKNOWN	Indicates the interface is in unknown

These values are case-sensitive.

Example:UP means an interface is in service. (Superseded.)

MAC Address The MAC address of the Network Interface Card. NOT_AVAILABLE is a valid value. It is typically 6 bytes, but can be up to 14. The value is formatted with a colon between each byte. (Superseded.)

Maximum Transmission Unit The maximum packet size (in bytes) for the specified network interface. This is a fixed value. The following values are valid: integers in the range 0 to 99999999. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. Use this attribute to determine the minimum, maximum or average packet size used by a network interface. This information can help you determine the size used by a network interface. (Superseded.)

Network Interface Name Identifies the network interface adapter. (Superseded.) The following values are valid: simple text string, alphanumeric comprised of .Interface Name, Unit Number. where:

• The name is a two-character representation of the adapter, based on the hardware, operating system, and installation procedure.
• The unit represents the physical adapter number installed in the system with a typical range 0 to 7.

Output Errors The number of packet transmission errors by the network interface. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Output Error (Percent) The total number of output errors as a percentage of the total number of packets transmitted in this sample. (Superseded.)

Output Errors Per Minute The number of packet transmission errors per minute during the monitoring interval. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Output FIFO Buffer Overruns The number of output FIFO buffer overruns that occurred during the sampling period. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Output Packets Dropped The number of output packets dropped by the device driver. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Packet Framing Errors The number of packet framing errors that occurred in the interface. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Packets Received The number of packets received by the interface during the sampling period. The following values are valid: integers in the range 0 to 99999999. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Packets Received Per Second The number of packets received per second by the interface. The following values are valid: integers in the range 0 to 2147483647. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Packets Transmitted The number of packets transmitted by the interface during the sampling period. The following values are valid: integers in the range 0 to 99999999. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Packets Transmitted Per Second The number of packets transmitted per second by the interface. The following values are valid: integers in the range 0 to 2147483647. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Received Count (KB) The number of kilobytes received since the network interface was configured. The following values are valid: integers in the range 0 to 2147483647. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Example: If a low number of packets are being received, data traffic might need to be re-routed.

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Collisions The number of times during the sampling period that a packet transmitted by the network interface collided with another packet. This occurs when another interface on the same local network transmits a packet at nearly the same time. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Use this attribute to determine if a network interface has an unacceptable number of packet collisions. Packet collisions cause the interface to retransmit the packet. With this increased traffic, the likelihood of future collisions increases. This can result in a steady increase of network traffic to critical levels.

Transmitted Count (KB) The number of kilobytes transmitted by an interface since boot time. The following values are valid: integers in the range 0 to 2147483647. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Example: A high value might indicate an overloaded interface. A low value might indicate a device that is not being used much, which can carry an additional load, if required.

4.3.30. NFS Statistics Attributes

Use NFS Statistics to monitor characteristics of Network File System (NFS) such as the number of calls, lookups, and operations. This agent currently reports only on NFS version 2 and 3 statistics.

Access Calls The number of access calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Access Calls Percent Of the total number of calls made to the NFS server, the percentage that were access calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Commit Calls The number of file commit calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Commit Calls Percent Of the total number of calls made to the NFS server, the percentage that were file commit calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

File Creates The number of file create calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

File Creates Percent Of the total number of calls made to the NFS server, the percentage that contained file creation operations. The following values are valid: integers in the range of 0 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

File System Info Calls The number of file system information calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

File System Info Calls Percent Of the total number of calls made to the NFS server, the percentage that were calls to obtain information about the file system. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

File System Statistics Calls The number of calls made to the NFS server which requested statistics of the file system. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

File System Statistics Calls Percent Of the total number of calls made to the NFS server, the percentage that involved a request for file system statistics. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Get Attribute Calls The number of calls made to the NFS server which contained a get attribute (getattr) operation. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Get Attribute Calls Percent Of the total number of calls made to the NFS server, the percentage that contained get attribute (getattr) operations. The following values are valid: integers in the range of 0 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Link Calls The total number of link calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Link Calls Percent Of the total number of calls made to the NFS server, the percentage that were link calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Location The location of the origin of the call in the Network File System. The following values are valid: integers. A value of 0 indicates unknown, the value of 1 represents the server, and a value of 2 represents the client. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected.

Lookups The number of lookups made on the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Lookups Percent Of the total number of calls made to the NFS server, the percentage that were lookups. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Make Directory Calls The number of make directory calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Make Directory Calls Percent Of the total number of calls made to the NFS server, the percentage that were make directory calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Make Node Calls The number of make node (mknod) calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Make Node Calls Percent Of the total number of calls made to the NFS server, the percentage that were make node (mknod) calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

NFS Calls The total NFS server or client calls. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

NFS Version The software version associated with the NFS server. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Null Calls The number of calls made to the NFS server from NFS clients which contained no data. The following values are valid: integers in the range of 0 to 100. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Null Calls Percent Of the total number of calls made to the NFS server, the percentage that contained no data. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Path Conf Calls The number of calls made to the NFS server that involved path configuration (pathconf) calls to obtain configuration values for files. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Path Conf Call Percent Of the total number of calls made to the NFS server, the percentage that involved use of the pathconf command to obtain configuration values for files. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Read Calls The number of read calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Read Calls Percent Of the total number of calls made to the NFS server, the percentage that were read calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Read Dir Plus Calls The number of read directory plus (readdirplus) calls made to the NFS server to return the name, the file ID, attributes, and file handle. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Read Dir Plus Calls Percent Of the total number of calls made to the NFS server, the percentage that were read directory plus (readdirplus) calls. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Read Directory Calls The number of read directory calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Read Directory Calls Percent Of the total number of calls made to the NFS server, the percentage that were read directory calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Read Link Calls The number of read link calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Read Link Calls Percent Of the total number of calls made to the NFS server, the percentage that were read link calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Remove Directory Calls The number of remove directory calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Remove Directory Calls Percent Of the total number of calls made to the NFS server, the percentage that were remove directory calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Remove File Calls The number of file removal calls made to the NFS server. The following values are valid: integers. Note: -1 indicates Not_Available, -2 indicates Not_Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum..

Remove File Calls Percent Of the total number of calls made to the NFS server, the percentage that were file removal calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Rename File Calls The number of file rename calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Rename File Calls Percent Of the total number of calls made to the NFS server, the percentage that were file rename calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Root Calls The number of calls made to the NFS server which contained root calls. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Root Calls Percent Of the total number of calls made to the NFS server, the percentage that were root calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Set Attribute Calls The number of calls made to the NFS server which contained a set attribute (setattr) operation. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Set Attribute Calls Percent Of the total number of calls made to the NFS server, the percentage that contained a set attribute (setattr) operation. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Symbolic Link Calls The total number of symbolic link calls. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Symbolic Link Calls Percentage Of the total number of calls made to the NFS server, the percentage that were symbol link calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Write Cache Calls The number of write cache calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Write Cache Calls Percent Of the total number of calls made to the NFS server, the percentage that were write cache calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Writes The number of write calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Writes Percent Of the total number of calls made to the NFS server, the percentage that were write calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

4.3.31. NFS Statistics Attributes (superseded)

Use NFS Statistics to monitor characteristics of Network File System (NFS) such as the number of calls, lookups, and operations. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Access Calls The number of access calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Access Calls Percent Of the total number of calls made to the NFS server, the percentage that were access calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Commit Calls The number of file commit calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Commit Calls Percent Of the total number of calls made to the NFS server, the percentage that were file commit calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

File Creates The number of file create calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

File Creates Percent Of the total number of calls made to the NFS server, the percentage that contained file creation operations. The following values are valid: integers in the range of 0 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

File System Info Calls The number of file system information calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

File System Info Calls Percent Of the total number of calls made to the NFS server, the percentage that were calls to obtain information about the file system. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

File System Statistics Calls The number of calls made to the NFS server which requested statistics of the file system. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

File System Statistics Calls Percent Of the total number of calls made to the NFS server, the percentage that involved a request for file system statistics. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Get Attribute Calls The number of calls made to the NFS server which contained a get attribute (getattr) operation. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Get Attribute Calls Percent Of the total number of calls made to the NFS server, the percentage that contained get attribute (getattr) operations. The following values are valid: integers in the range of 0 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Link Calls The total number of link calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Link Calls Percent Of the total number of calls made to the NFS server, the percentage that were link calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Location The location of the origin of the call in the Network File System. The following values are valid: integers. A value of 0 indicates unknown, the value of 1 represents the server, and a value of 2 represents the client. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected. (Superseded.)

Lookups The number of lookups made on the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Lookups Percent Of the total number of calls made to the NFS server, the percentage that were lookups. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Make Directory Calls The number of make directory calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Make Directory Calls Percent Of the total number of calls made to the NFS server, the percentage that were make directory calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Make Node Calls The number of make node (mknod) calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Make Node Calls Percent Of the total number of calls made to the NFS server, the percentage that were make node (mknod) calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

NFS Calls The total NFS server or client calls. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

NFS Version The software version associated with the NFS server. The following values are valid: integers. A value of 2 represents version 2, 3 represents version 3, 4 represents version 4. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Null Calls The number of calls made to the NFS server from NFS clients which contained no data. The following values are valid: integers in the range of 0 to 100. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Null Calls Percent Of the total number of calls made to the NFS server, the percentage that contained no data. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Path Conf Calls The number of calls made to the NFS server that involved path configuration (pathconf) calls to obtain configuration values for files. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Path Conf Call Percent Of the total number of calls made to the NFS server, the percentage that involved use of the pathconf command to obtain configuration values for files. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Read Calls The number of read calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Read Calls Percent Of the total number of calls made to the NFS server, the percentage that were read calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Read Dir Plus Calls The number of read directory plus (readdirplus) calls made to the NFS server to return the name, the file ID, attributes, and file handle. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Read Dir Plus Calls Percent Of the total number of calls made to the NFS server, the percentage that were read directory plus (readdirplus) calls. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Read Directory Calls The number of read directory calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Read Directory Calls Percent Of the total number of calls made to the NFS server, the percentage that were read directory calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Read Link Calls The number of read link calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Read Link Calls Percent Of the total number of calls made to the NFS server, the percentage that were read link calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Remove Directory Calls The number of remove directory calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Remove Directory Calls Percent Of the total number of calls made to the NFS server, the percentage that were remove directory calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Remove File Calls The number of file removal calls made to the NFS server. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Remove File Calls Percent Of the total number of calls made to the NFS server, the percentage that were file removal calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Rename File Calls The number of file rename calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Rename File Calls Percent Of the total number of calls made to the NFS server, the percentage that were file rename calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Root Calls The number of calls made to the NFS server which contained root calls. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Root Calls Percent Of the total number of calls made to the NFS server, the percentage that were root calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Set Attribute Calls The number of calls made to the NFS server which contained a set attribute (setattr) operation. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Set Attribute Calls Percent Of the total number of calls made to the NFS server, the percentage that contained a set attribute (setattr) operation. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Symbolic Link Calls The total number of symbolic link calls. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Symbolic Link Calls Percentage Of the total number of calls made to the NFS server, the percentage that were symbol link calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Write Cache Calls The number of write cache calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Write Cache Calls Percent Of the total number of calls made to the NFS server, the percentage that were write cache calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Writes The number of write calls made to the NFS server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Writes Percent Of the total number of calls made to the NFS server, the percentage that were write calls. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

4.3.32. OS Configuration Attributes

The OS Configuration attributes refer to configuration characteristics such as OS Name and OS Version.

GCC Version The version of the GNU Compiler with which the kernel was compiled.

OS Name The operating system name.

OS Vendor Information The operating system information.

OS Version The operating system version.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Vendor ID The Processor Vendor ID.

4.3.33. Process Attributes

The Process attributes refer to process characteristics such as data set size, kernel scheduling priority, the number of pages of memory, and the number of page faults. The sampling interval for the Process Instant Busy CPU (Percent) attribute is configured using the KLZ_PROCESS_SAMPLE_SECS environment variable. The default value is 30 seconds. The value 0 specifies that the Instant Busy CPU calculation is disabled.

Command Line The process command line string. The following values are valid: text strings with a maximum length of 768 characters.

CPU Seconds The total CPU seconds spent on the process. The following is a valid value: Value_Exceeds_Maximum=9223372036854775807.

Cumulative Busy CPU (Percent) The summation of user CPU and system CPU for this process's children.

Cumulative Process System CPU (Percent) The percentage of cumulative CPU time spent in kernel mode by this process's children. The following values are valid: integers between 0 and 100.

Cumulative Process User CPU (Percent) The percentage of cumulative CPU time spent in user mode by this process's children. The following values are valid: integers between 0 and 100.

Data Resident Set (Pages) The size of the data set based on the number of pages. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

Data Size (KB) The data size (in kilobytes) of the virtual memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807 Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Data Size (MB) The data size (in megabytes) of the virtual memory. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Executable Size (KB) The executable size (in kilobytes) of the virtual memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Executable Size (MB) The executable size (in megabytes) of the virtual memory. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Kernel Priority The kernel scheduling priority. The following values are valid: integers between -100 - 100 (-100 is the highest). Real-time processes can have priorities that are negative.

Library Size (KB) The library size (in kilobytes) of the virtual memory. This measurement represents all pages, including unused. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Library Size (MB) The library size (in megabytes) of the virtual memory. This measurement represents all pages, including unused. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Nice Value The standard UNIX nice level (-20 represents the highest level). The following values are valid: integers in the range -20 to 19.

Number of Threads The number of threads started for this process. (Valid only on 2.6 kernel and above.) Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Process Busy CPU (Percent) The summation of User CPU Percent and System CPU Percent for this process.

Process Busy CPU (Time) The total CPU time (user + system) spent on the process. The value is expressed in the DDDd HHh MMm SSs format. The following values are valid: Not_Available=0.

Process Command Name The name of the process command. The following values are valid: alphanumeric text strings with a maximum length of 96 characters.

Process Count The count of processes with the same name. The name is selected by using the Command Line (UNICODE), CMDLINEU, attribute. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Process CPU ID The ID of the process CPU. The following values are valid: integers. Note: -1 indicates Not Available.

Process Dirty Pages Pages that have been modified (dirty) in buffer (main memory), but not yet copied to the cache. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

Process Filter A regular expression to be applied to the Command Line attribute. The maximum allowable length is 256 characters. The following values are valid:

• Java_processes_(.*java.*)
• IBM_Java_processes_entry_method_only_(.*java.*(com.ibm.*))
• System_Admin_installed_processes_(/usr.*)

Process Group LeaderID The process group leader ID. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807, Not Available=-1, and Not_Collected=-2.

Process ID The identifier of the process. The following values are valid: integers between 0 and 999. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Process Instant Busy CPU (Percent) The percentage of CPU used by this process in the last sampling interval normalized to account for multiple online processors. For example, the following values are valid: Not Available=-1, and Not_Collected=-2.

Process Parent ID The identifier for the parent process. The following values are valid: integers between 0 and 999. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Process Short Term Avg Busy CPU (Percent) The summation of Proc System CPU Norm and Proc User CPU Norm for this process. CPU percentages are normalized to account for multiple online processors; percentages are normalized to a maximum of 100 percent. This metric is only available through situations and only when the Process name is also specified within the situation predicate. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Process Short Term Avg System CPU (Percent) The short term average of the percentage of CPU time spent in kernel mode by the process. CPU percentages are normalized to account for multiple online processors; percentages are normalized to a maximum of 100 percent. This metric is only available through situations and only when the Process name is also specified within the situation predicate. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Process Short Term Avg User CPU (Percent) The short term average of the percentage of CPU time spent in user mode by the process. CPU percentages are normalized to account for multiple online processors; percentages are normalized to a maximum of 100 percent. This metric is only available through situations and only when the Process name is also specified within the situation predicate. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Process State The state of the process (Sleeping, Disk, Running, Zombie, Trace, Dead, or N/A). The following values are valid: integers between -1 and 5, where:

0 = Sleeping

1 = Disk

2 = Running

3 = Zombie

4 = Trace

5 = Dead

-1 = Not_Available

Process System CPU (Percent) The percentage of CPU time spent in kernel mode by process. The following values are valid: integers between 0 and 100.

Process System CPU (Time) The system CPU time spent executing the process. The value is expressed in the DDDd HHh MMm SSs format. The following values are valid: Not_Available=0.

Process User CPU (Percent) The percentage of CPU time spent in user mode by process. The following values are valid: integers between 0 and 100.

Process User CPU (Time) The user CPU time spent executing the process. The value is expressed in the DDDd HHh MMm SSs format. The following values are valid: Not_Available=0.

Resident Set Size (Pages) The number of pages the process has in real memory. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

Session ID The session ID. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Shared Lib Resident Set (Pages) The number of pages of shared library set (mmap) memory. mmap is a system API that lets you map a file or device into memory. The mapped pages might be shared so that other processes can access them. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

Shared Memory (Pages) The number of pages of shared (mmap) memory. mmap is a system API that lets you map a file or device into memory. The mapped pages might be shared so that other processes can access them. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

Stack Size (KB) The stack size (in kilobytes) of the virtual memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Stack Size (MB) The stack size (in megabytes) of the virtual memory. The following values are valid: integers. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Text Resident Set (Pages) The number of pages of text resident (mmap) memory. mmap is a system API that lets you map a file or device into memory. The mapped pages might be shared so that other processes can access them. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Major Faults The total number of major page faults (including child processes) since the start of the process. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Total Minor Faults The total number of minor page faults (including child processes) since the start of the process. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Total Size (Pages) The number of pages that the process has in real memory. The following values are valid: integers. For example, the following values are valid: Value_Exceeds_Maximum=9223372036854775807 and Not_Collected=-2.

User to System CPU (Percent) Of the total system CPU usage, the percentage that was user CPU usage. For example, 500% means that user CPU usage is 5 times the system CPU usage. The following values are valid: integers between -10,000 and 10,000.

VM Locked Pages (KB) The size (in kilobytes) of locked pages of the virtual memory. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

VM Locked Pages (MB) The size (in megabytes) of locked pages of the virtual memory. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

VM Size (KB) The size (in kilobytes) of the virtual memory. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

VM Size MB Virtual memory size in megabytes. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

4.3.34. Process Attributes (superseded)

The Process attributes refer to process characteristics such as data set size, kernel scheduling priority, the number of pages of memory, and the number of page faults. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Command Line The process command line string. The following values are valid: alphanumeric text strings with a maximum length of 256 characters. (Superseded.)

Command Line (Unicode) The process command line string. The following values are valid: text strings with a maximum length of 512 bytes. This attribute is globalized (Unicode). (Superseded.)

Cumulative Busy CPU (Percent) The summation of user CPU and system CPU for this process and children. (Superseded.)

Cumulative Process System CPU (Percent) The percentage of cumulative CPU time spent in kernel mode by process. The following values are valid: integers between 0 and 100. (Superseded.)

Cumulative Process User CPU (Percent) The percentage of cumulative CPU time spent in user mode by process. The following values are valid: integers between 0 and 100. (Superseded.)

Data Resident Set (Pages) The size of the data set based on the number of pages. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Data Size (KB) The data size (in kilobytes) of the virtual memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Data Size (MB) The data size (in megabytes) of the virtual memory. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Executable Size (KB) The executable size (in kilobytes) of the virtual memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Executable Size (MB) The executable size (in megabytes) of the virtual memory. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Kernel Priority The kernel scheduling priority. The following values are valid: integers between -100 - 100 (-100 is the highest). Real-time processes can have priorities that are negative. (Superseded.)

Library Size (KB) The library size (in kilobytes) of the virtual memory. This measurement represents all pages, including unused. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Library Size (MB) The library size (in megabytes) of the virtual memory. This measurement represents all pages, including unused. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Nice Value The standard Linux nice level (-20 represents the highest level). The following values are valid: integers in the range -20 to 19. (Superseded.)

Number of Threads The number of threads started for this process. (Valid only on 2.6 kernel and above.) Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Parent Process ID The identifier for the parent process. The following values are valid: integers between 0 and 999. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Process Busy CPU (Percent) The summation of User CPU Percent and System CPU Percent for this process. (Superseded.)

Process Command Name The name of the process command. The following values are valid: alphanumeric text strings with a maximum length of 32 characters. (Superseded.)

Process Command Name (Unicode) The name of the process command. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Process Count The count of processes with the same name. The name is selected by using the Command Line (UNICODE), CMDLINEU, attribute. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Process CPU ID The ID of the process CPU. The following values are valid: integers. Note: -1 indicates Not Available. (Superseded.)

Process Dirty Pages Pages that have been modified (dirty) in buffer (main memory), but not yet copied to the cache. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Process ID The identifier of the process. The following values are valid: integers between 0 and 999. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Process Short Term Avg Busy CPU (Percent) The summation of Proc System CPU Norm and Proc User CPU Norm for this process. CPU percentages are normalized to account for multiple online processors; percentages are normalized to a maximum of 100 percent. This metric is only available through situations and only when the Process name is also specified within the situation predicate. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Process Short Term Avg System CPU (Percent) The short term average of the percentage of CPU time spent in kernel mode by the process. CPU percentages are normalized to account for multiple online processors; percentages are normalized to a maximum of 100 percent. This metric is only available through situations and only when the Process name is also specified within the situation predicate. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Process Short Term Avg User CPU (Percent) The short term average of the percentage of CPU time spent in user mode by the process. CPU percentages are normalized to account for multiple online processors; percentages are normalized to a maximum of 100 percent. This metric is only available through situations and only when the Process name is also specified within the situation predicate. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Process State The state of the process (Sleeping, Disk, Running, Zombie, Trace, Dead, or N/A). (Superseded.) The following values are valid: integers between -1 and 5, where:

0 = Sleeping

1 = Disk

2 = Running

3 = Zombie

4 = Trace

5 = Dead

-1 = Not_Available

Process System CPU (Percent) The percentage of CPU time spent in kernel mode by process. The following values are valid: integers between 0 and 100. (Superseded.)

Process User CPU (Percent) The percentage of CPU time spent in user mode by process. The following values are valid: integers between 0 and 100. (Superseded.)

Resident Set Size (Pages) The number of pages the process has in real memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Session ID The session ID. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Shared Lib Resident Set (Pages) The number of pages of shared library set (mmap) memory. mmap is a system API that lets you map a file or device into memory. The mapped pages might be shared so that other processes can access them. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Shared Memory (Pages) The number of pages of shared (mmap) memory. mmap is a system API that lets you map a file or device into memory. The mapped pages might be shared so that other processes can access them. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Stack Size (KB) The stack size (in kilobytes) of the virtual memory. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Stack Size (MB) The stack size (in megabytes) of the virtual memory. The following values are valid: integers. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Text Resident Set (Pages) The number of pages of text resident (mmap) memory. mmap is a system API that lets you map a file or device into memory. The mapped pages might be shared so that other processes can access them. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Major Faults The total number of major page faults (including child processes) since the start of the process. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Total Minor Faults The total number of minor page faults (including child processes) since the start of the process. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Total Size (Pages) The number of pages that the process has in real memory. The following values are valid: integers. (Superseded.) For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

User to System CPU (Percent) Of the total system CPU usage, the percentage that was user CPU usage. For example, 500% means that user CPU usage is 5 times the system CPU usage. The following values are valid: integers between -10,000 and 10,000. (Superseded.)

VM Locked Pages (KB) The size (in kilobytes) of locked pages of the virtual memory. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

VM Locked Pages (MB) The size (in megabytes) of locked pages of the virtual memory. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value -2147483648 indicates Value_Exceeds_Minimum. (Superseded.)

VM Size (KB) The size (in kilobytes) of the virtual memory. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

VM Size MB Virtual memory size in megabytes. This attribute displays as a floating point with a scale of 1. For example 5.2. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

4.3.35. Process User Info Attributes

The Process User Info attributes refer to characteristics associated with effective groups, file system groups, real groups, and saved groups.

Effective Group ID The identifier of the effective group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Effective Group Name The effective group name. The following values are valid: text strings with a maximum length of 64 bytes.

Effective User ID The identifier of the effective user. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Effective User Name The name of the effective user. The following values are valid: text strings with a maximum length of 64 bytes.

File System Group Name The name of the file system group. The following values are valid: text strings with a maximum length of 64 bytes.

File System Group ID The identifier of the file system group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

File System User ID The identifier of the file system user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

File System User Name The name of the file system user. The following values are valid: text strings with a maximum length of 64 bytes.

Process Command Line The Command Line string for the process.

Process Command Name Command name of the process.

Process ID The identifier associated with the process. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Process Parent ID The Parent Process ID. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Process State The state of the process (Sleeping, Disk, Running, Zombie, Trace, Dead, or N/A). The following values are valid: integers between -1 and 5, where:

0 = Sleeping

1 = Disk

2 = Running

3 = Zombie

4 = Trace

5 = Dead

-1 = Not_Available

Real Group ID The identifier of the real group. The following values are valid: simple text string, alphanumeric with a maximum length 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Real Group Name The name of the real group. The following values are valid: simple text string, with a maximum length 64 bytes.

Real User ID The identifier of the real user. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Real User Name The name of the real user. The following values are valid: text strings with a maximum length of 64 bytes.

Saved Group ID The identifier of the saved group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Saved Group Name The name of the saved group. The following values are valid: text strings with a maximum length of 64 bytes.

Saved User ID The identifier of the saved user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Saved User Name The name of the saved user. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode).

Session ID The session ID. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Terminal Device Name of the terminal device that started a process.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

VM Size (MB) Virtual Memory Size in Megabytes. This attribute displays as a floating point with a scale of 1. For example 5.2. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

4.3.36. Process User Info Attributes (superseded)

The Process User Info attributes refer to characteristics associated with effective groups, file system groups, real groups, and saved groups. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Command Line (Unicode) Command Line string of the process. (Superseded.)

Effective Group ID The identifier of the effective group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Effective Group Name The effective group name. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Effective Group Name (Unicode) The effective group name. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Effective User ID The identifier of the effective user. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Effective User Name The name of the effective user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Effective User Name (Unicode) The name of the effective user. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

File System Group Name The name of the file system group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

File System Group Name (Unicode) The name of the file system group. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

File System Group ID The identifier of the file system group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

File System User ID The identifier of the file system user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

File System User Name The name of the file system user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

File System User Name (Unicode) The name of the file system user. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Process Command Name (Unicode) The Process Command name (Unicode). (Superseded.)

Process ID The identifier associated with the process. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Process Parent ID The Parent Process ID. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Process State The state of the process (Sleeping, Disk, Running, Zombie, Trace, Dead, or N/A). (Superseded.) The following values are valid: integers between -1 and 5, where:

0 = Sleeping

1 = Disk

2 = Running

3 = Zombie

4 = Trace

5 = Dead

-1 = Not_Available

Real Group ID The identifier of the real group. The following values are valid: simple text string, alphanumeric with a maximum length 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Real Group Name The name of the real group. The following values are valid: simple text string, alphanumeric with a maximum length 16 characters. (Superseded.)

Real Group Name (Unicode) The name of the real group. The following values are valid: simple text string, with a maximum length 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Real User ID The identifier of the real user. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Real User Name The name of the real user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Real User Name (Unicode) The name of the real user. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Saved Group ID The identifier of the saved group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Saved Group Name The name of the saved group. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Saved Group Name (Unicode) The name of the saved group. The following values are valid: text strings with a maximum length of 64 bytes. (Superseded.)

Saved User ID The identifier of the saved user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Saved User Name The name of the saved user. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Saved User Name (Unicode) The name of the saved user. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Session ID The session ID. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Terminal Device Name of the terminal device that started a process. (Superseded.)

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

VM Size (MB) Virtual Memory Size in Megabytes. This attribute displays as a floating point with a scale of 1. For example 5.2. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

4.3.37. RPC Statistics Attributes

Use RPC Statistics to monitor remote procedure call (RPC) characteristics, such as the number of RPC server calls (including the number of rejected calls), packets that are not valid, and client calls.

RPC Calls Retransmitted The number of client calls that needed to be transmitted again. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

RPC Client Calls The number of calls to the server made by the clients of the server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

RPC Packets with Malformed Header The number of packets that were received at the server with header records that were not properly formatted. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

RPC Server Call Authorization Failures The number of packets that were received at the server with authorizations that were not valid. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

RPC Server Calls Rejected The number of calls made to the server, which were rejected. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

RPC Server Invalid Client Requests The number of packets that were received at the server, which had client requests that were not valid. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

RPC Total Server Calls Received The total number of calls made to the server (both valid and not valid). The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Times Authentication Refreshed The number of times the authentication of a client was refreshed. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.38. RPC Statistics Attributes (superseded)

Use RPC Statistics to monitor remote procedure call (RPC) characteristics, such as the number of RPC server calls (including the number of rejected calls), packets that are not valid, and client calls. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

RPC Calls Retransmitted The number of client calls that needed to be transmitted again. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

RPC Client Calls The number of calls to the server made by the clients of the server. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

RPC Packets with Malformed Header The number of packets that were received at the server with header records that were not properly formatted. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

RPC Server Call Authorization Failures The number of packets that were received at the server with authorizations that were not valid. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

RPC Server Calls Rejected The number of calls made to the server, which were rejected. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

RPC Server Invalid Client Requests The number of packets that were received at the server, which had client requests that were not valid. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

RPC Total Server Calls Received The total number of calls made to the server (both valid and not valid). The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Times Authentication Refreshed The number of times the authentication of a client was refreshed. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.39. Sockets Detail Attributes

The Sockets Detail attributes refer to characteristics associated with socket details, including user ID, local and foreign addresses, socket states, and socket protocols.

Foreign Address The address of the remote end of the socket. Like .netstat. * indicates that the address is unassigned/unavailable. The following values are valid: alphanumeric text strings with a maximum length of 16 characters.

Foreign Port The number of the foreign port. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Local Address The address of the local end of the socket, presented as a dotted ip address. The following values are valid: alphanumeric text strings with a maximum length of 16 characters.

Local Port The local port number. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Local Service Name The local port number translated to service name from /etc/services. The following values are valid: alphanumeric text strings with a maximum length of 64 characters.

Receive Queue (Bytes) The count of bytes not copied by the user program connected to this socket. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Send Queue (Bytes) The count of bytes not acknowledged by the remote host. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Socket Inode The inode used by the socket. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Socket Owner Name The user name associated with the user ID that owns or started the socket connection. The following values are valid: text strings with a maximum length of 64 bytes.

Socket Protocol Indicates the sockets using this protocol. .Total. includes UNIX domain sockets not displayed here. The following values are valid: integers, where:

0 = TCP

1 = UDP

2 = RAW

3 = UNIX

-1 = Not Available

-2 = Not Collected

Socket State The state of the socket. The following values are valid: integers, where

1 = ESTABLISHED

2 = SYN_SENT

3 = SYN_RECV

4 = FIN_WAIT1

5 = FIN_WAIT2

6 = TIME_WAIT

7 = CLOSED

8 = CLOSED_WAIT

9 = LAST_ACK

10 = LISTEN

11 = CLOSING

12 = UNKNOWN

Socket UID The user ID of the owner of the socket. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.40. Sockets Detail Attributes (superseded)

The Sockets Detail attributes refer to characteristics associated with socket details, including user ID, local and foreign addresses, socket states, and socket protocols. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Foreign Address The address of the remote end of the socket. Like .netstat. * indicates that the address is unassigned/unavailable. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Foreign Port The number of the foreign port. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Local Address The address of the local end of the socket, presented as a dotted ip address. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Local Port The local port number. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Local Service Name The local port number translated to service name from /etc/services. The following values are valid: alphanumeric text strings with a maximum length of 64 characters. (Superseded.)

Receive Queue (Bytes) The count of bytes not copied by the user program connected to this socket. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Send Queue (Bytes) The count of bytes not acknowledged by the remote host. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Socket Inode The inode used by the socket. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Socket Owner Name (Unicode) The user name associated with the user ID that owns or started the socket connection. The following values are valid: text strings with a maximum length of 64 bytes. This attribute is globalized (Unicode). (Superseded.)

Socket Protocol Indicates the sockets using this protocol. .Total. includes UNIX domain sockets not displayed here. (Superseded.) The following values are valid: integers, where:

0 = TCP

1 = UDP

2 = RAW

3 = UNIX

-1 = Not Available

-2 = Not Collected

Socket State The state of the socket. (Superseded.) The following values are valid: integers, where

1 = ESTABLISHED

2 = SYN_SENT

3 = SYN_RECV

4 = FIN_WAIT1

5 = FIN_WAIT2

6 = TIME_WAIT

7 = CLOSED

8 = CLOSED_WAIT

9 = LAST_ACK

10 = LISTEN

11 = CLOSING

12 = UNKNOWN

Socket UID The user ID of the owner of the socket. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.41. Sockets Status Attributes

The Sockets Status attributes refer to characteristics associated with the status of the Linux system sockets, including protocol names and high water marks used by protocols.

Highest Sockets Used The high water mark of sockets used by this protocol. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Socket Protocol Indicates the sockets using this protocol. .Total. includes UNIX domain sockets not displayed here. The following values are valid: integers, where:

0 = TCP

1 = UDP

2 = RAW

3 = UNIX

4 = FRAG

-1 = TOTAL

-2 = NOT_AVAILABLE

Sockets in Use Sockets in use by protocol. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.42. Sockets Status Attributes (superseded)

The Sockets Status attributes refer to characteristics associated with the status of the Linux system sockets, including protocol names and high water marks used by protocols. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Highest Sockets Used The high water mark of sockets used by this protocol. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Socket Protocol Indicates the sockets using this protocol. .Total. includes UNIX domain sockets not displayed here. (Superseded.) The following values are valid: integers, where:

0 = TCP

1 = UDP

2 = RAW

3 = UNIX

4 = FRAG

-1 = TOTAL

-2 = NOT_AVAILABLE

Sockets in Use Sockets in use by protocol. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

4.3.43. Swap Rate Attributes

The Swap Rate attributes feature swap space characteristics, including usage rates and days till full data.

Days Until Swap Space Full The predicted number of days till swap space is completely used (moving average). The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

Low Water Mark for Free real memory (KB) The lowest level that Free real memory has reached, expressed in kilobytes. The following values are valid: integers. Note: -1 indicates Not Available and -2 indicates Not Collected. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Minimum Days to Swap Full The minimum number of days till swap space is completely used (peak rate based). The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647.

Peak Swap Space Used (MB) The peak swap space used based on snap shots, expressed in megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Swap Space Used (MB) (Moving Average) The moving average of swap space used, expressed in megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Swap Space Used (bytes per hour) The swap space usage rate, expressed in bytes per hour. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Swap Space (MB) (Moving Average) The moving average of total swap space, expressed in megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

4.3.44. Swap Rate Attributes (superseded)

The Swap Rate attributes feature swap space characteristics, including usage rates and days till full data. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Days Until Swap Space Full The predicted number of days till swap space is completely used (moving average). The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Low Water Mark for Free real memory (KB) The lowest level that Free real memory has reached, expressed in kilobytes. The following values are valid: integers. Note: -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Minimum Days to Swap Full The minimum number of days till swap space is completely used (peak rate based). The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Peak Swap Space Used (MB) The peak swap space used based on snap shots, expressed in megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Swap Space Used (MB) (Moving Average) The moving average of swap space used, expressed in megabytes. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Swap Space Used (bytes per hour) The swap space usage rate, expressed in bytes per hour. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Swap Space (MB) (Moving Average) The moving average of total swap space, expressed in megabytes. The following values are valid: integers. (Superseded.)

4.3.45. System Statistics Attributes

The System Statistics attributes refer to characteristics associated with system performance such as the number of logged in users, the number of processes per second, and system load statistics.

Context Switches Per Second The number of context switches per second. Calculated on a 30 second interval. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Minimum=-9223372036854775808 and the value Value_Exceeds_Maximum=9223372036854775807.

Major Page Faults Per Second Number of major faults per second, these are page faults that directly require the loading of pages from disk. (Kernel 2.6 and greater.) Calculated on a 30 second interval. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Number of Processes in Zombie State Number of processes currently in Zombie State. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Number of User Logins The current number of users logged in. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Page Faults Per Second The total number of page faults per second (major and minor). (Kernel 2.6 and above only.) Calculated on a 30 second interval. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Pages Paged In Per Second The pages paged in per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Pages Paged Out Per Second The pages paged out per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Pages Swapped In The pages swapped in. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Pages Swapped In Per Second The pages swapped in per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Pages Swapped Out The pages swapped out. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Pages Swapped Out Per Second The pages swapped out per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Percent Change Context Switches Per Second The percentage change in the number of context switches per second. The following values are valid: integers in the range -100 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Percent Change Processes Created The percentage change in the number of processes created per second. The following values are valid: integers in the range -100 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected.

Processes Created Per Second The number of processes created per second. Calculated on a 30 second interval. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. For example, the following value is valid: Value_Exceeds_Minimum=-9223372036854775808 and the value Value_Exceeds_Maximum=9223372036854775807.

System Load Last 1 Minute The load on the system for the last minute. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Load Last 5 Minutes The load on the system for the last 5 minutes. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Load Last 15 Minutes The load on the system for the last 15 minutes. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

System Uptime The System Uptime in seconds, however it displays as a time counter on the IBM PureApplication System Monitoring Portal The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Number of Processes The total number of processes. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

Total Pages Paged In The total pages paged in. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Total Pages Paged Out The total pages paged out. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

4.3.46. System Statistics Attributes (superseded)

The System Statistics attributes refer to characteristics associated with system performance such as the number of logged in users, the number of processes per second, and system load statistics. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Context Switches Per Second The number of context switches per second. Calculated on a 30 second interval. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Minimum=-2147483648 and the value Value_Exceeds_Maximum=2147483647. (Superseded.)

Major Page Faults Per Second Number of major faults per second, these are page faults that directly require the loading of pages from disk. (Kernel 2.6 and greater.) Calculated on a 30 second interval. (Superseded.) Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum.

Number of Processes in Zombie State Number of processes currently in Zombie State. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Number of User Logins The current number of users logged in. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Page Faults Per Second The total number of page faults per second (major and minor). (Kernel 2.6 and above only.) Calculated on a 30 second interval. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Pages Paged In Per Second The pages paged in per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Pages Paged Out Per Second The pages paged out per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Pages Swapped In The pages swapped in. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Pages Swapped In Per Second The pages swapped in per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Pages Swapped Out The pages swapped out. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Pages Swapped Out Per Second The pages swapped out per second. Calculated on a 30 second interval. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Percent Change Context Switches Per Second The percentage change in the number of context switches per second. The following values are valid: integers in the range -100 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Percent Change Processes Created The percentage change in the number of processes created per second. The following values are valid: integers in the range -100 to 100. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

Processes Created Per Second The number of processes created per second. Calculated on a 30 second interval. The following values are valid: integers. Note: -1 indicates Not_Available and -2 indicates Not_Collected. (Superseded.)

System Load Last 1 Minute The load on the system for the last minute. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Load Last 5 Minutes The load on the system for the last 5 minutes. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Load Last 15 Minutes The load on the system for the last 15 minutes. The following values are valid: integers in the range 0 to 100. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

System Uptime The System Uptime in seconds, however it displays as a time counter on the IBM PureApplication System Monitoring Portal The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Number of Processes The total number of processes. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

Total Pages Paged In The total pages paged in. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Total Pages Paged Out The total pages paged out. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

4.3.47. User Login Attributes

The User Login attributes refer to user characteristics such as idle time, user name, location, and log in time.

Hostname (From) The host name associated with the log in for the user. The following values are valid: alphanumeric text strings with a maximum length of 256 characters.

Idle Time The number of minutes that have passed since a user last entered a command. The following values are valid: numeric values expressed as minutes in the range 0 to 20160. Use this attribute to check idle time.

Line The terminal device type or line to which the user is connected. The following values are valid: alphanumeric text strings with a maximum length of 16 characters.

Login Time The date and time the user logged in. Valid entries are displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Example: To express November 6, 1998, 1:05 p.m., enter 0981106130500000.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

User Login PID The log in ID of the user. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=9223372036854775807.

User Name The full name of a user. The following values are valid: alphanumeric text strings with a maximum length of 96 characters.

4.3.48. User Login Attributes (superseded)

The User Login attributes refer to user characteristics such as idle time, user name, location, and log in time. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Hostname (From) The host name associated with the log in for the user. The following values are valid: alphanumeric text strings with a maximum length of 256 characters. (Superseded.)

Idle Time The number of minutes that have passed since a user last entered a command. The following values are valid: numeric values expressed as minutes in the range 0 to 20160. Use this attribute to check idle time. (Superseded.)

Line The terminal device type or line to which the user is connected. The following values are valid: alphanumeric text strings with a maximum length of 16 characters. (Superseded.)

Login Time The date and time the user logged in. (Superseded.) Valid entries are displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Example: To express November 6, 1998, 1:05 p.m., enter 0981106130500000.

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

User Login PID The log in ID of the user. The following values are valid: integers. For example, the following value is valid: Value_Exceeds_Maximum=2147483647. (Superseded.)

User Name The full name of a user. The following values are valid: alphanumeric text strings with a maximum length of 32 characters. (Superseded.)

User Name (Unicode) The name of the user logging in to access the system. The following values are valid: text strings up to 64 bytes. This attribute is globalized (Unicode). (Superseded.)

4.3.49. VM Stats Attributes

The VM Stats attributes refer to memory characteristics such as the size of cached, free, and shared memory.

Free Virtual Storage (MB) The available virtual storage (in megabytes). Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Free Virtual Storage (Percent) Available Virtual Storage in percentage. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Memory Cached (MB) The size (in megabytes) of physical memory cached. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Memory Cached Percent Physical memory cached, in percent. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected.

Memory Free (MB) The size (in megabytes) of physical memory free. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Memory Free (Percent) The available real memory in percentage. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Memory in Buffers (MB) The size (in megabytes) of physical memory in buffers. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Memory Used (MB) The size (in megabytes) of physical memory used. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Memory Used (Percent) The used real memory in percentage. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Net Memory Used (MB) Physical Memory used (in MB) not considering Memory in Buffers and Memory Cached. It is calculated as Memory Used (MB) - Memory in Buffers (MB) - Memory Cached (MB). Note: the value -1 indicates Not Available, -2 indicates Not Collected, and 9223372036854775807 indicates Value_Exceeds_Maximum.

Net Memory Used (Percent) Physical Memory used (in Percent) not considering Memory in Buffers and Memory Cached. It is calculated as Memory Used (MB) - Memory in Buffers (MB) - Memory Cached (MB). Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Shared Memory (MB) The size (in megabytes) of physical memory shared. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Swap Space Free (MB) The size (in megabytes) of swap space free. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Swap Space Free (Percent) Available Swap Space (Percent). Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Swap Space Used (MB) The size (in megabytes) of swap space used. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Swap Space Used (Percent) Used Swap Space (Percent). Note: the value -1 indicates Not Available and -2 indicates Not Collected.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Memory (MB) The total size (in megabytes) of physical memory. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Total Memory Free (MB) Physical Memory free (in MB) not considering Memory in Buffers and Memory Cached. It is calculated as Memory Free (MB) + Memory in Buffers (MB) + Memory Cached (MB). The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Total Memory Free (Percent) Physical Memory free (in percent) not considering Memory in Buffers and Memory Cached. It is calculated as Memory Free (MB) + Memory in Buffers (MB) + Memory Cached (MB). The following values are valid: integers. Note: the value -1 indicates Not Available and the value -2 indicates Not Collected.

Total Swap Space (MB) The total size (in megabytes) of swap space. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Total Virtual Storage (MB) The total virtual storage (real plus swap storage) in MB. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Used Virtual Storage (MB) The used virtual storage in MB. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 9223372036854775807 indicates Value_Exceeds_Maximum.

Used Virtual Storage (Percent) The used virtual storage in percentage. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

4.3.50. VM Stats Attributes (superseded)

The VM Stats attributes refer to memory characteristics such as the size of cached, free, and shared memory. This attribute group is superseded. There is a new attribute group with the same name that replaces it.

Available Virtual Storage (MB) The available virtual storage in MB. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Available Virtual Storage (Percent) The available virtual storage in percentage. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Memory Cached (MB) The size (in megabytes) of physical memory cached. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Memory Free (MB) The size (in megabytes) of physical memory free. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Memory in Buffers (MB) The size (in megabytes) of physical memory in buffers. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Memory Used (MB) The size (in megabytes) of physical memory used. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Real Memory Available (Percent) Available Real Memory in Percent. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Real Memory Used (Percent) Used Real Memory (Percent). Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Shared Memory (MB) The size (in megabytes) of physical memory shared. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Swap Space Available (Percent) Available Swap Space (Percent). Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

Swap Space Free (MB) The size (in megabytes) of swap space free. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Swap Space Used (MB) The size (in megabytes) of swap space used. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Swap Space Used (Percent) Used Swap Space (Percent). Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

System Name The managed system name. The form should be hostname:agent_code. (Superseded.)

Examples include spark:LZ or deux.raleigh.ibm.com:LZ.

In workspace queries, this attribute should be set equal to the value $NODE$ in order to populate the workspace with data. This attribute is generally not included in situations, unless there is a need to customize the situation for a specific managed system.

Time Stamp The date and time the agent collects information as set on the monitored system. (Superseded.) The timestamp for SCAN and STR functions is displayed in the CYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01) where:

C = Century (0 for 20th, 1 for 21st)

Y = Year

M = Month

D = Day

H = Hour

M = Minute

S = Second

m = millisecond

Total Memory (MB) The total size (in megabytes) of physical memory. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Total Swap Space (MB) The total size (in megabytes) of swap space. The following values are valid: integers. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Total Virtual Storage (MB) The total virtual storage (real plus swap storage) in MB. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Used Virtual Storage (MB) The used virtual storage in MB. Note: the value -1 indicates Not Available, the value -2 indicates Not Collected, and the value 2147483647 indicates Value_Exceeds_Maximum. (Superseded.)

Used Virtual Storage (Percent) The used virtual storage in percentage. Note: the value -1 indicates Not Available and -2 indicates Not Collected. (Superseded.)

4.4. Disk capacity planning for historical data

Disk capacity planning for a monitoring agent is a prediction of the amount of disk space to be consumed for each attribute group whose historical data is being collected. Required disk storage is an important factor to consider when you are defining data collection rules and your strategy for historical data collection.

The table in this chapter provides the following information required to calculate disk space for this agent:

• Table is the table name as it is displayed in the warehouse database, if the attribute group is configured to be written to the warehouse.
• Attribute group is the name of the attribute group as it is displayed in the warehouse configuration panel.
• Bytes per instance (agent) is an estimate of the record length for each row or instance written to the agent disk for historical data collection. This estimate can be used for agent disk space planning purposes.
• Database bytes per instance (warehouse) is an estimate of the record length for detailed records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Detailed records are those that have been uploaded from the agent for long-term historical data collection. This estimate can be used for warehouse disk space planning purposes.
• Aggregate bytes per instance (warehouse) is an estimate of the record length for aggregate records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Aggregate records are created by the Summarization agent for attribute groups that have been configured for summarization. This estimate can be used for warehouse disk space planning purposes.

In addition to the information in the tables, you must know the number of instances of data that you plan to collect. An attribute group can have single or multiple instances of data depending on the application environment that is being monitored. For example, if your attribute group is monitoring each processor in your computer and you have a dual processor computer, the number of instances is 2.

The following table contains capacity planning information for the data logged by Warehouse Proxy.

Capacity planning for historical data logged by component

Table	Attribute group	Bytes per instance (agent)	Database bytes per instance (warehouse)	Aggregate bytes per instance (warehouse)
KHDCONF	KHD_CONFIG	212	224	261
KHDDBINFO	KHD_DB_INFO	1312	1328	1365
KHDLASTERR	KHD_LAST_ERROR_DETAILS	1607	1623	1660
KHDLOADST	KHD_LOAD_STATISTICS	112	153	433
KHDNODELST	KHD_NODE_LIST	168	169	251
KHDRGADLST	KHD_REGISTRATION_ADDRESS_LIST	296	295	332
KHDRPCS	KHD_RPCSOURCE_STATISTICS	96	121	329
KHDTEMSLST	KHD_WAREHOUSE_TEMS_LIST	108	105	142
KHDWORKQ	KHD_WORK_QUEUE	112	141	394

For more information about historical data collection, see the Administrator's Guide.

Situations reference

This chapter contains an overview of situations, references for detailed information about situations, and descriptions of the predefined situations included in this monitoring agent.

5.1. About situations

A situation is a logical expression involving one or more system conditions. Situations are used to monitor the condition of systems in your network. You can manage situations from PureApplication Monitoring Portal by using the Situation editor.

The monitoring agents that you use to monitor your system environment are delivered with a set of predefined situations that you can use as-is or you can create new situations to meet your requirements. Predefined situations contain attributes that check for system conditions common to many enterprises.

Using predefined situations can improve the speed with which you can begin using the Monitoring Agent for Linux. You can examine and, if necessary, change the conditions or values being monitored by a predefined situation to those best suited to your enterprise.

You can display predefined situations and create your own situations using the Situation editor. The left frame of the Situation editor initially lists the situations associated with the Navigator item that you selected. When you click a situation name or create a new situation, the right frame opens with the following tabs:

Formula

Formula describing condition being tested

Distribution

List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed. All of the Monitoring Agent for Linux managed systems are assigned by default.

Expert advice

Comments and instructions to be read in the event workspace

Action

Command to be sent to the system

Util

Options to close the event after a period of time, or when another situation becomes true

5.2. More information about situations

The IBM PureApplication System Monitoring Server User's Guide contains more information about predefined and custom situations and how to use them to respond to alerts.

5.3. Predefined situations

This monitoring agent contains the following predefined situations, which are organized by Navigator item.

Agent level Navigator items

• Warehouse Proxy
  • Not applicable

• Configuration
  • Not applicable
  • KHD_DB_Connectivity

• Statistics
  • Not applicable
  • KHD_Error_Critical
  • KHD_Error_Fatal

The remaining sections of this chapter contain descriptions of each of these situations. The situations are organized by Navigator item. The following information is provided about each situation:

Description

Information about the conditions that the situation tests.

Formula

Syntax that contains one or more logical expressions describing the conditions for the situation to monitor. The information center topic that corresponds to this situation contains the formula for this agent.

Distribution

Whether the situation is automatically distributed to instances of the agent or is available for manual distribution.

Run at startup

Whether the situation starts monitoring when the agent starts.

Sampling interval

Number of seconds that elapses between one sample of data that the monitoring agent collects for the server and the next sample.

Situation persistence

Whether the conditions specified in the situation evaluate to "true" for the defined number of occurrences in a row before the situation is raised. The default of one means no persistence-checking takes place.

Severity

Severity of the predefined events: Warning, Informational, or Critical.

Clearing conditions

Controls when a true situation closes: after a period of time, when another situation is true, or whichever occurs first if both are selected.

5.3.1. Linux_AMS_Alert_Critical situation

Monitors to determine if one of the following conditions is true:

• A managed agent has exceeded its restart count for the day as configured in the 'maxRestarts' field of its Common Agent Package file.
• A managed agent is overutilizing the available CPU resources as configured in the 'cpuThreshold' field of its Common Agent Package file.
• A managed agent is overutilizing the available system memory resources as configured in the 'memoryThreshold' field of its Common Agent Package file.
• An attempt at auto-restarting a managed agent failed.
• An attempt at starting a stopped or manually stopped managed agent failed.
• The Agent Management Services watchdog is no longer reliable. If either watchdog stops monitoring, you will receive this message.

The formula for this situation is as follows:

Alert Message=='Agent exceeded restart count' OR 
Alert Message=='Agent overutilizing CPU' OR 
Alert Message=='Agent overutilizing memory'  OR 
Alert Message=='Agent restart failed' OR 
Alert Message=='Agent manual stop failed' OR
Alert Message =='Agent Management Services watchdog no longer reliable'

5.3.2. Linux_BP_AvgCpuBusyPct1h_Critic situation

Monitors total percent CPU (system + user) busy for the sum of all the CPU on the system. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_CPU_Averages.CPU_Usage_Current_Average *GE 95.0

5.3.3. Linux_BP_CpuBusyPct_Critical situation

Monitors if the CPU workload is high. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF ( ( *VALUE KLZ_CPU.CPU_ID *NE Aggregate *AND *VALUE KLZ_CPU.Busy
_CPU *GT 95.0 ) *OR ( *VALUE KLZ_CPU.CPU_ID *EQ Aggregate *AND *VALUE KL
Z_CPU.Busy_CPU *GT 90.0 ) )

5.3.4. Linux_BP_CpuWaitIOPct_Warning situation

Monitors CPU I/O waits. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_CPU.Wait_IO_CPU *GT 10 *AND *VALUE KLZ_CPU.CPU_ID *EQ
 Aggregate

5.3.5. Linux_BP_LoadAvg5min_Critical situation

Monitors the load on the system for the last five minutes. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF ( ( *VALUE Linux_Machine_Information.Number_of_Processors_Online
 *EQ 1 *AND *VALUE KLZ_System_Statistics.System_Load_5min *GT 4.0 ) *OR 
( *VALUE Linux_Machine_Information.Number_of_Processors_Online *EQ 2 *AN
D *VALUE KLZ_System_Statistics.System_Load_5min *GT 8 ) *OR ( *VALUE Lin
ux_Machine_Information.Number_of_Processors_Online *EQ 3 *AND *VALUE KLZ
_System_Statistics.System_Load_5min *GT 12 ) *OR ( *VALUE Linux_Machine_
Information.Number_of_Processors_Online *EQ 4 *AND *VALUE KLZ_System_Sta
tistics.System_Load_5min *GT 16 ) *OR ( *VALUE Linux_Machine_Information
.Number_of_Processors_Online *EQ 6 *AND *VALUE KLZ_System_Statistics.Sys
tem_Load_5min *GT 24 ) *OR ( *VALUE Linux_Machine_Information.Number_of_
Processors_Online *EQ 8 *AND *VALUE KLZ_System_Statistics.System_Load_5m
in *GT 32 ) )

5.3.6. Linux_BP_NetTotalErrPct_Warning situation

Monitors the percentage of errors of received or transmitted network packets. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_Network.Total_Error_Percent *GT 10

5.3.7. Linux_BP_NumberZombies_Warning situation

Monitors the number of processes for defunct. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_System_Statistics.Processes_Zombie_Count *GE 50

5.3.8. Linux_BP_ProcHighCpu_Critical situation

Monitors the CPU percent utilization by all processes except kswapd. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_Process.Busy_CPU_Pct *GE 95.0 *AND *VALUE KLZ_Process
.Process_Command_Name *NE kswapd

5.3.9. Linux_BP_ProcMissing_Critical situation

Monitors specified processes that are not found in the system. The process might have been killed or might never have been started. An asterisk is used to identify the specific process started from the system directory. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *MISSING KLZ_Process.Proc_CMD_Line *EQ ( '/usr/*/sshd','/usr/*/s
yslogd','/usr/*/ntpd','/usr/*/inetd','/usr/*/crond' )

5.3.10. Linux_BP_SpaceUsedPct_Critical situation

Monitors all mounted file systems for space used percentage. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_Disk.Disk_Used_Percent *GE 95 *AND *VALUE KLZ_Disk.FS
_Type *NE nfs

5.3.11. Linux_BP_SpaceUsedPctCustom_Cri situation

Monitors only specific file systems for space used percentage, for example, /home. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF ( ( *VALUE KLZ_Disk.Mount_Point *EQ '/' *AND *VALUE KLZ_Disk.Dis
k_Used_Percent *GE 90 ) *OR ( *VALUE KLZ_Disk.Mount_Point *EQ '/home' *A
ND *VALUE KLZ_Disk.Disk_Used_Percent *GE 80 ) ) *UNTIL ( *SIT Linux_BP_S
paceUsedPct_Critical )

5.3.12. Linux_BP_SwapSpaceUsedPct_Criti situation

Monitors the percentage of swap space used. This situation is automatically installed, but not automatically distributed, during installation to the default MSL or managed system.

The formula for this situation is as follows:

*IF *VALUE KLZ_VM_Stats.Swap_Used_Pct *GT 40

5.3.13. Linux_Fragmented_File_System situation

This situation has been superseded by Linux_Fragmented_File_System_2. Monitors the percentage of i-nodes to disk space. An exception condition occurs when the percentage of i-nodes to disk space used is high, which could indicate high disk fragmentation on the disk.

This situation has the following formula.

IF VALUE Linux_Disk.Space_Used_Percent LT 85 AND 
VALUE Linux_Disk.Inodes_Used_Percent GT 80

5.3.14. Linux_Fragmented_File_System_2 situation

Monitors the percentage of i-nodes to disk space. An exception condition occurs when the percentage of i-nodes to disk space used is high, which could indicate high disk fragmentation on the disk.

This situation has the following formula.

IF VALUE KLZ_Disk.Disk_Used_Percent LT 85 AND 
VALUE KLZ_Disk.Inodes_Used_Percent *GT 80

5.3.15. Linux_High_CPU_Overload situation

This situation has been superseded by Linux_High_CPU_Overload_2. Monitors the percentage of time the processor is busy. An exception condition occurs when the percentage is extremely high.

This situation has the following formula.

IF VALUE Linux_CPU.Idle_CPU LT 10.0 AND VALUE Linux_CPU.CPU_ID EQ Aggregate

5.3.16. Linux_High_CPU_Overload_2 situation

Monitors the percentage of time the processor is busy. An exception condition occurs when the percentage is extremely high.

This situation has the following formula.

IF VALUE KLZ_CPU.Idle_CPU LT 10.0 AND VALUE KLZ_CPU.CPU_ID EQ 
Aggregate

5.3.17. Linux_High_CPU_System situation

This situation has been superseded by Linux_High_CPU_System_2. Monitors the percentage of processor time that is used for system calls to check for runaway processes. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_CPU.CPU_ID EQ Aggregate AND VALUE 
Linux_CPU.System_CPU GT 80.0

5.3.18. Linux_High_CPU_System_2 situation

Monitors the percentage of processor time that is used for system calls to check for runaway processes. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_CPU.CPU_ID EQ Aggregate AND VALUE KLZ_CPU.System_CPU 
GT 80.0

5.3.19. Linux_High_Packet_Collisions situation

This situation has been superseded by Linux_High_Packet_Collisions_2. Monitors the percentage of packet collisions during data transmission. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_Network.Collision_Percent GT 10

5.3.20. Linux_High_Packet_Collisions_2 situation

Monitors the percentage of packet collisions during data transmission. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_Network.Collision_Percent GT 10

5.3.21. Linux_High_RPC_Retransmit situation

This situation has been superseded by Linux_High_RPC_Retransmit_2. Monitors the percentage of retransmits because of RPC Server calls. An exception condition occurs when the percentage is extremely high.

This situation has the following formula.

IF PCTCHANGE Linux_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 10

5.3.22. Linux_High_RPC_Retransmit_2 situation

Monitors the percentage of retransmits because of RPC Server calls. An exception condition occurs when the percentage is extremely high.

This situation has the following formula.

IF PCTCHANGE KLZ_RPC_Statistics.RPC_Client_Calls_Retransmitted GT
 10

5.3.23. Linux_High_Zombies situation

This situation has been superseded by Linux_High_Zombies_2. Monitors the number of processes in zombie state. An exception condition occurs when the number is high.

This situation has the following formula.

IF VALUE Linux_Process.State EQ Zombie AND COUNT Linux_Process.State GT 20

5.3.24. Linux_High_Zombies_2 situation

Monitors the number of processes in zombie state. An exception condition occurs when the number is high.

This situation has the following formula.

IF VALUE KLZ_Process.State EQ Zombie AND COUNT 
KLZ_Process.Parent_Process_ID GT 20

5.3.25. Linux_Low_Pct_Inodes situation

This situation has been superseded by Linux_Low_Pct_Inodes_2. Monitors the percentage of available i-nodes. An exception condition occurs when the number is low.

This situation has the following formula.

IF VALUE Linux_Disk.Inodes_Used_Percent GT 80

5.3.26. Linux_Low_Pct_Inodes_2 situation

Monitors the percentage of available i-nodes. An exception condition occurs when the number is low.

This situation has the following formula.

IF VALUE KLZ_Disk.Inodes_Used_Percent GT 80

5.3.27. Linux_Low_percent_space situation

This situation has been superseded by Linux_Low_percent_space_2. Monitors the percentage of space available on a file system. An exception condition occurs when the percentage is low.

This situation has the following formula.

IF VALUE Linux_Disk.Space_Available_Percent LT 15 

5.3.28. Linux_Low_percent_space_2 situation

Monitors the percentage of space available on a file system. An exception condition occurs when the percentage is low.

This situation has the following formula.

IF VALUE KLZ_Disk.Disk_Free_Percent LT 15 

5.3.29. Linux_Low_Space_Available situation

This situation has been superseded by Linux_Low_Space_Available_2. Monitors the available space on a file system. An exception condition occurs when the amount of space is low.

This situation has the following formula.

IF VALUE Linux_Disk.Space_Available LT 7 

5.3.30. Linux_Low_Space_Available_2 situation

Monitors the available space on a file system. An exception condition occurs when the amount of space is low.

This situation has the following formula.

IF VALUE KLZ_Disk.Disk_Free LT 7 

5.3.31. Linux_Network_Status situation

This situation has been superseded by Linux_Network_Status_2. Monitors whether the Network Interface Card is up or not. An exception condition occurs when the network interface card is not up.

This situation has the following formula.

IF VALUE Linux_Network.Interface_Status NE UP

5.3.32. Linux_Network_Status_2 situation

Monitors whether the Network Interface Card is up or not. An exception condition occurs when the network interface card is not up.

This situation has the following formula.

IF VALUE KLZ_Network.Interface_Status NE UP

5.3.33. Linux_NFS_Buffer_High situation

This situation has been superseded by Linux_NFS_Buffer_High_2. Monitors the number of RPC retransmissions with no duplicate acknowledgements. An exception condition occurs when the number of retransmissions is high.

This situation has the following formula.

IF VALUE Linux_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 60 AND
 PCTCHANGE Linux_RPC_Statistics.RPC_Client_Times_Authentication_Refreshed GT 5

5.3.34. Linux_NFS_Buffer_High_2 situation

Monitors the number of RPC retransmissions with no duplicate acknowledgements. An exception condition occurs when the number of retransmissions is high.

This situation has the following formula.

IF VALUE KLZ_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 60 
AND PCTCHANGE KLZ_RPC_Statistics.RPC_Client_Times_Authentication_Refreshed 
GT 5

5.3.35. Linux_NFS_Getattr_High situation

This situation has been superseded by Linux_NFS_Getattr_High_2. Monitors the percentage of NFS server calls to read client attributes. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Get_Attribute_Calls_Pct GT 40

5.3.36. Linux_NFS_Getattr_High_2 situation

Monitors the percentage of NFS server calls to read client attributes. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_NFS_Statistics.NFS_Get_Attribute_Calls_Pct GT 40

5.3.37. Linux_NFS_rdlink_high situation

This situation has been superseded by Linux_NFS_rdlink_high_2. Monitors the percentage of NFS server calls for read link operations. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Read_Link_Pct GT 10

5.3.38. Linux_NFS_rdlink_high_2 situation

Monitors the percentage of NFS server calls for read link operations. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_NFS_Statistics.NFS_Read_Link_Pct GT 10

5.3.39. Linux_NFS_Read_High situation

This situation has been superseded by Linux_NFS_Read_High_2. Monitors the percentage of NFS server calls for read operations. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Read_Calls_Pct GT 30

5.3.40. Linux_NFS_Read_High_2 situation

Monitors the percentage of NFS server calls for read operations. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_NFS_Statistics.NFS_Read_Calls_Pct GT 30

5.3.41. Linux_NFS_Writes_High situation

This situation has been superseded by Linux_NFS_Writes_High_2. Monitors the percentage of NFS server calls for write operations. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Writes_Pct GT 15 

5.3.42. Linux_NFS_Writes_High_2 situation

Monitors the percentage of NFS server calls for write operations. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_NFS_Statistics.NFS_Writes_Pct GT 15 

5.3.43. Linux_Packets_Error situation

This situation has been superseded by Linux_Packets_Error_2. Monitors the percentage of network packets in error. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_Network.Total_Error_Percent GT 10

5.3.44. Linux_Packets_Error_2 situation

Monitors the percentage of network packets in error. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_Network.Total_Error_Percent GT 10

5.3.45. Linux_Process_High_Cpu situation

This situation has been superseded by Linux_Process_High_Cpu_2. Monitors the percentage of processor time used by a process. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_Process.Busy_CPU_Pct GT 60.0

5.3.46. Linux_Process_High_Cpu_2 situation

Monitors the percentage of processor time used by a process. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_Process.Busy_CPU_Pct GT 60.0

5.3.47. Linux_Process_High_Instant_CPU situation

Monitors the CPU usage percentage used by a process. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE KLZ_Process.Instant_Busy_CPU_Pct GT 60.0

5.3.48. Linux_Process_stopped situation

This situation has been superseded by Linux_Process_stopped_2. Monitors the number of stopped processes on the system. An exception condition occurs when the number is high.

This situation has the following formula.

IF VALUE Linux_Process.State NE Running AND 
VALUE Linux_Process.State NE Sleeping

5.3.49. Linux_Process_stopped_2 situation

Monitors the number of stopped processes on the system. An exception condition occurs when the number is high.

This situation has the following formula.

IF VALUE KLZ_Process.State NE Running AND VALUE 
KLZ_Process.State NE Sleeping

5.3.50. Linux_RPC_Bad_Calls situation

This situation has been superseded by Linux_RPC_Bad_Calls_2. Monitors the percentage of rejected RPC server or client calls. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF ( ( VALUE Linux_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 30 
) OR ( VALUE Linux_RPC_Statistics.RPC_Server_Calls_Rejected GT 30 ) )

5.3.51. Linux_RPC_Bad_Calls_2 situation

Monitors the percentage of rejected RPC server or client calls. An exception condition occurs when the percentage is high.

This situation has the following formula.

IF ( ( VALUE KLZ_RPC_Statistics.RPC_Client_Calls_Retransmitted 
GT 30 ) OR ( VALUE KLZ_RPC_Statistics.RPC_Server_Calls_Rejected GT 30 )  )

5.3.52. Linux_System_Thrashing situation

This situation has been superseded by Linux_System_Thrashing_2. Monitors the swap space paging activity on the system. An exception condition occurs when the activity is extremely high.

This situation has the following formula.

IF ( ( VALUE Linux_System_Statistics.Pages_paged_out_per_sec GT 400.0 ) 
OR ( *VALUE Linux_System_Statistics.Pages_paged_in_per_sec GT 400.0 ) )

5.3.53. Linux_System_Thrashing_2 situation

Monitors the swap space paging activity on the system. An exception condition occurs when the activity is extremely high.

This situation has the following formula.

IF ( ( VALUE KLZ_System_Statistics.Pages_paged_out_per_sec GT 400
.0 ) OR ( VALUE KLZ_System_Statistics.Pages_paged_in_per_sec 
GT 400.0) )

Take Action commands reference

This chapter contains an overview of Take Action commands, references for detailed information about Take Action commands, and a description of the Take Actions commands included in this monitoring agent.

6.1. About Take Action commands

Take Action commands can be run from the desktop or included in a situation or a policy.

When included in a situation, the command executes when the situation becomes true. A Take Action command in a situation is also referred to as reflex automation. When you enable a Take Action command in a situation, you automate a response to system conditions. For example, you can use a Take Action command to send a command to restart a process on the managed system or to send a text message to a cell phone.

Advanced automation uses policies to perform actions, schedule work, and automate manual tasks. A policy comprises a series of automated steps called activities that are connected to create a workflow. After an activity is completed, PureApplication Monitoring Portal receives return code feedback, and advanced automation logic responds with subsequent activities prescribed by the feedback.

6.2. More information about Take Action commands

For more information about working with Take Action commands, see the IBM PureApplication System Monitoring Server User's Guide.

6.3. Predefined Take Action commands

This monitoring agent contains the following Take Action commands:

• AMS Recycle Agent Instance
• AMS Reset Agent Daily Restart Count
• AMS Start Agent
• AMS Start Agent Instance
• AMS Stop Agent
• AMS Start Management
• AMS Stop Management
• Sample kill Process

The remaining section of this chapter contains a description of this Take Action command. The following information is provided about the Take Action command:

Description

Which actions the command performs on the system to which it is sent

Arguments

List of arguments, if any, for the Take Action with a short description and default value for each one

Destination systems

Where the command is to be executed: on the Managed System (monitoring agent) where the agent resides or on the Managing System (PureApplication Monitoring Server) to which it is connected

Usage notes

Additional relevant notes for using the Take Actions

6.3.1. AMS Recycle Agent Instance

Description

Use this action to stop and start any agent with a single request. This recycle does not increase the restart count of an agent.

Arguments

Agent Name

The name of the agent as it is displayed in the Agents' Runtime Status View's Agent Name column.

Process Name

The name of the agent's process as it is displayed in the Agents' Runtime Status View's Process Name column.

Instance Name

If it exists, the name of an agent instance as it is displayed in the Agents' Runtime Status View's Instance Name column.

Process ID

The process ID of the agent process as it appears in the Agents' Runtime Status View's Process ID column.

Destination systems

Managed system

Usage notes

Not available to previous versions of the OS agents. To use this action against the OS agent, the Agent Management Services watchdog must be running.

6.3.2. AMS Reset Agent Daily Restart Count

Description

Use this action to reset the daily restart count of an agent to 0.

Arguments

Agent Name

The name of the agent as it is displayed in the Agents' Runtime Status View's Agent Name column.

Process Name

The name of the agent's process as it is displayed in the Agents' Runtime Status View's Process Name column.

Instance Name

If it exists, the name of an agent instance as it is displayed in the Agents' Runtime Status View's Instance Name column.

Destination systems

Managed system

Usage notes

Not available to previous versions of the OS agents. To use this action against the OS agent, the Agent Management Services watchdog must be running.

6.3.3. AMS Start Agent action

Description

Use this action to start an agent that is under the management of Agent Management Services. The action includes an optional input field for resetting the Daily Restart Count back to 0. This is helpful when an agent has exceeded its maxRestartCount for the day.

Arguments

Agent Name

The name of the agent as it is displayed in the Agents' Runtime Status View's Agent Name column.

Daily Restart Count

Value indicating whether to reset the daily restart count. The value 1 indicates True, and the value 0 (default) indicates False.

Process Name

The name of the process representing the agent instance as it is displayed in the Agents' Runtime Status View's Process Name column.

Destination systems

Managed system

Usage notes

You cannot target the Monitoring Agent for Linux OS with this action. Only the other agents being managed by Agent Management Services running on the Monitoring Agent for Linux OS can be targeted with this action.

6.3.4. AMS Start Agent Instance action

Description

Use this action to start a monitoring agent instance of type ITM Windows or ITM UNIX that is under the management of Agent Management Services. The action includes an optional input field for resetting the Daily Restart Count back to 0. This is helpful when an agent instance has exceeded its maxRestartCount for the day.

Arguments

Agent Name

The name of the agent as it is displayed in the Agents' Runtime Status View's Agent Name column.

Daily Restart Count

Value indicating whether to reset the daily restart count. The value 1 indicates True, and the value 0 (default) indicates False.

Process Name

The name of the process representing the agent instance as it is displayed in the Agents' Runtime Status View's Process Name column.

Instance Name

The name of the monitoring agent instance as it is displayed in the Agents' Runtime Status View's Instance Name column.

Destination systems

Managed system

Usage notes

You cannot target the Monitoring Agent for Linux OS with this action. Only the other agents being managed by Agent Management Services running on the Monitoring Agent for Linux OS can be targeted with this action.

6.3.5. AMS Stop Agent action

Description

Use this action to stop an agent that is under the management of Agent Management Services. The action will put a running instance of an agent into the 'Manually Stopped' state, meaning that Agent Management Services will not perform any auto-restarts. To prompt Agent Management Services to commence auto-restarting, use the AMS Start Agent command or the AMS Start Agent Instance command to manually put the agent back into a Running state.

Arguments

Process ID

By default, this argument is populated with the Process ID of the particular agent instance selected from the Tivoli Enterprise Portal. To stop all instances of an agent, such as by using the tacmd executeaction AMS Stop Agent command, leave this argument blank.

Destination systems

Managed system

Usage notes

You cannot target the Monitoring Agent for Linux OS with this action. Only the other agents being managed by Agent Management Services running on the Monitoring Agent for Linux OS can be targeted with this action.

6.3.6. AMS Start Management action

Description

Use this action to put an agent under the management of Agent Management Services. This management is what provides auto-restart capability.

Destination systems

Managed system

Usage notes

You now can target the Monitoring Agent for Linux OS with this command. Starting management of the OS Agent restarts the physical watchdog and rearms Agent Management Services. Watch of managed agents resumes. There is no change to non-OS agent management operations.

6.3.7. AMS Stop Management action

Description

Use this action to remove an agent from management by Agent Management Services. The action will cause the Agent Management Services watchdog to stop performing health checks and auto restarts.

Destination systems

Managed system

Usage notes

You now can target the Monitoring Agent for Linux OS with this command. However, stopping management stops the physical watchdog and disarms Agent Management Services, which also stops watching and restarting of any managed agents. While the OS Agent is unmanaged, the Start Manage action will not be allowed against any other non-OS agent. The Linux_AMS_Alert_Critical situation is activated if this take action is run on the OS agent.

6.3.8. Sample_kill_Process action

Description

Kills the process named in the parameter supplied and enables you to issue ad-hoc commands from the PureApplication Monitoring Portal that the Monitoring Agent for Linux OS will execute on your behalf.

Arguments

Process ID

The Process ID (PID) of the process you would like to kill.

Destination systems

Managed system

Usage notes

The kill command is executed directly by the remote Monitoring Agent for Linux OS. Because it is easy to kill processes unintentionally, you need to exercise caution if the monitoring agent is run as superuser (root).

Policies reference

This chapter contains an overview of policies and references for detailed information about policies.

7.1. About policies

Policies are an advanced automation technique for implementing more complex workflow strategies than you can create through simple automation.

A policy is a set of automated system processes that can perform actions, schedule work for users, or automate manual tasks. You use the Workflow Editor to design policies. You control the order in which the policy executes a series of automated steps, which are also called activities. Policies are connected to create a workflow. After an activity is completed, PureApplication Monitoring Portal receives return code feedback and advanced automation logic responds with subsequent activities prescribed by the feedback.

Note: For monitoring agents that provide predefined policies, predefined policies are not read-only. Do not edit these policies and save over them. Software updates will write over any of the changes that you make to these policies. Instead, clone the policies that you want to change to suit your enterprise.

7.2. More information about policies

For more information about working with policies, see the IBM PureApplication System Monitoring Server User's Guide.

For information about using the Workflow Editor, see the IBM PureApplication System Monitoring Server Administrator's Guide or the PureApplication Monitoring Portal online help.

7.3. Predefined policies

There are no predefined policies for this monitoring agent.

Tivoli Common Reporting for the monitoring agent

This chapter contains a description of the data model for the Monitoring Agents for Windows OS, Linux OS, and UNIX OS reports and descriptions of these reports.

See the following additional information about using reports with this monitoring agent:

• The "Tivoli Common Reporting" chapter in the PureApplication System Monitoring Server Administrator's Guide, V6.2.3 or later contains information about prerequisites and importing and running the reports.
• To enable Tivoli Common Reporting for monitoring agents, use the Report Installer. When requested by the Report Installer, choose the "PureApplication System Monitoring Server OS Agents Reports" package.

Complete documentation for the Tivoli Common Reporting tool is located at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/tcr_welcome.html

You must have the following prerequisite actions completed to use this function:

• PureApplication System Monitoring Server v6.2.3 must be installed with the OS agents up and running.
• The Summarization and Pruning agent must be started with or without shifts enabled.
• Historical collection must be turned on and collection started.
• Summarized tables and views must be created and populated in the Tivoli Data Warehouse.

The data model for the Monitoring Agents for Windows OS, Linux OS, and UNIX OS reports will have the following features:

• The model covers data from OS Agents only.
• The model contains a subset of the attribute groups collected by OS Agents in aggregated form for time dimension: AVG, MIN, MAX, SUM, LAT, TOT, HI, LOW.
• The model includes a Managed System dimension with the Agent Type attribute (on Windows, Linux, and UNIX systems). It is placed in the PureApplication System Monitoring Server Shared Dimensions namespace.
• The model includes all the aggregations handled by Summarization and Pruning from daily to yearly including the raw data.
• The model contains forecasting based on the linear trend for the following metrics for each time dimension:

  For Linux:

  • KLZ_CPU_FCAST_XX.AVG_Idle_CPU
  • KLZ_Disk_FCAST_XX.AVG_Disk_Used_Percent
  • KLZ_VM_Stats_FCAST_XX.AVG_Used_Virtual_Storage_Pct
  • KLZ_Network_FCAST_XX.AVG_Bytes_Transmitted_per_sec
  • KLZ_Network_FCAST_XX.AVG_Bytes_Received_per_sec

  For UNIX:

  • System_FCAST_XX.AVG_Idle_CPU
  • Disk_FCAST_XX.AVG_Space_Used_Percent
  • Unix_Memory_FCAST_XX.AVG_Virtual_Storage_Pct_Used
  • Network_FCAST_XX.AVG_Transmitted_MB_Total
  • Network_FCAST_XX.AVG_Received_MB_Total

  For Windows:

  • NT_System_FCAST_XX.AVG_%_Total_Processor_Time
  • NT_Logical_Disk_FCAST_XX.AVG_%_Used
  • NT_Memory_64_FCAST_XX.AVG_Available_Usage_Percentage
  • NT_Server_FCAST_XX.AVG_Bytes_Transmitted/sec
  • NT_Server_FCAST_XX.AVG_Bytes_Received/sec

• The metrics are organized in the following way:
  • Key Metrics
    • Performance
    • Availability

  • Extended metrics

• The metric's data items names reflect the catalog attributes names with the following suffixes:
  • SUM_ into (Sum)
  • LAT_ into (Latest)
  • MIN_ into (Minimum)
  • MAX_ into (Maximum)
  • TOT_ into (Total)
  • AVG_ into (Average)
  • HI_ into (Higher)
  • LOW_ into (Lower)

• Support for raw data is provided.
• The Summarization and Pruning configuration is shown in a specific query subject (Summarization and Pruning Configuration). The result is one row that represents the most recent entry in the KSY_SUMMARIZATION_CONFIG_DV view. The query subject contains the following query items:
  • Shift Enabled. The value is 1 if the shifts hours were specified, otherwise, the value is 0.
  • Vacations Enabled. The value is 1 if the vacations days were specified, otherwise, the value is 0.
  • Peak Hours per Day. The value contains the number of peak hours specified in the shifts hours settings.

• An availability daily data query subject for each agent type is provided. Metrics are computed using the following specific availability attributes: KLZ_System_Statistics.TOT_System_Uptime, System_DV.TOT_Up_Time, NT_System.TOT_System_Up_Time_64. The calculated query items have the following meaning:
  • % Up Time. The percentage the system is available in the day.
  • % Down Time. The percentage the system is not available in the day.
  • Up Days. The portion of the day the system is available.
  • Down Days. The portion of the day the system is not available.
  • MTBSI. Mean Time Before System Interruption (in hours).
  • MTTR. Mean Time To Recovery (in hours).

The following paragraphs describe the reports. In particular, they contain the required views for each one. If these views are not present, the report might not work. To ensure that the required views are present, run the following query against the Tivoli Data Warehouse:

DB2: select distinct "VIEWNAME" from SYSCAT.VIEWS where "VIEWNAME" like '%V'
Oracle: select distinct "VIEW_NAME" from USER_VIEWS where "VIEW_NAME" like '%V'
MS SQL Server: select distinct "NAME" from SYS.VIEWS where "NAME" like '%V'

The following databases are supported: DB2, Oracle, and SQL Server.

The following reports are available:

• Utilization Details for Single Resource

  This report shows CPU, memory, disk, network use and top 10 CPU use processes for a system during the selected time period in a line chart. Statistical process information is shown in all line charts (including average, upper and lower control limits). A linear trending feature is also provided and it is based on the selected forecast period.

• Utilization Details for Multiple Resources

  This report shows CPU, memory, disk and network use for multiple systems during the selected time period in an overlaid line chart. A linear trending feature is also provided, and it is based on the selected forecast period.

• Utilization Comparison for Single Resource

  This report shows the comparison between CPU, disk and memory use for a particular server, over a period of time, in an overlaid line chart.

• Utilization Comparison for Multiple Resource

  This report shows the comparison between CPU, disk and memory use for the selected servers over a period of time.

• Utilization Heat Chart for Single Resource

  This report helps identify patterns of use of a particular system over a period of time. The first column shows dates during the selected time period and the other columns represent hours during the day. The chart can be used for showing a heat chart for CPU, Memory and Disk or all three in the same report. The dates have hyperlinks that you can use to drill down to Utilization Details for Single Resource. A linear trending feature is also provided, which is based on the selected forecast period.

• Memory Utilization for Single Resource

  This report shows memory usage details for a specific system. It uses a line chart to show the percentage of virtual, physical and swap memory usage. It also provides finer memory metrics in a table.

• Memory Utilization for Multiple Resources Comparison

  This report shows memory usage details for multiple systems over a period of time. It uses three overlaid line charts for virtual, physical and swap memory.

• Top Resources Utilization

  This report shows top resources by CPU, Disk and Memory use. The stacked bars show average CPU used and free (in percent) for each system over the selected report period. If the number of systems is less than 20, then a bar is shown in each row. For example, there are 20 rows in the table with charts for each system. If the number of systems is more than 20, then there is a bar chart on top with the top 20 systems, and the rest of the data is in the table. This is done to eliminate overcrowding of the bars in the chart.

• Top Situations by Status

  This report shows the top 10 situations sorted by the selected status in a bar chart, along with finer details on all the top situations, listed in a table.

• Enterprise Daily Utilization Heat Chart

  This report shows CPU, disk and memory patterns for all servers, for a select operating system type, and on a particular date. The first column lists the server names. The rest of the columns show use data during the day hours and the last column shows the average for the server on the selected date. You can choose to see either CPU, disk, memory or all metrics.

• Enterprise Resources List

  This report lists all the Windows, Linux and UNIX resources in the environment. By clicking on a resource name, you can drill through to see the use details for that resource over the last 30 days.

• Enterprise Summary

  This report shows the overall availability and use of all Windows, Linux and UNIX monitoring agents.

• Top Resources by Availability

  This report displays availability of the top N systems based on System Uptime over a period of time.

• Top Resources Utilization Summary Heat Chart

  This report shows top resources by CPU, Disk or Memory use in a summary heat chart.

• Resource Availability Comparison

  This report shows availability comparison between two or more servers.

• Top Resources by Availability (MTTR/MTBSI)

  This report displays availability trending of the top N systems based on the Mean Time Before System Interruption (MTBSI) and Mean Time To Recovery (MTTR).

• Availability Heat Chart for Single Resource

  This report helps identify patterns of resource availability over a period of time.

• CPU Utilization Comparison for Multiple Resources

  This report shows CPU usage details for multiple systems.

• CPU Utilization for Single Resource

  This report shows CPU usage details for a specific system.

• Disk Utilization for Single Resource

  This report shows the percentage of space usage for the logical disks of a particular server, over a period of time, in an overlaid line chart, along with a table that shows finer details on logical disks usage.

• Disk Utilization Comparison for Multiple Resources

  This report shows disk usage details for multiple systems, over a period of time, in two overlaid line charts.

• Situations History

  This report shows the distribution of situation events status in a pie chart, along with more detailed information on the history of situation events listed in a table.

These reports use the following attribute groups:

• Windows agent:
  • Logical_Disk
  • Memory
  • Process
  • Server
  • System

• Linux agent:
  • CPU
  • Disk
  • Network
  • Process
  • VM_Stats

• UNIX agent:
  • Disk
  • Network
  • Process
  • System
  • Memory

• KSY SUMMARIZATION CONFIG

The next sections in this chapter contain descriptions of the reports. For each report, the following information is included:

• Name
• Description
• Purpose
• Parameters
• Tables or views used
• Output
• Usage

One of the parameters, summarization type, has the following maximum forecast periods:

• Hourly: 60 hours in the future
• Daily: 60 days in the future
• Weekly: 1 year in the future
• Monthly: 5 years in the future
• Quarterly: no limit
• Yearly: no limit

8.1. Utilization Details for Single Resource report

Name	Utilization Details for Single Resource
Description	This report shows resources utilization for a selected server: CPU utilization, disk utilization, memory utilization, network utilization. Each metric is shown on a separate chart where data for the server is overlaid. For disk utilization, only this average value for all logical disks is shown. For network utilization, total value for all network interfaces is shown. The time frame for report data can be determined in the standard way by using the Duration and Include shift periods parameters. The server can be selected from a list of available servers by using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trend computed over historical data. The report also shows the top 10 CPU utilizing processes for the selected server.
Purpose	Helps identify system performance problems related to over-utilization of key system resources. Helps identify which systems are performing poorly due to low physical memory, causing excessive paging, performing poorly due to CPU intensive tasks, or performing poorly due to other factors such as poor load balancing of applications across available systems.
Parameters	OS Type Determines the type of agent to work on, and is selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from or to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list sorted alphabetically. You can see up to 30 system names. For more than 30 names, type the name to see the filtered list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast Show Data Specifies if the chart data source should be displayed in a table or not.
Tables or views used
Output	Four line charts to show CPU, disk, memory and network usage for the selected system. Each chart has 3 lines representing average, maximum and minimum % processor time used by a server over a period along with SPC data like average, upper control limit and lower control limit. A table representing the top 10 CPU utilizing processes for the selected server .
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs) and at what times are they at most risk of violation. The same report can be used for hourly, daily, weekly, monthly, quarterly, and yearly. The ability to compare all four metrics in one chart is useful.
Drill through	On memory section title to Memory Utilization for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
	Linux Disk	KLZ_Disk	X	X	X	X	X	X
	Linux VM Stats	KLZ_VM_Stats	X	X	X	X	X	X
	Linux Network	KLZ_Network	X	X	X	X	X	X
	Linux Process	KLZ_Process	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X
	Disk	Disk	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
	Network	Network	X	X	X	X	X	X
	Process	Process	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
	Memory	NT_Memory_64	X	X	X	X	X	X
	Server	NT_Server	X	X	X	X	X	X
	Process	NT_Process_64	X	X	X	X	X	X

8.2. Utilization Details for Multiple Resources report

Name	Utilization Details for Multiple Resources
Description	This report shows resources utilization for selected servers: CPU utilization, disk utilization, memory utilization, network utilization. Each metric is shown on a separate line chart where data for all servers is overlaid. For disk utilization, only average value for all logical disks is shown. For network utilization, total value for all network interfaces is shown. The time frame for report data can be determined in standard way by using the Duration and Include shift periods parameters. The servers can be selected from a list of available servers using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trend computed over historical data.
Purpose	Helps identify and compare system performance problems related to over-utilization of key system resources. Helps identify which systems are performing poorly due to low physical memory, causing excessive paging, performing poorly due to CPU intensive tasks, or performing poorly due to other factors such as poor load balancing of applications across available systems.
Parameters	OS Type Determines the type of agent to work on and can be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and should be selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list sorted alphabetically. You are able to see up to 30 system names. For more than 30 names, type the name to filter the list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days
Parameters (Cont.)	Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used
Output	Three overlaid line charts for selected systems, with each line representing the different systems. The legend is interactive.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). Reports indicate which systems are overutilized or underutilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	On legends to Utilization Details for Single Resource. On the memory section title to Memory Utilization for Multiple Resources Comparison. On the CPU section title to CPU Utilization Comparison for Multiple Resources. On the disk section title to Disk Utilization Comparison for Multiple Resources.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
	Linux Disk	KLZ_Disk	X	X	X	X	X	X
	Linux VM Stats	KLZ_VM_Stats	X	X	X	X	X	X
	Linux Network	KLZ_Network	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X
	Disk	Disk	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
	Network	Network	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
	Memory	NT_Memory_64	X	X	X	X	X	X
	Server	NT_Server	X	X	X	X	X	X

8.3. Utilization Comparison for Single Resource report

Name	Utilization Comparison for Single Resource
Description	This report shows the comparison between CPU, disk, and memory utilization for a particular server, over a period of time, in an overlaid line chart. By clicking on the chart title, you can drill-through to see the Utilization Details for Single Resource report for the same server. The time frame for report data can be determined in the standard way by using the Duration and Include shift periods parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trend computed over historical data.
Purpose	This report helps to compare the CPU, disk, and memory utilization of a single server.
Parameters	OS Type Determines the type of agent to work on, and is selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from or to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list sorted alphabetically. You can see up to 30 system names. For more than 30 names, type the name to see the filtered list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used
Output	An overlaid line chart showing the comparison between CPU, disk, and memory utilization for a particular server, over a period of time.
Usage	The IT administrator or manager responsible for meeting the server service levels needs to receive a daily report showing which servers are at risk of violating Service Level Agreements (SLAs). The report shows the overall resource utilization of a single server. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	By clicking on the chart title, you can drill-through to see the Utilization Details for Single Resource report for the same server.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
	Linux Disk	KLZ_Disk	X	X	X	X	X	X
	Linux VM Stats	KLZ_VM_Stats	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X
	Disk	Disk	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
	Memory	NT_Memory_64	X	X	X	X	X	X

8.4. Utilization Comparison for Multiple Resources report

Name	Utilization Comparison for Multiple Resources
Description	This report shows the comparison between CPU, disk, and memory utilization for the selected servers over a period of time. By clicking on the chart title, you can drill-through to see the corresponding Utilization Details for Multiple Resources report. By clicking on the server name, you can drill-through to see the Utilization Details for Single Resource report for the selected server. By clicking on the chart data points, you can drill-through to the corresponding CPU, Disk, or Memory Utilization for Single Resource report. The time frame for report data can be determined in the standard way by using the Duration and Include shift periods parameters. The servers can be selected from a list of available servers using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trend computed over historical data.
Purpose	This report helps to compare the CPU, disk, and memory utilization for multiple servers.
Parameters	OS Type Determines the type of agent to work on, and is selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from or to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list sorted alphabetically. You can see up to 30 system names. For more than 30 names, type the name to see the filtered list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used
Output	Three line charts showing the CPU, disk, and memory utilization are displayed for each server selected. A table, which can be collapsed, corresponds to each chart.
Usage	The IT administrator or manager responsible for meeting the server service levels needs to receive a daily report showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates which systems are over-utilized or under-utilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	By clicking on the chart title, you can drill-through to see the corresponding Utilization Details for Multiple Resources report. By clicking on the server name, you can drill-through to see the Utilization Details for Single Resource report for the selected server. By clicking on the chart data points, you can drill-through to the corresponding CPU, Disk or Memory Utilization for Single Resource report.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
	Linux Disk	KLZ_Disk	X	X	X	X	X	X
	Linux VM Stats	KLZ_VM_Stats	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X
	Disk	Disk	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
	Memory	NT_Memory_64	X	X	X	X	X	X

8.5. Utilization Heat Chart for Single Resource report

Name	Utilization Heat Chart for Single Resource
Description	This report helps identify patterns of utilization of a particular system over a period of time. The first column shows dates during the selected time period and the other columns represent hours during the day. The chart can be used for showing a heat chart for CPU, memory, disk or all three in the same report. The dates have hyperlinks that allow you to drill through to the Utilization Details for Single Resource report.
Purpose	Helps identify system performance of a system or server over a period of time. Shows daily patterns for utilization.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and should be selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type is displayed in a drop-down list sorted alphabetically. You can see up to 30 system names. For more than 30 names, type the name to filter the list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days
Parameters (continued)	Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast Upper Limit for Good Status Specifies the upper limit for good status. Upper Limit for Fair Status Specifies the upper limit for fair status. Upper Limit for Warning Status Specifies the upper limit for warning status. Upper Limit for Bad Status and Lower Limit for Critical Status Specifies the upper limit for bad status and the lower limit for critical status.
Tables or views used
Output	A heat chart. The first column shows dates during the selected time period and the other columns represent 24 hours during the day starting with 0. The last column shows average value for that day. The report can be generated for CPU, disk or memory utilization. The timestamp is a hyperlink that you can use to drill through to a details report for CPU, disk, memory, network usage, top 10 processes for that particular system on the selected day. The thresholds for the colors can be specified in the parameters.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). Reports indicate which systems are overutilized or underutilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	On row level to Utilization Details for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux CPU	KLZ_CPU	X
	Linux Disk	KLZ_Disk	X
	Linux VM Stats	KLZ_VM_Stats	X
UNIX	System	System	X
	Disk	Disk	X
	UNIX Memory	UNIX_Memory	X
Windows	System	NT_System	X
	Logical Disk	NT_Logical_Disk	X
	Memory	NT_Memory_64	X

8.6. Memory Utilization for Single Resource report

Name	Memory Utilization for Single Resource
Description	This report shows memory usage details for a specific system. It uses a line chart to show the percentage of virtual, physical and swap memory usage. It also provides finer memory metrics in a table. The time frame for report data can be determined in the standard way by using the Duration and Include shift periods parameters. The server can be selected from a list of available servers by using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trends computed over historical data.
Purpose	Helps identify which systems are performing poorly due to low physical memory causing excessive paging.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and should be selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type is displayed in a drop-down list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days
Parameters (continued)	Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used
Output	A line chart showing the average usage of virtual, physical and swap memory. A table showing finer memory details.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates what is the memory health of a single system systems and if it is over-utilized or under-utilized. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux VM Stats	KLZ_Network	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
Windows	Memory	NT_Memory_64	X	X	X	X	X	X
	Paging File	NT_Paging_File	X	X	X	X	X	X

8.7. Memory Utilization for Multiple Resources Comparison report

Name	Memory Utilization for Multiple Resources Comparison
Description	This report shows memory usage details for multiple systems over a period of time. It uses three overlaid line charts for virtual, physical and swap memory. The time frame for report data can be determined in standard way by using the Duration and Include shift periods parameters. The servers can be selected from a list of available servers by using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trend computed over historical data.
Purpose	Helps identify and compare different systems behavior to identify potential memory issues due to unbalanced workload or wrong configurations. Helps identify which systems are performing poorly due to low physical memory, causing excessive paging.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and should be selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type is displayed in a drop-down list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days
Parameters (continued)	Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used
Output	Three overlaid line charts for selected systems, with each line representing the different systems. Each chart represents the behavior of a memory aspect.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates which systems are over-utilized or under-utilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	On legends to Memory Utilization for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux VM Stats	KLZ_Network	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
Windows	Memory	NT_Memory_64	X	X	X	X	X	X
	Paging File	NT_Paging_File	X	X	X	X	X	X

8.8. Top Resources Utilization report

Name	Top Resources Utilization
Description	This report shows top resources by CPU, disk and memory utilization. The stacked bars show average resource used and free (in percent) for each system over the selected report period. If the number of systems is less than 20, then a bar is shown in each row. For example, there are 20 rows in the table with charts for each system. If the number of systems is more than 20, then a bar chart is on top with the top 20 systems and the rest of the data is in the table. This is done to eliminate over-crowding of the bars in the chart.
Purpose	CPU utilization: Helps identify which systems are most overloaded and which have the least load based on the percentage of CPU utilization. Identifies which systems are over-utilized and which are under-utilized. Disk utilization: Helps identify which systems are experiencing heavy disk activity. Additionally, shows systems running low on disk space. This allows for planning the addition of hard drives or balancing of applications or data across available hard disk resources. Memory utilization: Helps identify growth in memory utilization which can lead to application and server outages. This allows for planning the increasing of paging space or the addition of physical memory.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and should be selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Number of systems The maximum number of systems to display. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Resource A drop-down list that you can use to choose which type of resource to display: All CPU Disk Memory
Tables or views used	CPU utilization General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_HV, NT_System_DV, NT_System_WV, NT_System_MV, NT_System_QV, NT_System_YV Linux agent: KLZ_CPU_HV, KLZ_CPU_DV, KLZ_CPU_WV, KLZ_CPU_MV, KLZ_CPU_QV, KLZ_CPU_YV UNIX agent: System_HV, System_DV, System_WV, System_MV, System_QV, System_YV Disk utilization Windows agent: NT_Logical_Disk_HV, NT_Logical_Disk_DV, NT_Logical_Disk_WV, NT_Logical_Disk_MV, NT_Logical_Disk_QV, NT_Logical_Disk_YV Linux agent: KLZ_Disk_HV, KLZ_Disk_DV, KLZ_Disk_WV, KLZ_Disk_MV, KLZ_Disk_QV, KLZ_Disk_YV UNIX agent: Disk_HV, Disk_DV, Disk_WV, Disk_MV, Disk_QV, Disk_YV Memory utilization Windows agent: NT_Memory_64_HV, NT_Memory_64_DV, NT_Memory_64_WV, NT_Memory_64_MV, NT_Memory_64_QV, NT_Memory_64_YV Linux agent: KLZ_VM_Stats_HV, KLZ_VM_Stats_DV, KLZ_VM_Stats_WV, KLZ_VM_Stats_MV, KLZ_VM_Stats_QV, KLZ_VM_Stats_YV UNIX agent: Unix_Memory_HV, Unix_Memory_DV, Unix_Memory_WV, Unix_Memory_MV, Unix_Memory_QV, Unix_Memory_YV
Output	A table is displayed with each row displaying a stacked bar representing one of the following for each system over the selected report period. average CPU used and free (in percent) average disk space used and free (in GB and in percent) average memory used and free (in percent) If the number of systems is less than 20, then a bar is shown in each row. For example, there are 20 rows in the table with charts for each system. If the number of systems is more than 20, then a bar chart is on top with the top 20 systems and the rest of the data is in the table. This is done to eliminate over-crowding of the bars in the chart. The charts are interactive. By clicking on the server, the hyperlink to the Utilization Details for Single Resource is provided.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). Reports indicate which systems are overutilized or underutilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	On systems axis to Utilization Details for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
	Linux Disk	KLZ_Disk	X	X	X	X	X	X
	Linux VM Stats	KLZ_VM_Stats	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X
	Disk	Disk	X	X	X	X	X	X
	UNIX Memory	UNIX_Memory	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
	Memory	NT_Memory_64	X	X	X	X	X	X

8.9. Top Situations by Status report

Name	Top Situations by Status
Description	This report shows the top 10 situations sorted by the selected status in a bar chart, along with finer details on all the top situations, listed in a table. The time frame for the report data can be determined, in the standard way, by using the Duration parameter.
Purpose	Helps to analyze the top situations generating the selected event.
Parameters	Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Status You can choose which situation status to use in order to identify the top situations. The options are displayed in a drop-down menu where a single value can be selected between the following ones: Acknowledged Closed Open Reset Stopped Unknown Aggregate Situations You can choose if the situations should be aggregated by the Managed System and Atomize attributes or not. The default value for this parameter is Yes.
Tables or views used	General: CCC Logs: STATUS_HISTORY (Raw Data)
Output	A bar chart showing the top 10 situations sorted by the selected status. A table showing finer details on all the top situations sorted by the selected status.
Usage	The IT administrator or manager responsible for meeting the server service levels needs to receive periodic reports which identify the top situations generating a specific event.
Drill through	By clicking on the situation name in the table, you can drill-through to see the corresponding Situations History report.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
CCC Logs	CCC Logs	STATUS_HISTORY

8.10. Enterprise Resources List report

Name	Enterprise Resources List
Description	This report lists all the Windows, Linux and UNIX resources in the environment. On clicking on a resource name you can drill through to see the utilization details for that resource over a period of time.
Purpose	You can use this report to see the list of OS Agents in the enterprise during a particular time.
Parameters	None
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System Linux agent: KLZ_CPU UNIX agent: System
Output	The output consists of three tables showing the resource names for Windows, Linux and UNIX. Each resource name is a hyperlink, and you can use this link to drill down to the Utilization Heat Chart for Single Resource report.
Usage	The manager responsible for meeting service levels needs to receive a weekly report of the existing systems in his environment.
Drill through	On each row in the list to Utilization Heat Chart for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X

8.11. Enterprise Daily Utilization Heat Chart report

Name	Enterprise Daily Utilization Heat Chart
Description	This report shows CPU, disk, and memory patterns for all servers, for a select operating system type, and on a particular date. The first column lists the server names. The rest of the columns show utilization data during the day hours and the last column shows the average for the server on the selected date. You can choose to see either CPU, disk, memory, or all three metrics. The date can be selected from a date prompt. The type of operating system (Linux, UNIX, Windows) can be selected from a drop down menu.
Purpose	This report helps to compare the CPU, disk and memory utilization of the machines with the same operating system in the Enterprise.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date A date prompt where you can choose the date of the report. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Attribute A drop-down list that you can use to choice what type of resource you would like to display: All (Default) CPU Disk Memory Upper Limit for Good Status Specifies the upper limit for good status. Upper Limit for Fair Status Specifies the upper limit for fair status. Upper Limit for Warning Status Specifies the upper limit for warning status. Upper Limit for Bad Status and Lower Limit for Critical Status Specifies the upper limit for bad status and the lower limit for critical status.
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_HV, NT_Logical_Disk_HV, NT_Memory_64_HV Linux agent: KLZ_CPU_HV, KLZ_Disk_HV, KLZ_VM_Stats_HV UNIX agent: System_HV, Disk_HV, Unix_Memory_HV
Output	A heat chart per attribute (CPU, Disk, Memory) is shown for all the servers with the selected operating system. The first column lists the server names. The rest of the columns show utilization data during the day hours and the last column shows the average for the server on the selected date. You can choose to see either CPU, disk, memory or all metrics.
Usage	The IT administrator or manager responsible for meeting the server service levels needs to receive a daily report showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates which systems are over-utilized or under-utilized relative to a collection of systems.
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU	X
	Linux Disk	KLZ_Disk	X
	Linux VM Stats	KLZ_VM_Stats	X
UNIX	System	System	X
	Disk	Disk	X
	UNIX Memory	UNIX_Memory	X
Windows	System	NT_System	X
	Logical Disk	NT_Logical_Disk	X
	Memory	NT_Memory_64	X

8.12. Enterprise Summary report

Name	Enterprise Summary
Description	This report shows the overall availability and utilization of all Windows, Linux and UNIX monitoring agents.
Purpose	You can use this report to compare different agent types in the environment. Note this report will run only when all 3 types of the OS agents are present in the environment.
Parameters	Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_DV, NT_Memory_64_DV, NT_Logical_Disk_DV Linux agent: KLZ_CPU_DV, KLZ_VM_Stats_DV, KLZ_Disk_DV, KLZ_System_Statistics_DV UNIX agent: System_DV, Disk_DV, Unix_Memory_DV
Output	The output consists of a bar chart showing a comparison of the different attributes CPU, Disk, Memory and Availability for Windows, UNIX, and Linux.
Usage	The IT administrator can see the health of the entire environment and compare the different OS types.
Drill through	On each bar to Top Resources by Utilization for the selected resource only. Note: This link only works for CPU, disk, and memory.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU		X
	Linux Disk	KLZ_Disk		X
	Linux VM Stats	KLZ_VM_Stats		X
	Linux System Statistics	KLZ_System_Statistics		X
UNIX	System	System		X
	Disk	Disk		X
	UNIX Memory	UNIX_Memory		X
Windows	System	NT_System		X
	Logical Disk	NT_Logical_Disk		X
	Memory	NT_Memory_64		X

8.13. Top Resources by Availability

Name	Top Resources by Availability
Description	This report displays availability of the top N systems based on System Up time over a period of time.
Purpose	Helps identify which systems have the worst (or best) availability based on the percentage of time the system is up and running. Identifies which systems are inherently unstable.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Number of systems The maximum number of systems to display. Sort by A drop-down list that you can use to choose how the top N list is sorted: % Up Time % Down Time
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_DV Linux agent: KLZ_System_Statistics_DV UNIX agent: System_DV
Output	Stacked bar chart showing average uptime and downtime for each system over the selected report period. The bar charts are interactive and let you drill through to a heat chart for system availability.
Usage	The manager responsible for meeting service levels based on server availability needs to receive a weekly report showing which servers are at risk of violating Service Level Agreements (SLAs).
Drill through	In the bar chart to Availability Heat Chart for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux System Statistics	KLZ_System_Statistics_DV		X
Windows	System	NT_System_DV		X
UNIX	System	System_DV		X

8.14. Top Resources Utilization Summary Heat Chart report

Name	Top Resources Utilization Summary Heat Chart
Description	This report shows top resources by CPU, disk, or memory utilization in a summary heat chart. By clicking on the resource name or the utilization value, you can drill through to a heat chart showing CPU, disk and memory utilization for the selected resource over the same period of time. The time frame for the report data can be determined, in the standard way, by using the Duration and Include shift periods parameters. The type of operating system (Linux, UNIX, Windows) can be selected from a drop down menu.
Purpose	This report helps to compare the top servers by CPU, disk, and memory utilization.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Sorting Attribute A drop-down list that you can use to choice what type of resource you would like to display: CPU (Default) Disk Memory Number of Systems The maximum number of servers to show in the report. Upper Limit for Good Status Specifies the upper limit for good status. Upper Limit for Fair Status Specifies the upper limit for fair status. Upper Limit for Warning Status Specifies the upper limit for warning status. Upper Limit for Bad Status and Lower Limit for Critical Status Specifies the upper limit for bad status and the lower limit for critical status.
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_HV, NT_Logical_Disk_HV, NT_Memory_64_HV Linux agent: KLZ_CPU_HV, KLZ_Disk_HV, KLZ_VM_Stats_HV UNIX agent: System_HV, Disk_HV, Unix_Memory_HV
Output	A heat chart with three columns for each server showing the CPU, disk, and memory utilization. The servers are sorted by CPU, disk, or memory utilization depending on the sorting attribute. The maximum number of servers shown is determined by the value of the Number of systems parameter.
Usage	The IT administrator or manager responsible for meeting the server service levels, needs to receive a daily report showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates which systems are over-utilized or under-utilized relative to a collection of systems.
Drill through	By clicking on the resource name or the utilization value, you can drill through to a heat chart showing CPU, disk, and memory utilization for the selected resource over the same period of time.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU	X
	Linux Disk	KLZ_Disk	X
	Linux VM Stats	KLZ_VM_Stats	X
UNIX	System	System	X
	Disk	Disk	X
	UNIX Memory	UNIX_Memory	X
Windows	System	NT_System	X
	Logical Disk	NT_Logical_Disk	X
	Memory	NT_Memory_64	X

8.15. Top Resources by Availability (MTTR/MTBSI)

Name	Top Resources by Availability (MTTR/MTBSI)
Description	This report displays availability trending of the top N systems based on the Mean Time Before System Interruption (MTBSI) and Mean Time To Recovery (MTTR).
Purpose	Help identify which systems have the worst (or best) availability based on the amount of time the system is up/running and the amount of time it takes to bring a system back online following an outage. Identifies which systems are inherently unstable.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Number of systems The maximum number of systems to display. Sort by A drop-down list that you can use to choose how the top N list is sorted: Mean Time To Recovery (Default) Mean Time Before System Interruption
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_DV Linux agent: KLZ_System_Statistics_DV UNIX agent: System_DV
Output	Stacked bar chart showing MTBSI and MTTR for each resource. An ordered table showing additional data .
Usage	The manager responsible for meeting service levels based on server availability needs to receive a weekly report showing which servers are at risk of violating Service Level Agreements (SLAs).
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux System Statistics	KLZ_System_Statistics_DV		X
Windows	System	NT_System_DV		X
UNIX	System	System_DV		X

8.16. Resource Availability Comparison

Name	Resource Availability Comparison
Description	This report shows availability comparison between two or more servers.
Purpose	Helps compare multiple systems based on availability.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_DV Linux agent: KLZ_System_Statistics_DV UNIX agent: System_DV
Output	Pie charts showing % Uptime and % Downtime for selected servers. A table showing the same availability information plus details on the number of days each system is available and unavailable.
Usage	The manager responsible for meeting service levels based on server availability needs to receive a weekly report showing which servers are at risk of violating Service Level Agreements (SLAs).
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux System Statistics	KLZ_System_Statistics_DV		X
Windows	System	NT_System_DV		X
UNIX	System	System_DV		X

8.17. Availability Heat Chart for Single Resource

Name	Availability Heat Chart for Single Resource
Description	This report helps identify patterns of resource availability over a period of time.
Purpose	Helps identify system performance of a system or server over a period of time. Shows daily patterns for availability or unavailability.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Attribute A drop-down list that you can use to specify which pattern to display: % Up Time (Default) % Down Time Upper Limit for Good Status Specifies the upper limit for good status. Upper Limit for Fair Status Specifies the upper limit for fair status. Upper Limit for Warning Status Specifies the upper limit for warning status. Upper Limit for Bad Status and Lower Limit for Critical Status Specifies the upper limit for bad status and the lower limit for critical status.
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_HV Linux agent: KLZ_System_Statistics_HV UNIX agent: System_DV
Output	A heat chart. The first column shows dates during the selected time period and the other columns represent 24 hours during the day starting with 0. The report can also be reversed to show system downtime instead of uptime based on parameter selection. The thresholds for the colors can be specified in the parameters.
Usage	The IT administrator or manager can use this report to identify patterns of availability for a particular system over a period of time.
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG_DV		X
Linux	Linux System Statistics	KLZ_System_Statistics_HV	X
Windows	System	NT_System_HV	X
UNIX	System	System_DV	X

8.18. CPU Utilization Comparison for Multiple Resources

Name	CPU Utilization Comparison for Multiple Resources
Description	This report shows CPU usage details for multiple systems, over a period of time, in three overlaid line charts for busy, user and system CPU usage on Linux and UNIX systems, and for total processor, user and privileged CPU usage on Windows systems. The time frame for the report data can be determined, in the standard way, by using the Duration and include the shift period parameters. The servers can be selected from a list of available servers using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on the linear trend computed over historical data.
Purpose	Helps to compare different system CPU usage behaviors to identify excessive CPU utilization, unbalanced workloads or wrong configurations.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or select from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only
Parameters (Continued)	Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_HV, NT_System_DV, NT_System_WV, NT_System_MV, NT_System_QV,NT_System_YV Linux agent: KLZ_CPU_HV, KLZ_CPU_DV, KLZ_CPU_WV, KLZ_CPU_MV, KLZ_CPU_QV,KLZ_CPU_YV UNIX agent: System_HV, System_DV, System_WV, System_MV, System_QV, System_YV
Output	Three overlaid line charts for selected systems, with each line representing the different systems. Each chart represents the behavior of a CPU aspect. A table, which can be collapsed, corresponds to each chart.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates which systems are over-utilized or under-utilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	On legends to CPU Utilization for Single Resource.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X

8.19. CPU Utilization for Single Resource

Name	CPU Utilization for Single Resource
Description	This report shows CPU usage details for a specific system. A line chart is used to show the busy and idle CPU time trends. It also provides finer CPU metrics in a table. The time frame for the report data can be determined, in the standard way, by using the Duration and include the shift period parameters. The servers can be selected from a list of available servers using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on the linear trend computed over historical data.
Purpose	Helps identify which systems are experiencing excessive CPU usage.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or select from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only
Parameters (Continued)	Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_System_HV, NT_System_DV, NT_System_WV, NT_System_MV, NT_System_QV,NT_System_YV Linux agent: KLZ_CPU_HV, KLZ_CPU_DV, KLZ_CPU_WV, KLZ_CPU_MV, KLZ_CPU_QV,KLZ_CPU_YV UNIX agent: System_HV, System_DV, System_WV, System_MV, System_QV, System_YV
Output	A line chart showing busy and idle CPU time trends.
Usage	The IT administrator or manager responsible for meeting service levels based on server performance needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates what is the CPU health of a single system systems and if it is over-utilized or under-utilized. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly.
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux CPU	KLZ_CPU	X	X	X	X	X	X
Windows	System	NT_System	X	X	X	X	X	X
UNIX	System	System	X	X	X	X	X	X

8.20. Disk Utilization for Single Resource

Name	Disk Utilization for Single Resource
Description	This report shows the percentage of space usage for the logical disks of a particular server, over a period of time, in an overlaid line chart, along with a table that shows finer details on logical disks usage. The time frame for the report data can be determined, in the standard way, by using the Duration and include the shift period parameters. The server can be selected from a list of available servers by using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on linear trend computed over historical data.
Purpose	Helps to analyze the disk utilization details of a specific machine.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or select from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only
Parameters (Continued)	Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Include remote file systems For Linux and UNIX systems only, it is possible to include remote file systems, such as NFS file systems, in the computation of the total average space usage percent and the total average space available in MB. Include pseudo file systems For Linux and UNIX systems only, it is possible to include the pseudo file systems, such as the proc file system, in the computation of the total average space usage percent and the total average space available in MB. Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_Logical_Disk_HV, NT_Logical_Disk_DV, NT_Logical_Disk_WV, NT_Logical_Disk_MV, NT_Logical_Disk_QV, NT_Logical_Disk_YV Linux agent: KLZ_Disk_HV, KLZ_Disk_DV, KLZ_Disk_WV, KLZ_Disk_MV, KLZ_Disk_QV, KLZ_Disk_YV UNIX agent: Disk_HV, Disk_DV, Disk_WV, Disk_MV, Disk_QV, Disk_YV
Output	A line chart showing the average percent space usage plotted against time. A table showing finer disk utilization details.
Usage	The IT administrator or manager responsible for meeting the server service levels, needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates what is the disk utilization health of a single system and which file systems are over-utilized or under-utilized. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly. Note that the percent of disk usage in the report is calculated each time at run time. This approach is different from the approach used in the PureApplication System Monitoring Portal Server workspace where the same metrics are instead taken directly from the % Used attribute of the Logical Disk attribute group. Due to the different units used and some rounding applied during the multiple calculations of average, the two values might vary slightly.
Drill through	None.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux DISK	KLZ_DISK	X	X	X	X	X	X
Windows	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
UNIX	Disk	Disk	X	X	X	X	X	X

8.21. Disk Utilization Comparison for Multiple Resources

Name	Disk Utilization Comparison for Multiple Resources
Description	This report shows disk usage details for multiple systems, over a period of time, in two overlaid line charts. The first overlaid line chart shows the total average space usage percent plotted against time. For example, the sum of the average space usage, over a period of time, for all the file systems of a single machine, in respect to the total size of all the file systems. A linear trending feature is also provided for the total average space usage percent and it is based on the selected forecast period. The second line chart shows the total space available in megabytes plotted against time. For example, the sum of all the average space available, over a period of time, for all the file systems of a machine. By clicking on the server names in the charts legends, you can drill-through to see the corresponding Disk Utilization for Single Resource report. The time frame for the report data can be determined, in the standard way, by using the Duration and Include the shift period parameters. The servers can be selected from a list of available servers using the OS Type and Servers parameters. The forecasts can also be shown for the given period. If set, all the charts show data that ends at that date, and missing samples are determined based on the linear trend computed over historical data.
Purpose	Helps to compare different file system usage behaviors to identify excessive file system utilization.
Parameters	OS Type Determines the type of agent to work on and should be selected from the drop-down list with the following items: Linux UNIX Windows Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or select from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Summarization Type Determined by Summarization and Pruning and is selected from the drop-down list with the following items: Daily (Default) Hourly Weekly Monthly Quarterly Yearly Servers The server or system names for the selected OS Type are displayed in a drop-down list. Include shift periods A drop-down list that you can use to select the shift periods to be included. The Peak/Off-Peak Hours period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Shifts (Default) Peak Hours Only Off - Peak Hours Only
Parameters (Continued)	Include vacation periods A drop-down list that you can use to include or exclude vacation days. The Vacation period terms refer to definitions contained in Summarization and Pruning. The list contains the following options: All Days (Default) Work days Vacation days Include remote file systems For Linux and UNIX systems only, it is possible to include remote file systems, such as NFS file systems, in the computation of the total average space usage percent and the total average space available in MB. Include pseudo file systems For Linux and UNIX systems only, it is possible to the pseudo file systems, such as the proc file system, in the computation of the total average space usage percent and the total average space available in MB. Forecast Period If forecast is enabled, specifies the forecast period. Forecast Specifies whether forecast is enabled using a drop-down list. The list contains the following options: Use forecast Do not use the forecast
Tables or views used	General: KSY_SUMMARIZATION_CONFIG_DV Windows agent: NT_Logical_Disk_HV, NT_Logical_Disk_DV, NT_Logical_Disk_WV, NT_Logical_Disk_MV, NT_Logical_Disk_QV, NT_Logical_Disk_YV Linux agent: KLZ_Disk_HV, KLZ_Disk_DV, KLZ_Disk_WV, KLZ_Disk_MV, KLZ_Disk_QV, KLZ_Disk_YV UNIX agent: Disk_HV, Disk_DV, Disk_WV, Disk_MV, Disk_QV, Disk_YV
Output	Two overlaid line charts are shown for the selected systems, with one line for each selected system that has some historical data stored in the Tivoli Data Warehouse. Each chart represents the behavior of a different file system aspect. A table, which can be collapsed, corresponds to each chart.
Usage	The IT administrator or manager responsible for meeting the server service levels, needs to receive periodic reports showing which servers are at risk of violating Service Level Agreements (SLAs). The report indicates which systems are over-utilized or under-utilized relative to a collection of systems. The report can be run hourly, daily, weekly, monthly, quarterly, and yearly. Note that the percent of disk usage in the report is calculated each time at run time. This approach is different from the approach used in the Tivoli Enterprise Portal Server workspace where the same metrics are instead taken directly from the % Used attribute of the Logical Disk attribute group. Due to the different units used and some rounding applied during the multiple calculations of average, the two values might vary slightly.
Drill through	By clicking on one of the system names on the legends, it is possible to drill through the corresponding Disk Utilization for Single Resource report.

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
All	KSY SUMMARIZATION CONFIG	KSY_SUMMARIZATION_CONFIG		X
Linux	Linux Disk	KLZ_DISK	X	X	X	X	X	X
Windows	Logical Disk	NT_Logical_Disk	X	X	X	X	X	X
UNIX	Disk	Disk	X	X	X	X	X	X

8.22. Situations History report

Name	Situations History
Description	This report shows the distribution of situation events status in a pie chart, along with more detailed information on the history of situation events listed in a table. The time frame for the report data can be determined by using Duration.
Purpose	You can use this report to analyze the history of the PureApplication System Monitoring Server situation events.
Parameters	Date Range Determines the range of data shown on a report. Provide the value as two border dates (from and to) or selected from the drop-down list with the following options: All Date Range (below) Today Yesterday Last 7 days Last 30 days Last 90 days Last 355 days Current week Current month Current Year to Date Last week Last month Last Year Status You can apply a filter on the situations event data set by specifying the status in a multi-select value prompt where one or multiple status value can be selected from the following: Acknowledged Closed Open Reset Stopped Unknown Managed System Filter You can apply a filter on the situations events data set by specifying a regular expression that the managed system attribute should follow. This filter can contain the two following wildcard characters: the percent sign (%), which matches zero or more characters, and the underscore sign (_), which matches a single character. The default value for the regular expression is the percent sign, and, by default, all the managed system are selected. The escape character for the underscore and percent signs is the backslash character (\). The empty string for the Situation Name Filter can be specified through two single quotation marks (' '). Situation Name Filter You can apply a filter on the situations events data set by specifying a regular expression that the situation name attribute should follow. This filter can contain the two following wildcard characters: the percent sign (%), which matches zero or more characters, and the underscore sign (_), which matches a single character. The default value for the regular expression is the percent sign, and, by default, all the situation names are selected. The escape character for the underscore and percent signs is the backslash character (\).
Tables or views used	General: CCC Logs: STATUS_HISTORY (Raw Data)
Output	A pie chart showing the distribution of situation events status. A table showing more detailed information on situation status history.
Usage	The IT administrator or manager responsible for meeting the server service levels, needs to receive periodic reports showing which is the situation event status distribution.
Drill through	None

The following table includes information about the historical collection configuration:

OS Type	Attribute Group	Table	Summarization
			H	D	W	M	Q	Y
CCC Logs	CCC Logs	STATUS_HISTORY

8.23. Creating custom queries and reports

You can create your own queries and reports using the models and reports that have been documented in the subsections above by completing the following steps:

1. Read the instructions for enabling historical collection found in the PureApplication System Monitoring Portal User's Guide.
2. Check in Table 1 below for the list of the attribute groups that are supported by the data model and are found in the Tivoli Data Warehouse database.
3. Enable historical collection for these supported attribute groups and configure the summarization settings. All of the summarization settings are supported.
4. After the database is populated, use the model leveraging in Query Studio and Report Studio.

Attributes groups supported by the data model

Agent	Attribute groups	Tables
Linux	Linux CPU Averages	KLZ_CPU_Averages
	Linux CPU	KLZ_CPU
	Linux Disk	KLZ_Disk
	Linux Network	KLZ_Network
	Linux Process	KLZ_Process
	Linux VM Stats	KLZ_VM_Stats
	Linux Disk IO	KLZ_Disk_IO
	Linux Disk Usage Trends	KLZ_Disk_Usage_Trends
	Linux IO Ext	KLZ_IO_Ext
	Linux NFS Statistics	KLZ_NFS_Statistics
	Linux Process User Info	KLZ_Process_User_Info
	Linux RPC Statistics	KLZ_RPC_Statistics
	Linux Sockets Detail	KLZ_Sockets_Detail
	Linux Sockets Status	KLZ_Sockets_Status
	Linux Swap Rate	KLZ_Swap_Rate
	Linux System Statistics	KLZ_System_Statistics
	Linux User Login	KLZ_User_Login
UNIX	Disk	Disk
	Network	Network
	Process	Process
	Unix Memory	Unix_Memory
	System	System
	Disk Performance	Disk_Performance
	NFS and RPC Statistics	N_F_S_and_R_P_C_Statistics
	SMP CPU	SMP_CPU
	Solaris Zones	Solaris_Zones
	User	User
Windows	Logical Disk Hourly	NT_Logical_Disk
	Memory Hourly	NT_Memory_64
	Network Interface Hourly	NT_Network_Interface
	Process Hourly	NT_Process_64
	Server Hourly	NT_Server
	System Hourly	NT_Process_64
	ICMP Statistics Hourly	ICMP_Statistics
	IP Statistics Hourly	IP_Statistics
	Cache Hourly	NT_Cache
	Device Dependencies Hourly	NT_Device_Dependencies
	Devices Hourly	NT_Devices
	Event Log Hourly	NT_Event_Log
	Monitored Logs Report Hourly	NT_Monitored_Logs_Report
	Network Port Hourly	NT_Network_Port
	Objects Hourly	NT_Objects
	Paging File Hourly	NT_Paging_File
	Physical Disk Hourly	NT_Physical_Disk
	Printer Hourly	NT_Printer
	Processor Hourly	NT_Processor
	Processor Summary Hourly	NT_Processor_Summary
	Redirector Hourly	NT_Redirector
	Server Work Queues Hourly	NT_Server_Work_Queues_64
	Service Dependencies Hourly	NT_Service_Dependencies
	Services Hourly	NT_Services
	Thread Hourly	NT_Thread
	Print Queue Hourly	Print_Queue
	Process IO Hourly	Process_IO
	TCP Statistics Hourly	TCP_Statistics
	UDP Statistics Hourly	UDP_Statistics

Note: There is a subset of tables that are visible in the model, but cannot be used in custom queries and reports. These tables are contained in the following folders:

• Forecast Hourly
• Forecast Daily
• Forecast Weekly
• Forecast Monthly
• Forecast Quarterly
• Forecast Yearly

Troubleshooting

This appendix provides agent troubleshooting information. See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information, including information on how to set up tracing for this agent. Also see Support information for other problem-solving options.

Note: You can resolve some problems by ensuring that your system matches the system requirements listed in Requirements for the monitoring agent.

9.1. Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing with this product, gather the information.

Information to gather before contacting IBM Software Support

Information type	Description
Log files	Collect trace log files from failing systems. Most logs are located in a logs subdirectory on the host computer. See the User's Guide for general information about the IBM PureApplication Monitoring environment.
Linux information	Version number and patch level
Operating system	Operating system version number and patch level
Messages	Messages and other information displayed on the screen
Version numbers for IBM PureApplication Monitoring	Version number of the following members of the monitoring environment: IBM PureApplication Monitoring. Also provide the patch level, if available. Monitoring Agent for Linux
Screen captures	Screen captures of incorrect output, if any.
(UNIX only) Core dump files	If the system stops on UNIX systems, collect the core dump file from install_dir/bin directory, where install_dir is the directory where you installed the monitoring agent.

9.2. Built-in troubleshooting features

The primary troubleshooting feature in the IBM PureApplication Monitoring: Linux OS Agent is logging. Logging refers to the text messages and trace data generated by the IBM PureApplication Monitoring: Linux OS Agent. Messages and trace data are sent to a file.

Trace data captures transient information about the current operating environment when a component or application fails to operate as designed. IBM Software Support personnel use the captured trace information to determine the source of an error or unexpected condition.

9.3. Problem classification

The following types of problems might occur with the IBM PureApplication Monitoring: Linux OS Agent:

• Installation and configuration
• General usage and operation
• Display of monitoring data
• Take Action commands

This chapter provides symptom descriptions and detailed workarounds for these problems, as well as describing the logging capabilities of the monitoring agent. See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.

9.4. Trace logging

Trace logs capture information about the operating environment when component software fails to operate as intended. The principal log type is the RAS (Reliability, Availability, and Serviceability) trace log. These logs are in the English language only. The RAS trace log mechanism is available for all components of IBM PureApplication Monitoring. Most logs are located in a logs subdirectory on the host computer. See the following sections to learn how to configure and use trace logging:

Note: The documentation refers to the RAS facility in IBM PureApplication Monitoring as "RAS1".

IBM Software Support uses the information captured by trace logging to trace a problem to its source or to determine why an error occurred. The default configuration for trace logging, such as whether trace logging is enabled or disabled and trace level, depends on the source of the trace logging. Trace logging is always enabled.

Log file management is described in the following table:

Log file management on UNIX compared to log file management on Windows

Location of logs	Description
On a Windows monitoring server On a Windows computer where the monitoring agent is running On a UNIX or Linux computer where the monitoring agent is running	On Windows, the log file is overwritten each time the component starts. There is no automated method to archive previous RAS1 log files. Note: To prevent the log files from consuming too much disk space, you can stop and start the component. This action automatically creates a new log file. Save a backup of log files if your company policy requires archiving of log files.
On a UNIX or Linux monitoring server On a UNIX or Linux computer where the monitoring agent is running	On UNIX or Linux systems, because of the use of the &Timestamp; variable in the log file names, multiple RAS1 logs are normally stored the logs subdirectory. The file name for a trace log is a copy of a related file that includes the process ID of the agent. The two files have the same timestamp as in these examples from a computer with a host name f50pa2b. The 1112097194 part of the name is the timestamp: f50pa2b_lz_1112097194.log f50pa2b_lz_1112097194.pid60420 where lz is the unique, two-character code for Monitoring Agent for Linux OS.

Note: When you communicate with IBM Software Support, you must capture and send the RAS1 log that matches any problem occurrence that you report.

9.4.1. Principal trace log files

Locations, file names, and descriptions of trace logs that can help determine the source of problems with agents.

Trace log files for troubleshooting agents

System where log is located	File name and path	Description
On the computer that hosts the monitoring agent	The hostname_lz_instance.log file is located in the install_dir/logs path.	Traces activity of the monitoring agent.
	The *.LG0 file is located in the following subdirectory of the install_dir path: /logs.	Shows whether agent was able to connect to the monitoring server. Shows which situations are started and stopped, and shows other events while the agent is running. A new version of this file is generated every time the agent is restarted. IBM PureApplication Monitoring generates one backup copy of the *.LG0 file with the tag .LG1. View .LG1 to learn the following details regarding the previous monitoring session: Status of connectivity with the monitoring server. Situations that were running. The success or failure status of Take Action commands.
	The take_action_name.log file (where take_action_name is the name of the Take Action command) is located in the /logs subdirectory of the install_dir path.	Traces activity each time a Take Action command runs. For example, when a hypothetical start_command Take Action command runs, IBM PureApplication Monitoring would generate a start_command.log file.
On the PureApplication Monitoring Server	The candle_installation.log file in the install_dir/logs path.	Provides details about products that are installed. Note: Trace logging is enabled by default. A configuration step is not required to enable this tracing.
	The Warehouse_Configuration.log file is located in the following path on Windows: install_dir\InstallITM.	Provides details about the configuration of data warehousing for historical reporting.
	The name of the RAS log file is as follows: On Windows: install_dir\logs\hostname_ms_timestamp.log On UNIX or Linux: hostname_ms_timestamp.log and hostname_ms_timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number.	Traces activity on the monitoring server.
On the PureApplication Portal Server	The name of the RAS log file is as follows: On Windows: install_dir\logs\hostname_cq_timestamp.log On UNIX or Linux: hostname_cq_timestamp.log and hostname_cq_timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number.	Traces activity on the portal server.
	The TEPS_ODBC.log file is located in the following path on Windows: install_dir\InstallITM.	When you enable historical reporting, this log file traces the status of the warehouse proxy agent.
Definitions of variables: timestamp is timestamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm install_dir represents the directory path where you installed the IBM PureApplication Monitoring component. install_dir can represent a path on the computer that host the monitoring system, the monitoring agent, or the portal. instance refers to the name of the database instance that you are monitoring. hostname refers to the name of the computer on which the IBM PureApplication Monitoring component runs.

See the IBM PureApplication System Monitoring Server Installation and Setup Guide for more information on the complete set of trace logs that are maintained on the monitoring server.

9.4.1.1. Examples: using trace logs

Typically IBM Software Support applies specialized knowledge to analyze trace logs to determine the source of problems. However, you can open trace logs in a text editor to learn some basic facts about the IBM PureApplication Monitoring environment.

Example one

This excerpt shows the typical log for a failed connection between a monitoring agent and a monitoring server with the host name server1a:

(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,
    "location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to     broker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable
    to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>

Example two

The following excerpts from the trace log for the monitoring server show the status of an agent, identified here as "Remote node." The name of the computer where the agent is running is SERVER5B:

(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:LZ is ON-LINE.
. . .
(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:KLZ is OFF-LINE.

Key points regarding the preceding excerpt:

• The monitoring server appends the LZ product code to the server name to form a unique name (SERVER5B:LZ) for this instance of Monitoring Agent for Linux OS. This unique name enables you to distinguish multiple monitoring products that might be running on SERVER5B.
• The log shows when the agent started (ON-LINE) and later stopped (OFF-LINE) in the environment.
• For the sake of brevity an ellipsis (...) represents the series of trace log entries that were generated while the agent was running.
• Between the ON-LINE and OFF-LINE log entries, the agent was communicating with the monitoring server.
• The ON-LINE and OFF-LINE log entries are always available in the trace log.

9.4.2. Setting RAS trace parameters

9.4.2.1. Objective

Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and modules.

9.4.2.2. Background Information

Monitoring Agent for Linux OS uses RAS1 tracing and generates logs. The default RAS1 trace level is ERROR.

9.4.2.3. Before you begin

When you are troubleshooting, follow these guidelines to ensure that you capture and analyze the correct log files: Because of the use of the &Timestamp; variable in the log file names on UNIX or Linux systems, there are typically multiple RAS1 logs in the logs subdirectory. When you forward log files to IBM Software Support, you must send the RAS1 log that matches the problem occurrence that the log files are reporting.

9.4.2.4. After you finish

On UNIX or Linux, periodically prune the trace logs in the logs subdirectory so that there is available disk space for new logging.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.

9.4.2.5. Procedure

Specify RAS1 trace options in the install_dir/config/lz.ini file. The basic format for setting tracing options is as follows:

KBB_RAS1=ERROR (UNIT:klz options) 

Use one of the following methods to modify trace options:

• Manually edit the configuration file to set trace logging
  1. Open the trace options file: /install_dir/config/lz.ini.
  2. Edit the line that begins with KBB_RAS1= to set trace logging preferences.

     For example, if you want detailed trace logging, set the Maximum Tracing option:

     export KBB_RAS1='ERROR (UNIT:klz ALL) (UNIT:kra ALL)'
     

  3. Restart the monitoring agent so that your changes take effect.

9.5. Problems and workarounds

The following sections provide symptoms and workarounds for problems that might occur with the Monitoring Agent for Linux:

9.5.1. Installation and configuration troubleshooting

This section provides tables that show solutions for installation, configuration, and uninstallation problems.

Problems and solutions for installation and configuration

Problem	Solution
(UNIX only) During a command-line installation, you choose to install a component that is already installed, and you see the following warning: WARNING - you are about to install the SAME version of "component_name" where component_name is the name of the component that you are attempting to install. Note: This problem affects UNIX command-line installations. If you monitor only Windows environments, you see this problem if you choose to install a product component (for example, a monitoring server) on UNIX.	You must exit and restart the installation process. You cannot return to the list where you selected components to install. When you run the installer again, do not attempt to install any component that is already installed.
A problem can arise when you install and configure a new monitoring agent to a computer where other agents are running as described in this example: Agents are running on computer and communicating with a PureApplication Monitoring Server, called TEMS1. You install a new agent on the same computer and you want this agent to communicate with a different monitoring server, called TEMS2. When you configure the new agent to communicate with TEMS2, all the existing agents are re-configured to communicate with TEMS2.	You must reconfigure the previously existing agents to restore their communication connection with TEMS1. For example, you can right-click the row for a specific agent in the Manage Tivoli Enterprise Monitoring Services, and select Reconfigure. See the Installation and Setup Guide for more information on reconfiguration.
Diagnosing problems with product browse settings (Windows systems only).	When you have problems with browse settings, perform the following steps: Click on Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring Services window is displayed. Right-click the Windows agent and select Browse Settings. A text window is displayed. Click Save As and save the information in the text file. If requested, you can forward this file to IBM Software Support for analysis.
The Warehouse Proxy Agent fails to connect to the database.	On a 64-bit system, use the Warehouse Proxy Agent 64-bit image. Create the ODBC data source name with the 64bit ODBC configuration application.
A message similar to "Unable to find running CMS on CT_CMSLIST" in the log file is displayed.	If a message similar to "Unable to find running CMS on CT_CMSLIST" is displayed in the Log file, the agent is not able to connect to the monitoring server. Confirm the following points: Do multiple network interface cards (NICs) exist on the system? If multiple NICs exist on the system, find out which one is configured for the monitoring server. Ensure that you specify the correct host name and port settings for communication in the IBM PureApplication Monitoring environment.
The system is experiencing high CPU usage.	Agent process: View the memory usage of the KHDCMA process. If CPU usage seems to be excessive, recycle the monitoring agent. Network Cards: The network card configurations can decrease the performance of a system. Each of the stream of packets that a network card receives (assuming it is a broadcast or destined for the under-performing system) must generate a CPU interrupt and transfer the data through the I/O bus. If the network card in question is a bus-mastering card, work can be off-loaded and a data transfer between memory and the network card can continue without using CPU processing power. Bus-mastering cards are generally 32-bit and are based on PCI or EISA bus architectures.

General problems and solutions for uninstallation

Problem	Solution
On Windows, uninstallation of IBM Tivoli Monitoring fails to uninstall the entire environment.	Be sure that you follow the general uninstallation process described in the IBM Tivoli Monitoring Installation and Setup Guide: Remove Tivoli Enterprise Monitoring Server Application support by completing the following steps: Use Manage Tivoli Enterprise Monitoring Services. Select Tivoli Enterprise Monitoring Server. Right-click and select advanced . Select Remove TEMS application support. Select the agent to remove its application support. Uninstall monitoring agents first, as in the following examples: Uninstall a single monitoring agent for a specific database. -OR- Uninstall all instances of a monitoring product, such as IBM Tivoli Monitoring for Databases. Uninstall IBM Tivoli Monitoring.
The way to remove inactive managed systems (systems whose status is OFFLINE) from the Navigator tree in the portal is not obvious.	Use the following steps to remove, but not uninstall, an offline managed system from the Navigation tree: Click the Enterprise icon in the Navigator tree. Right-click Workspace > Managed System Status. Right-click the offline managed system, and select Clear offline entry. If you also want to uninstall the monitoring agent, use the procedure described in the IBM Tivoli Monitoring Installation and Setup Guide.

9.5.1.1. Agent upgrade and restart using non-root

The monitoring agent can run by using a non-root user ID on UNIX and Linux systems. This can be done by running the itmcmd agent start command while logged in as a non-root user, and this can be done remotely by deploying the agent by using the Run As option on the GUI or by using the _UNIX_STARTUP_.Username option on the tacmd addSystem command line. If the agent is running by using a non-root user ID, and then the agent is upgraded, restarted remotely, restarted as a result of a system reboot, or the itmcmd agent start is run by using the root user ID, then the monitoring agent subsequently runs as the root user. To confirm the user ID that the monitoring agent is by using, run the following command:

itm_install/bin/cinfo -r

If the agent is using root, and that is not the desired user ID, then use the following steps to restart the agent:

1. Log in as root.
2. Run the itmcmd agent stop command.
3. Log in (or 'su') to the user ID that you want the agent to run as.
4. Run the itmcmd agent start command.

If the agent was running as root because of a system reboot, then edit the startup file by using the following steps so that the appropriate user ID is used the next time the system is rebooted:

1. Look at install_dir/registry/AutoStart, and get NUM.
2. Edit the autostart for your operating system:

   The location of the startup file is platform dependent as follows:

   • AIX: /etc/rc.itmNUM
   • HP-UX: /sbin/init.d/ITMAgentsNUM
   • Linux: /etc/init.d/ITMAgentsNUM
   • Solaris: /etc/init.d/ITMAgentsNUM

3. Add entries for your operating system by using the following command:

   /usr/bin/su - instancename 
   -c "install_dir/bin/itmcmd agent 
   -h install_dir 
   -o instancename 
   start product_code"
   

   Where:

   instancename

   Name of the instance

   install_dir

   Name of the directory

   product_code

   2-character product code for the agent, for example, lz for the Monitoring Agent for Linux OS

   
   Examples:

   • For AIX, add entries with the following format:

     su - USER -c " /opt/IBM/ITM/bin/itmcmd agent 
     -o INSTANCE start lz.
     

     Where:

     USER

     Name of the user

     INSTANCE

     Name of the instance

   • For Linux, HP_UX, and Solaris, add entries with the following format:

     /bin/su - USER -c " /opt/IBM/ITM/bin/itmcmd agent 
     -o INSTANCE start lz >/dev/null 2>&1"
     

     Where:

     USER

     Name of the user

     INSTANCE

     Name of the instance

4. Repeat Steps 1 through 3 for all occurrences of stop.
5. Save the file.

9.5.1.2. Unique names for monitoring components

IBM PureApplication Monitoring might not be able to generate a unique name for monitoring components due to the truncation of names that the product automatically generates.

If the agent supports multi-instances, IBM PureApplication Monitoring automatically creates a name for each monitoring component by concatenating the subsystem name, host name, and product code separated by colons (subsystem_name:hostname:KHD).

Note: When you monitor a multinode system, such as a database, IBM PureApplication Monitoring adds a subsystem name to the concatenated name, typically a database instance name. The length of the name that IBM PureApplication Monitoring generates is limited to 32 characters. Truncation can result in multiple components having the same 32-character name. If this problem happens, shorten the hostname portion of the name as follows:

1. Open the configuration file for the monitoring agent, which is located in the following path:
   • On Windows: &install_dir;\tmaitm6\Kproduct_codeCMA.INI. For example, the product code for the Monitoring Agent for Windows OS is NT and the file name is KNTCMA.INI.
   • On UNIX and Linux: itm_home/config/product_code.ini and product_code.config. For example, the file names for the Monitoring Agent for UNIX OS is ux.ini and ux.config.

2. Find the line the begins with CTIRA_HOSTNAME=.
3. Type a new name for host name that is a unique, shorter name for the host computer. The final concatenated name including the subsystem name, new host name, and KHD, cannot be longer than 32 characters.

   Note: You must ensure that the resulting name is unique with respect to any existing monitoring component that was previously registered with the PureApplication Monitoring Server.

4. Save the file.
5. Restart the agent.

9.5.2. Agent troubleshooting

This section lists problems that might occur with agents.

This appendix provides agent-specific troubleshooting information. See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.

Agent problems and solutions

Problem	Solution
Log data accumulates too rapidly.	Check the RAS trace option settings, which are described in IBM Tivoli Monitoring Troubleshooting Guide. The trace options settings that you can set on the KBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.
The Warehouse Proxy Agent fails.	If the Warehouse Proxy Agent fails, this might be due to the port numbers not being the same every time you restart the Warehouse Proxy Agent. See the IBM Tivoli Monitoring Installation and Setup Guide for instructions on how to setup a static port number for the Warehouse Proxy Agent.
The Warehouse Proxy Agent leaks memory when either the User ID or password is incorrect.	A memory leak can occur if the Warehouse Proxy Agent User ID or password is incorrect, and this leak is most probably occurring in the ODBC layer.
The Monitoring Agent for Linux workspaces and navigator items are not visible in the Tivoli Enterprise Portal.	The application support files need to be installed for the Tivoli Enterprise Portal Server, browser Tivoli Enterprise Portal, and desktop Tivoli Enterprise Portal. This problem can occur in IBM Tivoli Monitoring upgrade environments where Monitoring Agent for Linux is upgraded from a version that did not have the self monitoring capabilities and the support files where not selected in the upgrade.
When using the F1 key or selecting Help --> Contents and Index, you receive a message in your Microsoft Internet Explorer browser which states, "It seems javascript is disabled in your browser, please enable it and reload again, or click here to view without javascript." If you select 'here', the Tivoli Enterprise Portal V6.1 Help is displayed, but the agent help is not.	Ensure that the local site is added to the browser's trusted site and then enable the javascript.
If you want to receive multiple trace logs for separate invocations of the same Take Action command, leaving this setting on permanently fills the available disk space.	Do not leave this setting permanently. By doing so, you create a new log file for each invocation of the Take Action command and ALL of them are left on the agent system.
Online Help Search cannot find any agent online help.	To search the online help for this agent the user must use the IBM Eclipse help search function and not the search function in the web based help online help. To use the search function for this agent's online help, ensure that you have selected the IBM Eclipse help server check box when installing the Tivoli Enterprise Portal Server. The 'Searching Agent Help' topic in this agent's online help contains a link to the Eclipse help, where the search function is enabled. From the Table of Contents in the left-hand pane of the help, select the 'Searching Agent Help' topic to find the link to the Eclipse help in the right-hand pane.

9.5.3. PureApplication Monitoring Portal troubleshooting

PureApplication Monitoring Portal problems and solutions

Problem	Solution
Historical data collection is unavailable because of incorrect queries in the PureApplication Monitoring Portal.	The column, Sort By, Group By, and First/Last functions are not compatible with the historical data collection feature. Use of these advanced functions will make a query ineligible for historical data collection. Even if data collection has been started, you cannot use the time span feature if the query for the chart or table includes any column functions or advanced query options (Sort By, Group By, First / Last). To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries. See the IBM Tivoli Monitoring Administrator's Guide or the PureApplication Monitoring Portal online Help for information on the Historical Data Collection function.
When you use a long process name in the situation, the process name is truncated.	Truncation of process names in the portal display is the expected behavior. 64 bytes is the maximum name length.
You see the following message: KFWITM083W Default link is disabled for the selected object; please verify link and link anchor definitions.	You see this message because some links do not have default workspaces. Right-click the link to access a list of workspaces to select.

9.5.4. Troubleshooting for remote deployment

Problems that might occur with remote deployment. This chapter provides agent-specific troubleshooting information. See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.

This section describes problems and solutions for remote deployment and removal of agent software Agent Remote Deploy:

Remote deployment problems and solutions

Problem	Solution
The removal of a monitoring agent fails when you use the remote removal process in the PureApplication Monitoring Portal desktop or browser.	This problem might happen when you attempt the remote removal process immediately after you have restarted the PureApplication Monitoring Server. You must allow time for the monitoring agent to refresh its connection with the PureApplication Monitoring Server before you begin the remote removal process.

9.5.5. Situation troubleshooting

This section provides information about both general situation problems and problems with the configuration of situations. See the IBM Tivoli Monitoring Troubleshooting Guide for more information about troubleshooting for situations.

9.5.5.1. General situation problems

Specific situation problems and solutions

Problem	Solution
You want to change the appearance of situations when they are displayed in a Workspace view.	Right-click an item in the Navigation tree. Select Situations in the pop-up menu. The Situation Editor window is displayed. Select the situation that you want to modify. Use the Status pull-down menu in the lower right of the window to set the status and appearance of the Situation when it triggers. Note: This status setting is not related to severity settings in IBM Tivoli Enterprise Console.
Situations are triggered in the Tivoli Enterprise Monitoring Server, but events for the situation are not sent to the Tivoli Enterprise Console server. The Tivoli Enterprise Monitoring Server is properly configured for event forwarding, and events for many other situations are sent to the event server.	This condition can occur when a situation is only monitoring the status of other situations. The event forwarding function requires an attribute group reference in the situation in order to determine the correct event class to use in the event. When the situation only monitors other situations, no attribute groups are defined and the event class cannot be determined. Because the event class cannot be determined, no event is sent. This is a limitation of the Tivoli Enterprise Monitoring Server event forwarding function. Situations that only monitor other situations do not send events to the event server.
Monitoring activity requires too much disk space.	Check the RAS trace logging settings. For example, trace logs grow rapidly when you apply the ALL logging option.
A formula that uses mathematical operators appears to be incorrect. For example, if you were monitoring Linux, a formula that calculates when Free Memory falls under 10 percent of Total Memory does not work: LT #'Linux_VM_Stats.Total_Memory' / 10	This formula is incorrect because situation predicates support only logical operators. Your formulas cannot have mathematical operators. Note: The Situation Editor provides alternatives to math operators. Regarding the example, you can select % Memory Free attribute and avoid the need for math operators.
If you are running a Version 350 Monitoring Agent for Linux OS and you choose to alter the views to include a Version 610 UNICODE attribute, be aware that data for this attribute is not displayed and you see a blank column in this view.	To enable Unicode and other features, upgrade the monitoring agent to IBM PureApplication Monitoring, Version 6.1.0.
IBM PureApplication Monitoring is configured to provide data to the optional product IBM Tivoli Enterprise Console. However, a situation displays the severity UNKNOWN in IBM Tivoli Enterprise Console.	For a situation to have the correct severity in TEC for those situations which are not mapped, you need to ensure that one of the following is true: Specify the severity in the SITINFO column of the O4SRV.TSITDESC table. For example use the values 'SEV=Critical' and 'SEV=Warning' for the SITINFO column in your kxx.sql file, which adds application support to the monitoring product. .OR. Have the name of the situation ends with '_Warn' or '_Warning' for WARNING severity and '_Cri' or '_Critical' for Critical severity
You see the 'Unable to get attribute name' error in the PureApplication Monitoring Server log after creating a situation.	Install the agent's application support files on the Tivoli Enterprise Monitoring Server, by using the following steps: Open the Manage IBM PureApplication Monitoring Services window. Right-click the name of the monitoring server. Select Advanced > Add TEMS Application Support in the pop-up menu. Add application support if any for any agent that is missing from the list. See in IBM PureApplication System Monitoring Server Installation and Setup Guide for more information on adding application support.
Events received at the Tivoli Enterprise Console server from IBM Tivoli Monitoring do not have values for all event attributes (slots) even though the values are visible in workspace views.	The problem is due to a limitation in the IBM Tivoli Monitoring interface code that generates Tivoli Enterprise Console events from situations. The situation results are provided in a chain of buffers of 3000 bytes each. The interface code currently extracts event information from only the first buffer. When situations or agent table data expands into a second buffer, this additional data is not examined, and it is not included in events sent to the Tivoli Enterprise Console server.
Tivoli Enterprise Console events from IBM Tivoli Monitoring 6.2 for IBM Tivoli Monitoring 5.x migrated situations receive parsing errors in the Tivoli Enterprise Console server.	Complete the following two steps: Ensure that you have the IBM Tivoli Monitoring 6.2 Event Sync installed on your Tivoli Enterprise Console server. Obtain updated baroc files from IBM Tivoli Monitoring 6.2 for the monitoring agent's events. Updated baroc files are on the Tivoli Enterprise Monitoring Server in the CANDLEHOME/CMS/TECLIB/itm5migr directory.
You are receiving Tivoli Business Systems Management events that cannot be associated due to application_oid and application_class not being set.	The problem is due to IBM Tivoli Monitoring 6.2 sending Tivoli Enterprise Console events for IBM Tivoli Monitoring 5.x migrated situations. These events are not able to set the cited slot values. Replace the agent_name_forward_tbsm_event_cb.sh script on the Tivoli Enterprise Console server with the version of this file from the Tivoli Enterprise Monitoring Server in the CANDLEHOME/CMS/TECLIB/itm5migr directory.
Situations created using the File Pattern attribute group are always TRUE if the Match Count attribute is not used.	When creating situations using the File Pattern Attribute Group like the following one: [*IF *VALUE Linux_File_Pattern.File_Name *EQ '/path/filename' *AND *VALUE Linux_File_Pattern.Match_Pattern *EQ 'pattern'] the situations are always TRUE. Redefine the situations in the following way: [*IF *VALUE Linux_File_Pattern.File_Name *EQ '/path/filename' *AND *VALUE Linux_File_Pattern.Match_Pattern *EQ 'pattern' *AND *VALUE Linux_File_Pattern.Match_Count *GT 0] The Match_Count attribute must always be used in order to monitor for a match pattern.

9.5.5.2. Problems with configuration of situations

This section provides information for troubleshooting for agents. Be sure to consult the IBM Tivoli Monitoring Troubleshooting Guide for more general troubleshooting information.

Problems with configuring situations that you solve in the Situation Editor

Problem	Solution
Note: To get started with the solutions in this section, perform these steps: Launch the PureApplication Monitoring Portal. Click Edit > Situation Editor. In the tree view, choose the agent whose situation you want to modify. Choose the situation in the list. The Situation Editor view is displayed.
The situation for a specific agent is not visible in the PureApplication Monitoring Portal.	Open the Situation Editor. Access the All managed servers view. If the situation is absent, confirm that application support for Monitoring Agent for Linux OS has been added to the monitoring server. If not, add application support to the server, as described in the IBM PureApplication System Monitoring Server Installation and Setup Guide.
The monitoring interval is too long.	Access the Situation Editor view for the situation that you want to modify. Check the Sampling interval area in the Formula tab. Adjust the time interval as needed.
The situation did not activate at startup.	Manually recycle the situation as follows: Right-click the situation and choose Stop Situation. Right-click the situation and choose Start Situation. Note: You can permanently avoid this problem by placing a check mark in the Run at Startup option of the Situation Editor view for a specific situation.
The situation is not displayed.	Click the Action tab and check whether the situation has an automated corrective action. This action can occur directly or through a policy. The situation might be resolving so quickly that you do not see the event or the update in the graphical user interface.
An Alert event has not occurred even though the predicate has been properly specified.	Check the logs, reports, and workspaces.
A situation fires on an unexpected managed object.	Confirm that you have distributed and started the situation on the correct managed system.
The product did not distribute the situation to a managed system.	Click the Distribution tab and check the distribution settings for the situation.
The situation does not fire. Incorrect predicates are present in the formula that defines the situation. For example, the managed object shows a state that normally triggers a monitoring event, but the situation is not true because the wrong attribute is specified in the formula.	In the Formula tab, analyze predicates as follows: Click the fx icon in the upper-right corner of the Formula area. The Show formula window is displayed. Confirm the following details in the Formula area at the top of the window: The attributes that you intend to monitor are specified in the formula. The situations that you intend to monitor are specified in the formula. The logical operators in the formula match your monitoring goal. The numerical values in the formula match your monitoring goal. (Optional) Click the Show detailed formula check box in the lower left of the window to see the original names of attributes in the application or operating system that you are monitoring. Click OK to dismiss the Show formula window. (Optional) In the Formula area of the Formula tab, temporarily assign numerical values that will immediately trigger a monitoring event. The triggering of the event confirms that other predicates in the formula are valid. Note: After you complete this test, you must restore the numerical values to valid levels so that you do not generate excessive monitoring data based on your temporary settings.

Problems with configuration of situations that you solve in the Workspace area

Problem	Solution
Situation events are not displayed in the Events Console view of the workspace.	Associate the situation with a workspace. Note: The situation does not need to be displayed in the workspace. It is sufficient that the situation be associated with any workspace.
You do not have access to a situation.	Note: You must have administrator privileges to perform these steps. Select Edit > Administer Users to access the Administer Users window. In the Users area, select the user whose privileges you want to modify. In the Permissions tab, Applications tab, and Navigator Views tab, select the permissions or privileges that correspond to the user's role. Click OK.
A managed system seems to be offline.	Select Physical View and highlight the Enterprise Level of the navigator tree. Select View > Workspace > Managed System Status to see a list of managed systems and their status. If a system is offline, check network connectivity and status of the specific system or application.

Problems with configuration of situations that you solve in the Manage IBM PureApplication Monitoring Services window

Problem	Solution
After an attempt to restart the agents in the PureApplication Monitoring Portal, the agents are still not running.	Check the system status and check the appropriate IBM PureApplication Monitoring logs.
The PureApplication Monitoring Server is not running.	Check the system status and check the appropriate IBM PureApplication Monitoring logs.
The managed objects you created are firing on incorrect managed systems.	Check the managed system distribution on both the situation and the managed object settings sheets.

9.6. Support information

9.7. Accessing terminology online

The IBM Terminology website consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology website at the following Web address:

http://www.ibm.com/software/globalization/terminology

9.8. Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Documentation Central website at http://www.ibm.com/tivoli/documentation.

Note: If you print PDF documents on other than letter-sized paper, set the option in the File &rarrow; Print window that allows Adobe Reader to print letter-sized pages on your local paper.

9.9. Ordering publications

You can order many Tivoli publications online at http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.

You can also order by telephone by calling one of these numbers:

• In the United States: 800-879-2755
• In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative, perform the following steps:

1. Go to http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.
2. Select your country from the list and click Go.
3. Click About this site in the main panel to see an information page that includes the telephone number of your local representative.

9.10. Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education website at http://www.ibm.com/software/tivoli/education.

9.11. Tivoli user groups

Tivoli user groups are independent, user-run membership organizations that provide Tivoli users with information to assist them in the implementation of Tivoli Software solutions. Through these groups, members can share information and learn from the knowledge and experience of other Tivoli users. Tivoli user groups include the following members and groups:

• 23,000+ members
• 144+ groups

10. Upgrading for warehouse summarization

The Monitoring Agent for Linux OS made changes to the warehouse collection and summarization characteristics for some agent attribute groups. These changes correct and improve the way warehouse data is summarized, producing more meaningful historical reports. This appendix explains those changes and the implications to your warehouse collection and reporting.

Note: This upgrade is only available from IBM Tivoli Monitoring v6.1.0 to v6.2.1, and is not available for upgrading from IBM Tivoli Monitoring v6.2 to v6.2.1.

Warehouse summarization is controlled on a per-table basis. How the rows in each table are summarized is determined by a set of attributes in each table that are designated as primary keys. There is always one primary key representing the monitored resource, and data is minimally summarized based on this value. For all agents, this primary key is represented internally by the column name, ORIGINNODE; however, the external attribute name varies with each monitoring agent.

One or more additional primary keys are provided for each attribute group to further refine the level of summarization for that attribute group. For example, in an OS agent disk attribute group, a primary key might be specified for the logical disk name that allows historical information to be reported for each logical disk in a computer.

10.1. Tables in the warehouse

For a monitoring agent, there are two main types of warehouse tables:

• Raw tables:

  These tables contain the raw information reported by a monitoring agent and written to the warehouse by the Warehouse Proxy agent. Raw tables are named for the attribute group that they represent, for example, lnxallusr.

• Summary tables:

  These tables contain summarized information based on the raw tables and written to the warehouse by the Summarization and Pruning agent. Summarization provides aggregation results over various reporting intervals, for example, hours, days, and so on. Summary table names are based on the raw table name with an appended suffix, for example, lnxallusr_H, lnxallusr_D, and so on.

10.2. Effects on summarized attributes

When tables are summarized in the warehouse, the summary tables and summary views are created to include additional columns to report summarization information.

Time periods and suffixes for summary tables and views

Data collection time period	Summary table suffixes	Summary view suffixes
Hourly	_H	_HV
Daily	_D	_DV
Weekly	_W	_WV
Monthly	_M	_MV
Quarterly	_Q	_QV
Yearly	_Y	_YV

columns of some of the most commonly used attribute types.

Additional columns to report summarization information

Attribute name	Aggregation type	Additional summarization columns
MyGauge	GAUGE	MIN_MyGauge MAX_MyGauge SUM_MyGauge AVG_MyGauge
MyCounter	COUNTER	TOT_MyCounter HI_MyCounter LO_MyCounter LAT_MyCounter
MyProperty	PROPERTY	LAT_Property

These additional columns are provided only for attributes that are not primary keys. In the cases when an existing attribute is changed to be a primary key, the Summarization and Pruning agent no longer creates summarization values for the attributes, but the previously created column names remain in the table with any values already provided for those columns. These columns cannot be deleted from the warehouse database, but as new data is collected, these columns will not contain values. Similarly, when the primary key for an existing attribute has its designation removed, that attribute has new summarization columns automatically added. As new data is collected, it is used to populate these new column values, but any existing summarization records do not have values for these new columns.

The overall effect of these primary key changes is that summarization information is changing. If these changes result in the old summarization records no longer making sense, you can delete them. As a part of warehouse upgrade, summary views are dropped. The views will be re-created by the Summarization and Pruning agent the next time it runs. Dropping and re-creating the views ensure that they reflect the current table structure.

10.3. Upgrading your warehouse with limited user permissions

The IBM Tivoli Monitoring warehouse agents (Warehouse Proxy and Summarization and Pruning agents) can dynamically adjust warehouse table definitions based on attribute group and attribute information being loaded into the warehouse. These types of table changes must be done for this monitoring agent for one or both of the following conditions:

• The monitoring agent has added new attributes to an existing attribute group and that attribute group is included in the warehouse.
• The monitoring agent has added a new attribute group and that attribute group is included in the warehouse.

For the warehouse agents to automatically modify the warehouse table definitions, they must have permission to alter warehouse tables. You might not have granted these agents these permissions, choosing instead to manually define the raw tables and summary tables needed for the monitoring agents. Or, you might have granted these permissions initially, and then revoked them after the tables were created.

You have two options to effect the required warehouse table changes during the upgrade process:

• Grant the warehouse agents temporary permission to alter tables

  If using this option, grant the permissions, start historical collection for all the desired tables, allow the Warehouse Proxy agent to add the new data to the raw tables, and allow the Summarization and Pruning agent to summarize data for all affected tables. Then, remove the permission to alter tables

• Make the warehouse table updates manually

  If using this option, you must determine the table structures for the raw and summary tables. If you manually created the tables in the earlier warehouse definition, you already have a methodology and tools to assist you in this effort. You can use a similar technique to update and add new tables for this warehouse migration.

  For a method of obtaining raw table schema, refer to the IBM Redbook,Tivoli Management Services Warehouse and Reporting, January 2007, SG24-7290. The chapter that explains warehouse tuning includes a section on creating data tables manually.

10.4. Types of table changes

The following types of table changes affect warehouse summarization:

• Case 1 - New attribute added to an attribute group and defined as a primary key.
• Case 2 - Existing attribute defined as a primary key or had primary key designation removed.
• Case 3 - Moving some tables from 4K tablespaces to 8K tablespaces when using DB2 as the warehouse database.

Case 1 and Case 2 are primary key changes. In both cases, new summarization records will not match existing summarized data:

• A new attribute was added to an attribute group and that attribute was defined as a primary key:

  New summarization records will provide more accurate summarization or greater granularity than previous records. Existing summarization records are still available but contain less granular detail if default values are not assigned for the new primary keys.

• An existing attribute was defined as a primary key or the primary key designation was removed:

  If a new key was added, then the new summarization records will provide more accurate summarization or greater granularity than previous records. If a key was removed, then the new summarization records will provide less granularity than previous records, but with the intent of providing more meaningful summarization. Existing summarization records are still available.

Case 3 requires that you move some tables from 4K tablespaces to 8K tablespaces when using DB2 as the warehouse database to avoid errors during summarization and pruning processing.

10.5. Table summary

Information to help you determine the effects of primary key and warehouse changes for this monitoring agent. The table shows each attribute group, the current primary keys (in addition to ORIGINNODE) for the attribute group, primary keys that were removed, and whether this table is being included in warehouse reporting.

Primary key and warehouse changes for the Monitoring Agent for Linux OS

Attribute group (the attribute group name as it is displayed in the Tivoli Enterprise Portal)	Current primary keys	Removed primary keys	Warehoused
KLZ_CPU_Averages			Yes
KLZ_CPU	CPU_ID		Yes
KLZ_Disk_IO	Dev_Name		Yes
KLZ_Disk_Usage_Trends	Disk_Name		Yes
KLZ_Disk	Mount_Point Disk_Name		Yes
KLZ_IO_Ext	Device_Name		Yes
KLZ_NFS_Statistics	NFS_Version Location		Yes
KLZ_Network	Network_Interface_Name		Yes
KLZ_Process_User_Info	Process_ID		Yes
KLZ_Process	Process_ID		Yes
KLZ_RPC_Statistics			Yes
KLZ_Sockets_Detail	Socket_Inode		Yes
KLZ_Sockets_Status	Socket_Protocol		Yes
KLZ_Swap_Rate			Yes
KLZ_System_Statistics			Yes
KLZ_User_Login	Login_PID User_Name		Yes
KLZ_VM_Stats			Yes
Linux_All_Users	User_ID_64 User_ID		Yes
Linux_CPU_Averages			Yes
Linux_CPU_Config	CPU_ID		Yes
Linux_CPU	CPU_ID		Yes
Linux_Disk_IO	Dev_Name		Yes
Linux_Disk_Usage_Trends	Disk_Name		Yes
Linux_Disk	Mount_Point_U Disk_Name		Yes
Linux_File_Comparison	File_Name_2 File_Name_1		No
Linux_File_Information	File_Name_U Path_U		No
Linux_File_Pattern	File_Name		No
Linux_Group	Group_ID_64 Group_ID		Yes
Linux_Host_Availability	Target_Host		No
Linux_IO_Ext	Device_Name		Yes
Linux_IP_Address	IP_Address Network_Interface_Name		No
Linux_Machine_Information			Yes
Linux_NFS_Statistics	NFS_Version Location		Yes
Linux_Network	Network_Interface_Name		Yes
Linux_OS_Config	OS_Name		Yes
Linux_Process_User_Info	Process_ID		Yes
Linux_Process	Process_ID		Yes
Linux_RPC_Statistics			Yes
Linux_Sockets_Detail	Socket_Inode		Yes
Linux_Sockets_Status	Socket_Protocol		Yes
Linux_Swap_Rate			Yes
Linux_System_Statistics			Yes
Linux_User_Login	User_Name_U Login_PID		Yes
Linux_VM_Stats			Yes

10.6. Upgrading your warehouse for primary key and tablespace changes

Upgrading your warehouse includes making the following types of changes:

• Case 1 - New attribute is added and is designated as a primary key
  • New attribute and a default value must be added to the raw table and the summarization tables.

    If the attribute group name is not too large for the underlying database, the table name corresponds to the attribute group name. If the attribute group name is too long, a short name is used. The mapping of attribute group names to table names is stored in the WAREHOUSEID table.

  • Case-1 scripts that perform the following actions are provided to assist in this change:
    • Alter existing raw tables
    • Alter existing summary tables
    • Drop existing summary views

  • These changes must be done before the monitoring agent is started and begins exporting data to the Warehouse Proxy agent.

• Case-2 - Existing attributes are changed to either add or remove primary key designation.
  • Existing data is of limited value and should be deleted.
  • Case-2_Truncate scripts that perform the following actions are provided to assist in this change:
    • Remove all records from existing summary tables, preserving existing table definitions
    • Delete the raw data marker allowing raw data to be resummarized

  • Case-2_Drop scripts that perform the following actions are provided to assist in this change:
    • Drop existing summary views
    • Drop existing summary tables
    • Delete the raw data marker allowing raw data to be resummarized

  • These changes are optional, but result in more accurate summarized information.

• Case 3 - Move tables from 4K tablespace to 8K tablespace for selected agents
  • Special processing for selected agents, to move tables from a 4K tablespace to an 8K tablespace.
  • Individual scripts are provided for each summary table to be changed.

10.6.1. Affected attribute groups and supporting scripts

Attribute groups and summary tables affected for this monitoring agent, the names of the SQL scripts provided to assist in the upgrade process, the types of warehouse databases for which the scripts must be run, and the types of changes (cases) to which the scripts apply.

Scripts for affected attribute groups and summary tables for the Monitoring Agent for Linux OS

Attribute group or summary table	File	DB2	Oracle	MS SQL Server	Case 1	Case 2
Linux_All_Users	klz_61migr_Linux_OS_Agent_Case-1.sql	X	X	X	X
Linux_Group	klz_61migr_Linux_OS_Agent_Case-1.sql	X	X	X	X

The following types of warehouse objects are affected by these scripts. Review the scripts before running them:

• Case-1.sql

  These scripts affect raw tables, summary tables, and summary views.

• Case-2_Drop.sql

  These scripts affect the summary tables, summary views, and the Summarization and Pruning agent WAREHOUSEMARKER table.

• Case-2_Truncate.sql

  These scripts affect the summary tables and the Summarization and Pruning agent WAREHOUSEMARKER table.

10.6.2. Procedures

The warehouse can be hosted on any of three databases: DB2, Oracle, or Microsoft SQL Server. There are different sets of script files for each type of database. These scripts are provided as part of the monitoring agent PureApplication Portal Server support file installation. After installing the PureApplication Portal Server support files for the monitoring agent, the files are located on the PureApplication Portal Server computer in install_dir/CNPS/SQLLIB/WAREHOUSE. There is a subdirectory for each type of database: DB2 for DB2, Oracle for Oracle, and SQLServer for Microsoft SQL Server.

The scripts provide commands for all affected tables and views. If you do not have summarization enabled for some periods, for example, quarterly or yearly, you will not have the corresponding summary tables (_Q, _Y) and summary views (_QV, _YV) in your warehouse database. If you run the scripts that are provided, the database reports errors for these missing objects. The scripts continue to run the remaining commands. Similarly, if you rerun the scripts, all commands are attempted. If the objects do not exist, or the command cannot be run (especially for the ALTER commands), the scripts continue processing the remaining commands.

10.6.2.1. DB2 warehouse database procedure

1. Stop all running Warehouse Proxy agent instances and the Summarization and Pruning agent.
2. Back up your warehouse database.
3. Copy the scripts from the PureApplication Portal Server in one of the following directories to a temporary directory on the system where the warehouse database is located:
   • Windows:

     install dir\CNPS\SQLLIB\WAREHOUSE\DB2
     

   • UNIX and Linux:

     install dir/arch/cq/sqllib/WAREHOUSE/DB2
     

4. On the system where the warehouse database is located, change to the directory where you placed the script files in Step 3. Then, connect to the warehouse database through the DB2 command line with a user ID that has the authorization to load and alter tables and drop views. Run commands based on the following example to connect, set the schema, and save the script to an output file:

   db2 connect to WAREHOUS user ITMUSER using ITMPASS
   db2 set current schema="ITMUSER"
   db2 -tv -z log/script.sql.log -f script.sql
   

   These parameters are used in the example:
   • WAREHOUS is the database name.
   • ITMUSER is the user name used by the Warehouse Proxy agent.
   • ITMPASS is the password used by the Warehouse Proxy agent.
   • script.sql is the name of the script file.
   • script.sql.log is the name of the output file.

   Notes: You might receive error messages such the following from DB2:

   • SQL0204N "schema name.table name" is an undefined name. SQLSTATE=42704

     This message indicates that the table named table name does not exist and cannot be altered or dropped. This happens if you do not have warehousing or summarization enabled for the given table. For example if you only have hourly and daily summarization enabled, you see this message for the weekly, monthly, quarterly, and yearly summarization tables because these tables do not exist.

   • SQL3304N The table does not exist.

     This message indicates that the table does not exist and cannot be loaded. This happens if you do not have warehousing or summarization enabled for the given table. For example if you only have hourly and daily summarization enabled, you see this message for the weekly, monthly, quarterly, and yearly summarization tables because these tables do not exist.

10.6.2.2. Oracle warehouse database procedure

1. Stop all running Warehouse Proxy agent instances and the Summarization and Pruning agent.
2. Back up your warehouse database.
3. Copy the scripts from The PureApplication Portal Server in one of the following directories to a temporary directory on the system where the warehouse database is located:
   • Windows

     install dir\CNPS\SQLLIB\WAREHOUSE\Oracle
     

   • UNIX and Linux

     install dir/arch/cq/sqllib/WAREHOUSE/Oracle
     

4. On the system where the warehouse database is located, change to the directory where you placed the script files in Step 3. Then, connect to the warehouse database through the Oracle command line with the same user that the Warehouse Proxy agent uses to connect to the warehouse, and run the script. To run the script, the user ID must have authorization to alter tables and drop views, or to drop tables when using Case 2 Drop, or truncate tables when using Case 2 Truncate. The output is saved to a file named script name.log. Run the following command:

   sqlplus ITMUSER/ITMPASS@WAREHOUS @script.sql
   

   These parameters are used in the example:
   • WAREHOUS is the connect identifier.
   • ITMUSER is the user name used by the Warehouse Proxy agent.
   • ITMPASS is the password used by the Warehouse Proxy agent.
   • script.sql is the name of this script file.

   Note: You might receive error messages such as the following from Oracle: ORA-00942: table or view does not exist

   This message indicates that the table does not exist and cannot be altered, dropped, or truncated. This happens if you do not have warehousing or summarization enabled for the given table. For example if you only have hourly and daily summarization enabled, you see this message for the weekly, monthly, quarterly, and yearly summarization tables because these tables do not exist.

10.6.2.3. MS SQL warehouse database procedure

1. Stop all running Warehouse Proxy agent instances and the Summarization and Pruning agent.
2. Back up your warehouse database.
3. Copy the scripts from the PureApplication Portal Server in the one of the following directories to a temporary directory on the system where the warehouse database is located:
   • Windows:

     install dir\CNPS\SQLLIB\WAREHOUSE\SQLServer
     

   • UNIX and Linux:

     install dir/arch/cq/sqllib/WAREHOUSE/SQLServer
     

4. On the system where the warehouse database is located, change to the directory where you placed the script files in Step 3. Then, connect to the warehouse database through the SQL Server command line with the same user that the Warehouse Proxy agent uses to connect to the warehouse, and run the script. To run the script, the user ID must have authorization to alter tables and drop views, or to drop tables when using Case 2 Drop, or truncate tables when using Case 2 Truncate. The output is saved to a file named script name.log. Run the following command:

   osql -I -S SQLHOST[\SQLINST] -U ITMUSER -P ITMPASS -d WAREHOUS
      -m-1 -n -o log/script.sql.log -i script.sql
   

   These parameters are used in the example:
   • WAREHOUS is the database name.
   • ITMUSER is the user name used by the Warehouse Proxy agent.
   • ITMPASS is the password used by the Warehouse Proxy agent.
   • script.sql is the name of this script file.
   • SQLHOST is the SQL server name.
   • SQLINST is the optional SQL instance name.

   Note: You might receive error messages from the SQL Server such as the following: Msg 4902, Level 16, State 1, Server ENTERPRISE, Line 1 Cannot find the object "table name" because it does not exist or you do not have permissions.

   This message indicates that the table named table name does not exist and cannot be dropped or truncated. This happens if you do not have warehousing or summarization enabled for the given table. For example if you only have hourly and daily summarization enabled, you see this message for the weekly, monthly, quarterly, and yearly summarization tables because these tables do not exist.

IBM Tivoli Enterprise Console event mapping

Each event class corresponds to an attribute group in the IBM Tivoli Enterprise Console. For a description of the event slots for each event class, see the lists in this appendix. For more information about mapping attribute groups to event classes, see the Administrator's Guide.

Generic event mapping provides useful event class and attribute information for situations that do not have specific event mapping defined. BAROC files are found on the PureApplication Monitoring Server in the installation directory in TECLIB (that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console event synchronization provides a collection of ready-to-use rule sets that you can deploy with minimal configuration. Be sure to install IBM Tivoli Enterprise Console event synchronization to access the correct Sentry.baroc, which is automatically included during base configuration of IBM Tivoli Enterprise Console rules if you indicate that you want to use an existing rule base. See the Installation and Setup Guide for details.

Each of the event classes is a child of KHD_Base and is defined in the khd.baroc (version 06.02.00) file. The KHD_Base event class can be used for generic rules processing for any event from the Warehouse Proxy.

For events generated by situations in the Config attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_CONFIG class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• start_time: STRING

• work_queue_size: INTEGER

• work_queue_size_enum: STRING

• worker_threads: INTEGER

• worker_threads_enum: STRING

• connection_pool_size: INTEGER

• connection_pool_size_enum: STRING

• export_timeout: INTEGER

• export_timeout_enum: STRING

• rpcsource_cleanup_wait: INTEGER

• rpcsource_cleanup_wait_enum: STRING

• database_connection_wait: INTEGER

• database_connection_wait_enum: STRING

• enable_database_connection_wait: INTEGER

• enable_database_connection_wait_enum: STRING

• batch: INTEGER

• batch_enum: STRING

• always_disconnect_option: INTEGER

• always_disconnect_option_enum: STRING

• kbb_sig1: STRING

• rate_wait_interval: INTEGER

• rate_wait_interval_enum: STRING

• registration_wait_interval: INTEGER

• registration_wait_interval_enum: STRING

• error_time: INTEGER

• error_time_enum: STRING

• max_error: INTEGER

• max_error_enum: STRING

• max_node: INTEGER

• max_node_enum: STRING

• database_compression: INTEGER

• database_compression_enum: STRING

• warehouse_compression_z_sources: INTEGER

• warehouse_compression_z_sources_enum: STRING

• warehouse_compression_distributed_sources: INTEGER

• warehouse_compression_distributed_sources_enum: STRING

For events generated by situations in the DB Info attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_DB INFO class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• db_type: INTEGER

• db_type_enum: STRING

• db_version: STRING

• db_name: STRING

• db_user: STRING

• nls_settings: STRING

• driver_name: STRING

• driver_version: STRING

• odbc_datasource_name: STRING

• url: STRING

• khd_classpath: STRING

• khd_java_args: STRING

• db_connectivity: INTEGER

• db_connectivity_enum: STRING

For events generated by situations in the Last Error Details attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_LAST ERROR DETAILS class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• error_type: STRING

• error_severity: INTEGER

• error_severity_enum: STRING

• error_file: STRING

• error_function: STRING

• error_line: INTEGER

• error_line_enum: STRING

• sql_code: INTEGER

• sql_code_enum: STRING

• sql_state: STRING

• error_reason_code: INTEGER

• error_reason_code_enum: STRING

• error_message: STRING

• error_api_call: STRING

• rows_not_exported: INTEGER

• rows_not_exported_enum: STRING

• failed_system: STRING

• product_code: STRING

• table_name: STRING

• attribute_group_name: STRING

• error_timestamp: STRING

For events generated by situations in the Load Statistics attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_LOAD STATISTICS class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• node_count: INTEGER

• node_count_enum: STRING

• rows_sent: INTEGER

• rows_sent_enum: STRING

• rows_retrieved: INTEGER

• rows_retrieved_enum: STRING

• rows_inserted: INTEGER

• rows_inserted_enum: STRING

• row_throughput: REAL

• row_throughput_enum: STRING

• failures: INTEGER

• failures_enum: STRING

• failure_rate: REAL

• failure_rate_enum: STRING

• disconnections: INTEGER

• disconnections_enum: STRING

• disconnection_rate: REAL

• disconnection_rate_enum: STRING

For events generated by situations in the Node List attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_NODE LIST class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• node_name: STRING

• export_count: INTEGER

• export_count_enum: STRING

• export_v101_count: INTEGER

• export_v101_count_enum: STRING

• export_v610_count: INTEGER

• export_v610_count_enum: STRING

• last_export_time: STRING

For events generated by situations in the Registration Address List attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_REGISTRATION ADDRESS LIST class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• registration_address: STRING

• registration_status: INTEGER

• registration_status_enum: STRING

• registration_time: STRING

For events generated by situations in the RPCSource Statistics attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_RPCSOURCE STATISTICS class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• orphaned_rpcsource: INTEGER

• orphaned_rpcsource_enum: STRING

• rpcsource_created: INTEGER

• rpcsource_created_enum: STRING

• rpcsource_creation_rate: REAL

• rpcsource_creation_rate_enum: STRING

• rpcsource_deleted: INTEGER

• rpcsource_deleted_enum: STRING

• rpcsource_deletion_rate: REAL

• rpcsource_deletion_rate_enum: STRING

For events generated by situations in the Warehouse TEMS List attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_WAREHOUSE TEMS LIST class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• tems_name: STRING

For events generated by situations in the Work Queue attribute group, Tivoli Enterprise Console events are sent using the ITM_KHD_WORK QUEUE class. This class contains the following slots:

• node: STRING

• timestamp: STRING

• maximum_queue_size: INTEGER

• maximum_queue_size_enum: STRING

• current_queue_size: INTEGER

• current_queue_size_enum: STRING

• export_queued: INTEGER

• export_queued_enum: STRING

• work_queue_insertion_rate: REAL

• work_queue_insertion_rate_enum: STRING

• export_unqueued: INTEGER

• export_unqueued_enum: STRING

• work_queue_removal_rate: REAL

• work_queue_removal_rate_enum: STRING

• export_rejected: INTEGER

• export_rejected_enum: STRING

• excess_work_queue_insertion: INTEGER

• excess_work_queue_insertion_enum: STRING

• work_queue_suspensions: INTEGER

• work_queue_suspensions_enum: STRING

Monitoring Agent for Linux OS data collection

In general, the Monitoring Agent for Linux OS gathers data when requested to satisfy a workspace refresh, situation sampling of attributes, or historical data collection. All attributes in the attribute groups that make up a workspace or situation are gathered at that time. The default refresh/sampling intervals were chosen such that the agent will not put a significant load on the system as it gathers the data.

The following table shows each Linux attribute group.

Mechanisms used to gather attributes

Attribute group	Attribute name	Collection method
KLZLOGIN	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	USRNAME	getutent API; struct utmp.ut_user
	USRPID	getutent API; struct utmp.ut_pid
	LINE	getutent API; struct utmp.ut_line
	LOGINTIME	getutent API; struct utmp.ut_tv.tv_sec
	IDLETIME	stat API on /dev/ut_line to get last access time & substract from current time
	FROMHOST	getutent API; struct utmp.ut_host
KLZDISK	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DSKNAME	getmntent API; struct mntent.mnt_fsname
	MOUNTPT	getmntent API; struct mntent.mnt_dir
	FSTYPE	statfs API; struct statfs elements: f_blocks * (f_bsize / 1024) / 1024
	DSKSIZE	statfs API; struct statfs elements: (f_blocks * (f_bsize / 1024)) / 1024
	DSKUSED	statfs API; struct statfs elements: ((f_blocks - f_bfree) * (f_bsize / 1024)) / 1024
	DSKUSEDPCT	DSKUSED * 100.0 / (DSKUSED + DSKFREE)
	DSKFREE	statfs API; struct statfs elements: ((f_blocks - f_bfree) * (f_bsize / 1024)) / 1024
	DSKFREEPCT	100 - DSKCUSEDPCT
	INDSIZE	statfs API; struct statfs element: f_files
	INDUSED	statfs API; struct statfs elements: f_files - f_ffree
	INDFREE	statfs API; struct statfs element: f_ffree
	INDFREEPCT	100 - INDUSEDPCT
	INDUSEDPCT	INODEUSED * 100.0 / f_files
	FSSTATUS	UP or DOWN (if statfs64() times out);
KLZDU	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DSKNAME	getmntent API; struct mntent.mnt_fsname
	SPCUSED	statfs API; struct statfs elements: ((f_blocks - f_bfree) * (f_bsize / 1024)) / 1024
	SPCFREE	statfs API; struct statfs elements: (f_bavail * (f_bsize / 1024)) / 1024
	DURATE	Calculated from "N" and "N - 1" samples of SPCUSED
	HWDURATE	Larger of "N" and "N - 1" samples of DURATE
	HWTIME	Timestamp associated with the HWDURATE sample
	DUMVAVG	Average of all DURATE values
	DAYSDSK	(SPCAVAIL * 1024 * 1024) / (DUMVAVG * 24)
	DAYSCURR	(SPCAVAIL * 1024 * 1024 / (DURATE * 24)
	LWCURR	Smaller of "N" and "N - 1" samples of DAYSCURR
	DAYSPEAK	(SPCAVAIL * 1024 * 1024) / (HWDURATE * 24)
KLZNET	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	FNAME	Read from /proc/net/dev
	FIPADDR	socket, ioctl & inet_ntoa APIs
	FSTATUS	socket & ioctl APIs
	FMTU	socket & ioctl APIs
	FIKBYTES	Read from /proc/net/dev & divided by 1024
	RECBPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FOKBYTES	Read from /proc/net/dev & divided by 1024
	TRANSBPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FIFRAMES	Read from /proc/net/dev
	RPACKPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FOFRAMES	Read from /proc/net/dev
	TPACKPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FIERRORS	Read from /proc/net/dev
	FOERRORS	Read from /proc/net/dev
	FCOLLSNS	Read from /proc/net/dev
	FCOLLSNRT	Read from /proc/net/dev; samples_("N" - "N - 1") * 60 / sample_interval
	FCOLLSPCT	Read from /proc/net/dev; for this sample period: (collisions / (frames sent + frames rcved)) * 100
	FIERRORT	Read from /proc/net/dev; samples_("N" - "N - 1") * 60 / sample_interval
	FOERRORT	Read from /proc/net/dev; samples_("N" - "N - 1") * 60 / sample_interval
	FIOERRPCT	Read from /proc/net/dev; for this sample period: (input_errors + output_errors) / (frames_sent + frames_rcved)) * 100
KLZNET	FIDROP	Read 5th value from /proc/net/dev
	FODROP	Read 11th value from /proc/net/dev
	FIFOINOVR	Read from /proc/net/dev
	FIPKTFRAM	Read from /proc/net/dev
	FCARRIER	Read from /proc/net/dev
	FIERRPCT	FIOERRPCT * (FIERRORT / (FIERRORT + FOERRORT))
	FOERRPCT	FIOERRPCT - FIERRPCT
	DEVTYPE	socket & ioctl APIs
	MACADDRESS	socket & ioctl APIs
KLZCPU	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	CPUID	Read from /proc/stat
	USRCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRNCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	SYSCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	IDLECPU	10000 - BUSYCPU
	BUSYCPU	USRCPU + USRNCPU + SYSCPU + WAITCPU
	WAITCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRSYSCPU	((USRNCPU + USRCPU) * 100) / SYSCPU
	STEALCPU	Read from /proc/stat; samples_("N" - "N - 1") / Total_CPU_over_the_sample_interval * 10000
KLZCPUAVG	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DAYSCPU	Read from /proc/stat; total_moving_used_cpu / (previous_moving_idle - current_moving_idle); converted to days.
	CPUCURAVG	USRNCURAVG + USRCURAVG + WAITCUR + SYSCPUCUR
	CPUMOVAVG	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	USRNCURAVG	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRNMOVCPU	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	USRCURAVG	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRMOVCPU	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	SYSCPUCUR	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
KLZCPUAVG (Continued)	SYSCPUMOV	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	IDLECUR	10000 - CPUCURAVG
	IDLEMOV	10000 - (USRNMOVCPU + USRMOVCPU + WAITMOV+ SYSCPUMOV)
	WAITCUR	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	WAITMOV	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
KLZPROC	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	PID	Read from /proc; PID is the subdirectory name
	PPID	Read from /proc/PID/stat
	CMD	Read from /proc/PID/stat
	CMDLINE	Read from /proc/PID/cmdline
	STATE	Read from /proc/PID/stat
	PSYSCPU	Read from /proc/PID/stat; converted from jiffies
	PUSRCPU	Read from /proc/PID/stat; converted from jiffies
	TSYSCPU	Read from /proc/PID/stat; converted from jiffies
	TUSRCPU	Read from /proc/PID/stat; converted from jiffies
	INTPRI	Read from /proc/PID/stat
	NICE	Read from /proc/PID/stat
	SIZE	Read from /proc/PID/statm
	RSS	Read from /proc/PID/statm
	SHAREMEM	Read from /proc/PID/statm
	TRS	Read from /proc/PID/statm
	LRS	Read from /proc/PID/statm
	DRS	Read from /proc/PID/statm
	DIRTPG	Read from /proc/PID/statm
	VMSIZE	Read from /proc/PID/status
	VMLOCK	Read from /proc/PID/status
	VMDATA	Read from /proc/PID/status
	VMSTACK	Read from /proc/PID/status
	VMEXESZ	Read from /proc/PID/status
	VMLIBSZ	Read from /proc/PID/status
	CMINFLT	Read from /proc/PID/stat
	CMAJFLT	Read from /proc/PID/stat
	CPUAFF	Read from /proc/PID/stat
	USRSYSCPU	(TUSRCPU / TSYSCPU) * 100
	TBUSYCPU	TSYSCPU + TUSRCPU
KLZPROC (Continued)	BUSYCPU	PSYSCPU + PUSRCPU
	CPUSECONDS	Read user + system CPU time from /proc/PID/stat; converted from jiffies to seconds
	TOTALTIME	Read user+system CPU time from /proc/PID/stat; converted in days,hours,minutes,seconds format
	UPROCFILT	the regular expression that matched; empty otherwise
	CPUPERCENT	Read user+system CPU time from /proc/PID/stat; converted from jiffies; samples ("N" - "N . 1") *10000 / (sample_interval * number of CPUs)
	SYSTEMTIM	Read system CPU time from /proc/PID/stat; converted in days,hours,minutes,seconds format
	USERTIME	Read user CPU time from /proc/PID/stat; converted in days,hours,minutes,seconds format
	VMSIZEMB	Read from /proc/PID/status; converted to MB
	VMLOCKMB	Read from /proc/PID/status; converted to MB
	VMDATAMB	Read from /proc/PID/status; converted to MB
	VMSTACKMB	Read from /proc/PID/status; converted to MB
	VMEXESZMB	Read from /proc/PID/status; converted to MB
	VMLIBSZMB	Read from /proc/PID/status; converted to MB
	PROCTHRD	Read from /proc/PID/status
	SESSIONID	Read from /proc/PID/stat
	PSYSNORM	Read from /proc/PID/stat; converted from jiffies
	PUSRNORM	Process user-mode time read from /prod/PID/stat; Nbr of CPUs read from sysconf API; (current_user_mode - previous_user_mode) / (elapsed_time * nbr_of_ cpus)
	PBUSYNORM	Process kernel-mode time read from /prod/PID/stat; Nbr of CPUs read from sysconf API; (current_kernel_mode - previous_kernel_mode) / (elapsed_time * nbr_of_ cpus)
	PROCCOUNT	Generated; count of processes with same CMDLINE
KLZPUSR	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	PID	Read from /proc; PID is the subdirectory name
	RUSERID	Read from /proc/PID/status
	EUSERID	Read from /proc/PID/status
	SUSERID	Read from /proc/PID/status
	FSUSERID	Read from /proc/PID/status
	RGRPID	Read from /proc/PID/status
	EFFGRPID	Read from /proc/PID/status
	SGRPID	Read from /proc/PID/status
	FSGRPID	Read from /proc/PID/status
	RUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	EUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	SUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	FSUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	RGRP	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	EGRP	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	SGRP	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	FSGRP	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	SESSIONID	Read from /proc/PID/stat
	PPID	Read from /proc/PID/stat
	STATE	Read from /proc/PID/stat
KLZPUSR (Continued)	CMD	Read from /proc/PID/stat
	CMDLINE	Read from /proc/PID/cmdline
	VMSIZEMB	Read from /proc/PID/status; converted to MB
	TTY	Read from /proc/PID/stat; converted to string by internal method
KLZSYS	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	CSWSEC	Read from /proc/PID/stat; samples_("N" - "N - 1") / sample_interval
	RATECSW	Read from /proc/PID/stat; ((current_CSWSEC - previous_CSWSEC) / previous_CSWSEC) * 100
	PROCSEC	Read from /proc/PID/stat; samples_("N" - "N - 1") / sample_interval
	RATEPROC	Read from /proc/PID/stat; ((current_PROCSEC - previous_PROCSEC) / previous_PROCSEC) * 100
	CURUSRS	getutent API; count of entries in utmp database
	LOAD1MIN	Read from /proc/loadavg
	LOAD5MIN	Read from /proc/loadavg
	LOAD15MIN	Read from /proc/loadavg
	SYSUPTIME	Read from /proc/uptime
	PGPGIN	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	PGPGINPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
	PGPGOUT	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	PGPGOUTPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
	PGSWAPIN	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	SWAPINPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
KLZSYS (Continued)	PGSWAPOUT	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	SWAPOUTPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
	PGFLTPS	Read from /proc/vmstat (2.6 kernel) samples_("N" - "N - 1") / sample_interval * 100; N/A on 2.4 kernel
	MAJFLTPS	Read from /proc/vmstat (2.6 kernel) samples_("N" - "N - 1") / sample_interval * 100; N/A on 2.4 kernel
	TOTPROCS	Count process subdirs in /proc
	ZOMBCNT	Count process subdirs in /proc in zombie state
KLZSWPRT	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	MOVSWPTOT	Read from /proc/meminfo; (last MOVSWAPTOT + SwapTotal) / 2
	SWAPUSED	Read from /proc/meminfo; (last SWAPUSED + (SwapTotal - SwapFree)) / 2
	SWPRATE	Read from /proc/meminfo; (last SWAPRATE + ((SwapTotal - SwapFree) - previous_SWAPUSED)) / 2
	SWAPDAYS	Read from /proc/meminfo; SwapTotal / (24 * SWAPRATE)
	PKSWPUSD	Read from /proc/meminfo; larger of last two (SwapTotal - SwapFree)
	MINSWPDAYS	Read from /proc/meminfoo; smaller of last two SWAPDAYS
	LOWMEM	Read from /proc/meminfo; LowFree
KLZVM	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	SWPTOT	Read from /proc/meminfo; (SwapTotal / 1024) * 100
	SWPUSED	Read from /proc/meminfo; ((SwapTotal - SwapFree) / 1024) * 100
	SWPUSEDPCT	Read from /proc/meminfo; ((SwapTotal - SwapFree) / SwapTotal) * 100
	SWPFREE	Read from /proc/meminfo; (SwapFree / 1024) * 100
	SWPFREEPCT	100 - SWPUSEDPCT
	MEMTOT	Read from /proc/meminfo; (MemTotal / 1024) * 100
	MEMUSED	Read from /proc/meminfo; ((MemTotal - MemFree) / 1024) * 100
	MEMUSEDPCT	Read from /proc/meminfo; ((MemTotal - MemFree) / MemTotal) * 100
	MEMFREE	Read from /proc/meminfo; (MemFree / 1024) * 100
	MEMFREEPCT	100 - MEMUSEDPCT
	MEMSHARED	Read from /proc/meminfo; (MemShared / 1024) * 100
	MEMBUFF	Read from /proc/meminfo; (Buffers / 1024) * 100
	MEMCACHE	Read from /proc/meminfo; (Cache / 1024) * 100
	VSTOT	MEMTOT + SWPTOT
	VSUSED	SWPUSED + MEMUSED
	VSUSEDPCT	100 - VSFREEPCT
	VSFREE	VSTOT - VSUSED
	VSFREEPCT	(VSFREE / VSTOT) * 100
	MEMCACHPCT	Read cached and total from /proc/meminfo; cached * 100/total
	NETMEMUSED	MEMUSED . MEMCACHE - MEMBUFF
	NETMEMUPCT	NETMEMUSED / MEMTOT
	TOTMEMFREE	MEMFREE + MEMCACHE + MEMBUFF
	TOTMEMFPCT	TOTMEMFREE / MEMTOT
KLZSOCKS	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	SCKPROTO	Read from /proc/net/sockstat
	SCKINUSE	Read from /proc/net/sockstat
	SCKHWUSED	Read from /proc/net/sockstat
KLZSOCKD	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	SCKPROTO	Generated TCP/UDP indicator
	RECVQ	Read from /proc/net/tcp or /proc/net/udp
	SENDQ	Read from /proc/net/tcp or /proc/net/udp
	LOCLADDR	Read from /proc/net/tcp or /proc/net/udp
	LOCLPORT	Read from /proc/net/tcp or /proc/net/udp
	LOCLSVC	Read from /proc/net/tcp or /proc/net/udp & getservbyport API; struct servent.s_name
	FORNADDR	Read from /proc/net/tcp or /proc/net/udp
	STATE	Read from /proc/net/tcp or /proc/net/udp
	SOCKUID	Read from /proc/net/tcp or /proc/net/udp
	SCKINOD	Read from /proc/net/tcp or /proc/net/udp
	REMOTPORT	Read from /proc/net/tcp or /proc/net/udp
	RUSER	Read from /proc/net/tcp or /proc/net/udp& getpwuid API; struct passed.pw_name
KLZDSKIO	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	TPS	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); reads + writes; samples_("N" - "N - 1") / sample_interval
	BLKRDSSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors read; samples_("N" - "N - 1") / sample_interval
	BLKWRTNSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors written; samples_("N" - "N - 1") / sample_interval
	BLKSRD	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); total sectors read
	BLKSWRTN	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); total sectors written
	DEVMAJOR	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
	DEVMINOR	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
	DKNAME	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
KLZIOEXT	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP		DKNAME	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
	RDRQMSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); reads merged; samples_("N" - "N - 1") / sample_interval
	WRTRQMSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); writes merged; samples_("N" - "N - 1") / sample_interval
	RDRQSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); reads; samples_("N" - "N - 1") / sample_interval
	WRTREQSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); writes; samples_("N" - "N - 1") / sample_interval
	RDSECTSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors read; samples_("N" - "N - 1") / sample_interval
	WRSECTSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors written; samples_("N" - "N - 1") / sample_interval
	AVGRQSZ	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); (sectors_read + sectors_written) / (totals_reads + total_writes)
	KLZIOEXT (Continued)	AVGRQQUSZ	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); I/O in progress; samples_("N" - "N - 1") / sample_interval
AVGWAITTM		Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); (time_reading + time_ writing) / (totals_reads + total_writes)
AVGSVCTM		Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); time_spent_on_I/O / (totals_reads + total_writes)
IOUTIL		Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); time_spent_on_I/O / monitoring_interval
IUTIL		Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1");IOUTIL / (total_reads / (totals_reads + total_writes))
OUTIL		IOUTIL - OUTIL
RDBYTESEC		RDSECTSEC converted to bytes
WRBYTESEC		WRSECTSEC converted to bytes
TOTBYTSEC		WRBYTESEC + RDBYTESEC
KLZRPC	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	RSCALLS	Read from /proc/net/rpc/nfsd
	RSBADCALL	Read from /proc/net/rpc/nfsd
	RSBADAUTH	Read from /proc/net/rpc/nfsd
	RSBADCLT	Read from /proc/net/rpc/nfsd
	RSXDRCALL	Read from /proc/net/rpc/nfsd
	RCCALLS	Read from /proc/net/rpc/nfs
	RCRETRAN	Read from /proc/net/rpc/nfs
	RCAREF	Read from /proc/net/rpc/nfs
KLZNFS	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	LOCORIG	Generated client/server indicator
	NFSVER	Generated version indicator
	NFSNULL	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	NULLPCT	NFSNULL * 100 / NFSTOT
	NFSGETATT	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	GETATTPCT	NFSGETADD * 100 / NFSTOT
	NFSSETATT
	SETATTPCT	NFSSETATT * 100 / NFSTOT
	NFSROOT
	NFSROOTPCT	NFSROOT * 100 / NFSTOT
	NFSLOOKUP
	LOOKUPPCT	NFSLOOKUP * 100 / NFSTOT
	NFSRDLINK
	RDLINKPCT	NFSRDLINK * 100 / NFSTOT
	NFSREAD
	READPCT	NFSREAD * 100 / NFSTOT
	NFSWRCACH
	WRCACHPCT	NFSWRCACH * 100 / NFSTOT
	NFSWRITES
	NFSWRTPCT	NFSWRITES * 100 / NFSTOT
	NFSCREATES
	CREATESPCT	NFSCREATES * 100 / NFSTOT
	NFSREMOVE
	REMOVEPCT	NFSREMOVE * 100 / NFSTOT
	NFSRENAME
	RENMPCT	NFSRENAME * 100 / NFSTOT
	NFSLINK
KLZNFS (Continued)	LINKPCT	NFSLINK * 100 / NFSTOT
	NFSSYMLNK	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	SYMLNKPCT	NFSSYMLNK * 100 / NFSTOT
	NFSMKDIR
	MKDIRPCT	NFSMKDIR * 100 / NFSTOT
	NSRMDIR
	RMDIRPCT	NFSRMDIR * 100 / NFSTOT
	NFSRDDIR
	RDDIRPCT	NFSRDDIR * 100 / NFSTOT
	NFSFSSTAT
	FSSTATPCT	NFSFSSTAT * 100 / NFSTOT
	NFSACCESS
	ACCSSPCT	NFSACCESS * 100 / NFSTOT
	NFSMKNOD
	MKNODPCT	NFSMKNOD * 100 / NFSTOT
	RDDIRPLUS
	RDIRPLSPCT	RDDIRPLUS * 100 / NFSTOT
	NFSFSINFO
	FSINFOPCT	NFSFSINFO * 100 / NFSTOT
	NFSPTHCONF
	PTHCONFPCT	NFSPTHCONF * 100 / NFSTOT
	NFSCOMMIT
	COMMITPCT	NFSCOMMIT * 100 / NFSTOT
	NFSTOT	NFSNULL + NFSGETATT + NFSSETATT + NFSROOT + NFSLOOKUP + NFSRDLINK + NFSREAD + NFSWRCACH + NFSWRITES + NFSCREATES + NFSREMOVE + NFSRENAME + NFSLINK + NFSSYMLNK + NFSMKDIR + NFSRMDIR + NFSRDDIR + NFSFSSTAT
KLZCPU	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	PKTRETRPS	Read from /proc/net/snmp; samples ("N" - "N . 1") / (sample_interval)
KLZLPAR	CAPWEIGHT	Read from /proc/ppc64/lparcfg
	CAPPED	Read from /proc/ppc64/lparcfg
	ENTITLEMENT	Read from /proc/ppc64/lparcfg
	ENTITLUSED	PHCPUUUSED*10000/ ENTITLEMENT
	LPARID	Read from /proc/ppc64/lparcfg
	MAXCAPUSED	PHCPUUUSED*100/ NVIRTCPUS (if CAPPED = 0); == ENTITLUSED (if CAPPED = 1)
	NVIRTCPUS	Read from /proc/ppc64/lparcfg
	PHCPUUUSED	Read from /proc/ppc64/lparcfg; samples_("N" - "N . 1") *100 / (sample_interval * timebase); timebase read from /proc/cpuinfo
	SHARED	Read from /proc/ppc64/lparcfg
	SHPOOLIDLE	Read from /proc/ppc64/lparcfg; samples ("N" - "N . 1") *100 / (sample_interval * timebase); timebase read from /proc/cpuinfo
	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	STEALTIME	Read aggregate CPU from /proc/stat; samples_("N" - "N - 1") / Total_CPU_over_the_sample_interval * 10000
LNXLOGIN	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	USRNAME	getutent API; struct utmp.ut_user
	USRPID	getutent API; struct utmp.ut_pid
	LINE	getutent API; struct utmp.ut_line
	LOGINTIME	getutent API; struct utmp.ut_tv.tv_sec
	IDLETIME	stat API on /dev/ut_line to get last access time & substract from current time
	FROMHOST	getutent API; struct utmp.ut_host
	USRNAMEU	getutent API; struct utmp.ut_user
LNXDISK	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DSKNAME	getmntent API; struct mntent.mnt_fsname
	MOUNTPT	getmntent API; struct mntent.mnt_dir
	DSKSIZE	statfs API; struct statfs elements: f_blocks * (f_bsize / 1024) / 1024
	SPCUSED	statfs API; struct statfs elements: ((f_blocks - f_bfree) * (f_bsize / 1024)) / 1024
	SPCAVAIL	statfs API; struct statfs elements: (f_bavail * (f_bsize / 1024)) / 1024
	INODESIZE	statfs API; struct statfs element: f_files
	INODEUSED	statfs API; struct statfs elements: f_files - f_ffree
	INODEFREE	statfs API; struct statfs element: f_ffree
	PCTSPCUSED	SPCUSED * 100.0 / (SPCUSED + SPCAVAIL)
	PCTINDUSED	INODEUSED * 100.0 / f_files
	FSTYPE	getmntent API; struct mntent.mnt_type
	PCTSPCAV	100 - PCTSPCUSED
	MOUNTPTU	getmntent API; struct mntent.mnt_dir
	PCTINDAVAL	100 - PCTINDUSED
LNXDU	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DSKNAME	getmntent API; struct mntent.mnt_fsname
	SPCUSED	statfs API; struct statfs elements: ((f_blocks - f_bfree) * (f_bsize / 1024)) / 1024
	SPCAVAIL	statfs API; struct statfs elements: (f_bavail * (f_bsize / 1024)) / 1024
	DURATE	Calculated from "N" and "N - 1" samples of SPCUSED
	HWDURATE	Larger of "N" and "N - 1" samples of DURATE
	HWTIME	Timestamp associated with the HWDURATE sample
	DUMVAVG	Average of all DURATE values
	DAYSDSK	(SPCAVAIL * 1024 * 1024) / (DUMVAVG * 24)
	DAYSCURR	(SPCAVAIL * 1024 * 1024 / (DURATE * 24)
	LWCURR	Smaller of "N" and "N - 1" samples of DAYSCURR
	DAYSPEAK	(SPCAVAIL * 1024 * 1024) / (HWDURATE * 24)
LNXNET	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	FNAME	Read from /proc/net/dev
	FIPADDR	socket, ioctl & inet_ntoa APIs
	FSTATUS	socket & ioctl APIs
	FMTU	socket & ioctl APIs
	FIKBYTES	Read from /proc/net/dev & divided by 1024
	RECBPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FOKBYTES	Read from /proc/net/dev & divided by 1024
	TRANSBPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FIFRAMES	Read from /proc/net/dev
	RPACKPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FOFRAMES	Read from /proc/net/dev
	TPACKPS	Read from /proc/net/dev; samples_("N" - "N - 1") / sample_interval
	FIERRORS	Read from /proc/net/dev
	FOERRORS	Read from /proc/net/dev
	FCOLLSNS	Read from /proc/net/dev
	FCOLLSNRT	Read from /proc/net/dev; samples_("N" - "N - 1") * 60/ sample_interval
	FCOLLSPCT	Read from /proc/net/dev; for this sample period: (collisions / (frames sent + frames rcved)) * 100
	FIERRORT	Read from /proc/net/dev; samples_("N" - "N - 1") * 60/ sample_interval
	FOERRORT	Read from /proc/net/dev; samples_("N" - "N - 1") * 60/ sample_interval
	FIOERRPCT	Read from /proc/net/dev; for this sample period: (input_errors + output_errors) / (frames_sent + frames_rcved)) * 100
LNXNET (Continued)	FIDROP	Read from /proc/net/dev
	FODROP	Read from /proc/net/dev
	FIFOINOVR	Read from /proc/net/dev
	FIFOUTOVR	Read from /proc/net/dev
	FIPKTFRAM	Read from /proc/net/dev
	FCARRIER	Read from /proc/net/dev
	FIERRPCT	FIOERRPCT * (FIERRORT / (FIERRORT + FOERRORT))
	FOERRPCT	FIOERRPCT - FIERRPCT
	DEVTYPE	socket & ioctl APIs
	MACADDRESS	socket & ioctl APIs
LNXCPU	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	CPUID	Read from /proc/stat
	USRCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRNCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	SYSCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	IDLECPU	10000 - BUSYCPU
	BUSYCPU	USRCPU + USRNCPU + SYSCPU + WAITCPU
	WAITCPU	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRSYSCPU	((USRNCPU + USRCPU) * 100) / SYSCPU
LNXCPUAVG	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DAYSCPU	Read from /proc/stat; total_moving_used_cpu / (previous_moving_idle - current_moving_idle); converted to days.
	CPUCURAVG	USRNCURAVG + USRCURAVG + WAITCUR + SYSCPUCUR
	CPUMOVAVG	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	USRNCURAVG	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRNMOVCPU	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	USRCURAVG	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	USRMOVCPU	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	SYSCPUCUR	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
LNXCPUAVG (Continued)	SYSCPUMOV	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
	IDLECUR	10000 - CPUCURAVG
	IDLEMOV	10000 - (USRNMOVCPU + USRMOVCPU + WAITMOV+ SYSCPUMOV)
	WAITCUR	Read from /proc/stat; samples_("N" - "N - 1") / total_CPU_over_the_sample_interval * 10000
	WAITMOV	Read from /proc/stat; metric_moving_average / moving_total_CPU_over_the_sample_interval * 10000; moving average of a metric is (previous_moving_average + samples_("N" - "N - 1")) / 2
LNXPROC	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	PID	Read from /proc; PID is the subdirectory name
	PPID	Read from /proc/PID/stat
	CMD	Read from /proc/PID/stat
	STATE	Read from /proc/PID/stat
	PSYSCPU	Read from /proc/PID/stat; converted from jiffies
	PUSRCPU	Read from /proc/PID/stat; converted from jiffies
	TSYSCPU	Read from /proc/PID/stat; converted from jiffies
	TUSRCPU	Read from /proc/PID/stat
	INTPRI	Read from /proc/PID/stat
	NICE	Read from /proc/PID/statm
	SIZE	Read from /proc/PID/statm
	RSS	Read from /proc/PID/statm
	SHAREMEM	Read from /proc/PID/statm
	TRS	Read from /proc/PID/statm
	LRS	Read from /proc/PID/statm
	DRS	Read from /proc/PID/statm
	DIRTPG	Read from /proc/PID/statm
	VMSIZE	Read from /proc/PID/status
	VMLOCK	Read from /proc/PID/status
	VMDATA	Read from /proc/PID/status
	VMSTACK	Read from /proc/PID/status
	VMEXESZ	Read from /proc/PID/status
	VMLIBSZ	Read from /proc/PID/status
	CMINFLT	Read from /proc/PID/stat
	CMAJFLT	Read from /proc/PID/stat
	CMDLINE	Read from /proc/PID/cmdline
	CMDLINEU	Read from /proc/PID/cmdline
	CPUAFF	Read from /proc/PID/stat
	USRSYSCPU	(TUSRCPU / TSYSCPU) * 100
	CMDU	Read from /proc/PID/stat
	TBUSYCPU	TSYSCPU + TUSRCPU
LNXPROC (Continued)	BUSYCPU	PSYSCPU + PUSRCPU
	VMSIZEMB	Read from /proc/PID/status; converted to MB
	VMLOCKMB	Read from /proc/PID/status; converted to MB
	VMDATAMB	Read from /proc/PID/status; converted to MB
	VMSTACKMB	Read from /proc/PID/status; converted to MB
	VMEXESZMB	Read from /proc/PID/status; converted to MB
	VMLIBSZMB	Read from /proc/PID/status; converted to MB
	PROCTHRD	Read from /proc/PID/status
	SESSIONID	Read from /proc/PID/stat
	PSYSNORM	Read from /proc/PID/stat; converted from jiffies
	PUSRNORM	Process user-mode time read from /prod/PID/stat; Nbr of CPUs read from sysconf API; (current_user_mode - previous_user_mode) / (elapsed_time * nbr_of_ cpus)
	PBUSYNORM	Process kernel-mode time read from /prod/PID/stat; Nbr of CPUs read from sysconf API; (current_kernel_mode - previous_kernel_mode) / (elapsed_time * nbr_of_ cpus)
	PROCCOUNT	Generated; count of processes with same CMDLINE
LNXPUSR	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	PID	Read from /proc; PID is the subdirectory name
	RUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	EUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	SUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	FSUSER	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	RGRP	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	EGRP	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	SGRP	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	FSGRP	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	RUSERID	Read from /proc/PID/status
	EUSERID	Read from /proc/PID/status
	SUSERID	Read from /proc/PID/status
	FSUSRID	Read from /proc/PID/status
	RGRPID	Read from /proc/PID/status
	EFFGRPID	Read from /proc/PID/status
	SGRPID	Read from /proc/PID/status
	FSGRPID	Read from /proc/PID/status
LNXPUSR (Continued)	RUSERU	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	EUSERU	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	SUSERU	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	FSUSERU	Read from /proc/PID/status; converted to string using the getpwuid API; struct passwd.pw_name
	RGRPU	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	EGRPU	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	SGRPU	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	FSGRPU	Read from /proc/PID/status; converted to string using the getgrgid API; struct group.gr_name
	SESSIONID	Read from /proc/PID/stat
	PPID	Read from /proc/PID/stat
	STATE	Read from /proc/PID/stat
	CMDLINEU	Read from /proc/PID/cmdline
	CMDU	Read from /proc/PID/stat
	VMSIZEMB	Read from /proc/PID/status; converted to MB
	TTY	Read from /proc/PID/stat; converted to string by internal method
LNXSYS	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	CSWSEC	Read from /proc/stat; samples_("N" - "N - 1") / sample_interval
	RATECSW	Read from /proc/stat; ((current_CSWSEC - previous_CSWSEC) / previous_CSWSEC) * 100
	PROCSEC	Read from /proc/stat; samples_("N" - "N - 1") / sample_interval
	RATEPROC	Read from /proc/stat; ((current_PROCSEC - previous_PROCSEC) / previous_PROCSEC) * 100
	CURUSRS	getutent API; count of entries in utmp database
	LOAD1MIN	Read from /proc/loadavg * 100
	LOAD5MIN	Read from /proc/loadavg * 100
	LOAD15MIN	Read from /proc/loadavg * 100
	SYSUPTIME	Read from /proc/uptime
	PGPGIN	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	PGPGINPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
	PGPGOUT	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	PGPGOUTPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
	PGSWAPIN	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	SWAPINPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
LNXSYS (Continued)	PGSWAPOUT	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel)
	SWAPOUTPS	Read from /proc/vmstat (2.6 kernel) or /proc/stat (2.4 kernel); samples_("N" - "N - 1") / sample_interval * 100
	PGFLTPS	Read from /proc/vmstat (2.6 kernel) samples_("N" - "N - 1") / sample_interval * 100; N/A on 2.4 kernel
	MAJFLTPS	Read from /proc/vmstat (2.6 kernel) samples_("N" - "N - 1") / sample_interval * 100; N/A on 2.4 kernel
	TOTPROCS	Count process subdirs in /proc
	ZOMBCNT	Count process subdirs in /proc in zombie state
LNXSWPRT	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	MOVSWPTOT	Read from /proc/meminfo; (last MOVSWAPTOT + SwapTotal) / 2
	SWAPUSED	Read from /proc/meminfo; (last SWAPUSED + (SwapTotal - SwapFree)) / 2
	SWPRATE	Read from /proc/meminfo; (last SWAPRATE + ((SwapTotal - SwapFree) - previous_SWAPUSED)) / 2
	SWAPDAYS	Read from /proc/meminfo; SwapTotal / (24 * SWAPRATE)
	PKSWPUSD	Read from /proc/meminfo; larger of last two (SwapTotal - SwapFree)
	MINSWPDAYS	Read from /proc/meminfo; smaller of last two SWAPDAYS
	LOWMEM	Read from /proc/meminfo; LowFree
LNXVM	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	SWAPTOT	Read from /proc/meminfo; (SwapTotal / 1024) * 100
	SWAPUSED	Read from /proc/meminfo; ((SwapTotal - SwapFree) / 1024) * 100
	SWAPFREE	Read from /proc/meminfo; (SwapFree / 1024) * 100
	MEMTOT	Read from /proc/meminfo; (MemTotal / 1024) * 100
	MEMUSED	Read from /proc/meminfo; ((MemTotal - MemFree) / 1024) * 100
	MEMFREE	Read from /proc/meminfo; (MemFree / 1024) * 100
	MEMSHARED	Read from /proc/meminfo; (MemShared / 1024) * 100
	MEMBUFF	Read from /proc/meminfo; (Buffers / 1024) * 100
	MEMCACHE	Read from /proc/meminfo; (Cache / 1024) * 100
	VSTOT	MEMTOT + SWAPTOT
	USEDVS	SWAPUSED + MEMUSED
	AVAILVS	VSTOT - USEDVS
	AVALVSPCT	(AVAILVS / VSTOT) * 100
	USEDVSPCT	100 - USEDSWPPCT
	USEDRLPCT	Read from /proc/meminfo; ((MemTotal - MemFree) / MemTotal) * 100
	AVALRLPCT	100 - USEDSWPPCT
	USEDSWPPCT	Read from /proc/meminfo; ((SwapTotal - SwapFree) / SwapTotal) * 100
	AVALSWPPCT	100 - USEDSWPPCT
LNXSOCKS	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	SCKPROTO	Read from /proc/net/sockstat
	SCKINUSE	Read from /proc/net/sockstat
	SCKHWUSED	Read from /proc/net/sockstat
LNXSOCKD	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	SCKPROTO	Generated TCP/UDP indicator
	RECVQ	Read from /proc/net/tcp or /proc/net/udp
	SENDQ	Read from /proc/net/tcp or /proc/net/udp
	LOCLADDR	Read from /proc/net/tcp or /proc/net/udp
	LOCLPORT	Read from /proc/net/tcp or /proc/net/udp
	LOCLSVC	Read from /proc/net/tcp or /proc/net/udp & getservbyport API; struct servent.s_name
	FORNADDR	Read from /proc/net/tcp or /proc/net/udp
	STATE	Read from /proc/net/tcp or /proc/net/udp
	SOCKUID	Read from /proc/net/tcp or /proc/net/udp
	SCKINOD	Read from /proc/net/tcp or /proc/net/udp
	REMOTPORT	Read from /proc/net/tcp or /proc/net/udp
	RUSERU	Read from /proc/net/tcp or /proc/net/udp & getpwuid API; struct passed.pw_name
LNXDSKIO	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	TPS	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); reads + writes; samples_("N" - "N - 1") / sample_interval
	BLKRDSSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors read; samples_("N" - "N - 1") / sample_interval
	BLKWRTNSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors written; samples_("N" - "N - 1") / sample_interval
	BLKSRD	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); total sectors read
	BLKSWRTN	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); total sectors written
	DEVMAJOR	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
	DEVMINOR	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
	DKNAME	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
LNXIOEXT	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	DKNAME	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel)
	RDRQMSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); reads merged; samples_("N" - "N - 1") / sample_interval
	WRTRQMSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); writes merged; samples_("N" - "N - 1") / sample_interval
	RDRQSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); reads; samples_("N" - "N - 1") / sample_interval
	WRTREQSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); writes; samples_("N" - "N - 1") / sample_interval
	RDSECTSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors read; samples_("N" - "N - 1") / sample_interval
	WRSECTSEC	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); sectors written; samples_("N" - "N - 1") / sample_interval
	AVGRQSZ	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); (sectors_read + sectors_written) / (totals_reads + total_writes)
LNXIOEXT (Continued)	AVGRQQUSZ	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); I/O in progress; samples_("N" - "N - 1") / sample_interval
	AVGWAITTM	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); (time_reading + time_ writing) / (totals_reads + total_writes)
	AVGSVCTM	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); time_spent_on_I/O / (totals_reads + total_writes)
	IOUTIL	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1"); time_spent_on_I/O / monitoring_interval
	IUTIL	Read from /proc/diskstats (2.6 kernel) or /proc/partitions (2.4 kernel); samples_("N" - "N - 1");IOUTIL / (total_reads / (totals_reads + total_writes))
	OUTIL	IOUTIL - OUTIL
	RDBYTESEC	RDSECTSEC converted to bytes
	WRBYTESEC	WRSECTSEC converted to bytes
	TOTBYTSEC	WRBYTESEC + RDBYTESEC
LNXRPC	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	RSCALLS	Read from /proc/net/rpc/nfsd
	RSBADCALL	Read from /proc/net/rpc/nfsd
	RSBADAUTH	Read from /proc/net/rpc/nfsd
	RSBADCLT	Read from /proc/net/rpc/nfsd
	RSXDRCALL	Read from /proc/net/rpc/nfsd
	RCCALLS	Read from /proc/net/rpc/nfs
	RCRETRAN	Read from /proc/net/rpc/nfs
	RCAREF	Read from /proc/net/rpc/nfs
LNXNFS	LOCORIG	Generated client/server indicator
	NFSVER	Generated version indicator
	NFSNULL	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	NULLPCT	NFSNULL * 100 / NFSTOT
	NFSGETATT	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	GETATTPCT	NFSGETADD * 100 / NFSTOT
	NFSSETATT	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	SETATTPCT	NFSSETATT * 100 / NFSTOT
	NFSROOT	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	NFSROOTPCT	NFSROOT * 100 / NFSTOT
	NFSLOOKUP	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	LOOKUPPCT	NFSLOOKUP * 100 / NFSTOT
	NFSRDLINK	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	RDLINKPCT	NFSRDLINK * 100 / NFSTOT
	NFSREAD	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	READPCT	NFSREAD * 100 / NFSTOT
	NFSWRCACH	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	WRCACHPCT	NFSWRCACH * 100 / NFSTOT
	NFSWRITES	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	NFSWRTPCT	NFSWRITES * 100 / NFSTOT
LNXNFS (Continued)	NFSCREATES	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	CREATESPCT	NFSCREATES * 100 / NFSTOT
	NFSREMOVE	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	REMOVEPCT	NFSREMOVE * 100 / NFSTOT
	NFSRENAME	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	RENMPCT	NFSRENAME * 100 / NFSTOT
	NFSLINK	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	LINKPCT	NFSLINK * 100 / NFSTOT
	NFSSYMLNK	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	SYMLNKPCT	NFSSYMLNK * 100 / NFSTOT
	NFSMKDIR	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	MKDIRPCT	NFSMKDIR * 100 / NFSTOT
	NSRMDIR	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	RMDIRPCT	NFSRMDIR * 100 / NFSTOT
	NFSRDDIR	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	RDDIRPCT	NFSRDDIR * 100 / NFSTOT
	NFSFSSTAT	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	FSSTATPCT	NFSFSSTAT * 100 / NFSTOT
	NFSACCESS	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	ACCSSPCT	NFSACCESS * 100 / NFSTOT
LNXNFS (Continued)	NFSMKNOD	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	MKNODPCT	NFSMKNOD * 100 / NFSTOT
	RDDIRPLUS	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	RDIRPLSPCT	RDDIRPLUS * 100 / NFSTOT
	NFSFSINFO	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	FSINFOPCT	NFSFSINFO * 100 / NFSTOT
	NFSPTHCONF	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	PTHCONFPCT	NFSPTHCONF * 100 / NFSTOT
	NFSCOMMIT	Read from /proc/net/rpc/nfs (client) or /proc/net/rpc/nfsd (server)
	COMMITPCT	NFSCOMMIT * 100 / NFSTOT
	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	NFSTOT	"NFSNULL + NFSGETATT + NFSSETATT + NFSROOT + NFSLOOKUP + NFSRDLINK + NFSREAD + NFSWRCACH + NFSWRITES + NFSCREATES + NFSREMOVE + NFSRENAME + NFSLINK + NFSSYMLNK + NFSMKDIR + NFSRMDIR + NFSRDDIR + NFSFSSTAT"
LNXCPUCON	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	CPUID	Read from /proc/cpuinfo
	VENDID	Read from /proc/cpuinfo
	CPUFAMILY	Read from /proc/cpuinfo
	CPUMODEL	Read from /proc/cpuinfo
	MODELNM	Read from /proc/cpuinfo
	CPUCLK	Read from /proc/cpuinfo
	CACHESZ	Read from /proc/cpuinfo
LNXOSCON	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	OSNAME	Read from /proc/version
	OSVER	Read from /proc/version
	GCCVER	Read from /proc/version
	OSVEND	Read from /proc/version
LNXFILE	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	PATHU	stat64, opendir and readdir APIs
	FILEU	stat64, opendir and readdir APIs
	SIZEMB	lstat64 API; struct stat64.st_size / (1024 * 1024) * 1000
	OWNERU	lstat64 API; struct stat64.st_uid & getpwuid API - struct passed.pw_name
	GROUPU	lstat64 API; struct stat64.st_gid & getgrgid API - struct group.gr_name
	CHANGEDTM	lstat64 API; struct stat64.st_mtime
	ACCESSEDTM	lstat64 API; struct stat64.st_atime
	LINKS	lstat64 API; struct stat64.st_nlinks
	ACCESS	lstat64 API; struct stat64.st_mode
	TYPE	lstat64 API; struct stat64.st_mode
	LINKNAMEU	readlink API
	MODE	lstat64 API; struct stat64.st_mode
	STATUSTM	lstat64 API; struct stat64.st_ctime
	HASHALGO	Passed to agent as parameter
	HASHSUM	CRC32, MD5 or SHA1 calculation - internal functions
	FCCHANGED	Generated; true if HASHSUM has changed since last monitoring interval
	SIZEMB64	lstat64 API; struct stat64.st_size / (1024 * 1024) * 1000
LNXPING	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	TGTSERV	Passed to agent as situation parameter or from KLZ_PINGHOSTLIST file
	SERVUP	Result from /bin/ping command
	HOSTRESP	Result from /bin/ping command
LNXFILPAT	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	FILENAME	Passed to agent as parameter
	MATCHPAT	Passed to agent as parameter
	MATCHOPT	Passed to agent as parameter
	MATCHCNT	Result from grep cmd
LNXFILCMP	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	FILENAME1	Passed to agent as parameter
	FILENAME2	Passed to agent as parameter
	COMPOPT	Passed to agent as parameter
	COMPRESULT	Result from /usr/bin/cmp or /usr/bin/diff commands
LNXALLUSR	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	USERNAME	getpwent API; struct passwd.pw_name
	UID	getpwent API; struct passwd.pw_uid
	PWNULL	getspnam API; generated; true if struct spwd.sp_pwdp is empty
	USERDUP	Generated; true if duplicate USERNAME or UID is detected
	USERSES	getpwent & getutxent APIs; generated; matches of struct paswd.pw_name & struct utmpx.ut_user fields
	UID64	getpwent API; struct passwd.pw_uid
LNXGROUP	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	GRPNAME	getgroupent API; struct group.gr_name
	GRPID	getgroupent API; struct group.gr_gid
	GRPDUP	Generated; true if duplicate GRPNAME or GRPID is detected
	GRPID64
LNXMACHIN	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	HOSTNAME	gethostname API
	BRAND	dmidecode program, where supported; hardcoded otherwise
	MODEL	dmidecode program, where supported; hardcoded otherwise
	ONLNCPU	sysconf API
	CONFCPU	sysconf API
	BIOSVER	dmidecode program, where supported; hardcoded otherwise
	BIOSREL	dmidecode program, where supported; hardcoded otherwise
	MACSERIAL	dmidecode program, where supported; hardcoded otherwise
	UUID	dmidecode program, where supported; hardcoded otherwise
LNXIPADDR	ORIGINNODE	Short host name + ":LZ"
	TIMESTAMP	Current time
	INTFNAME	Read from /proc/net/dev
	IPADDRESS	IPv4: socket, ioctl & inet_ntoa APIs. IPv6: read from /proc/net/if_inet6
	DNSNAME	getaddrinfo and getnameinfo APIs
	IPVERSION	Hardcoded based on IP type

Discovery Library Adapter for the monitoring agent

This chapter contains information about the Discovery Library Adapter (DLA) for the Monitoring Agent for Linux.

13.1. About the DLA

The Tivoli Management Services DLA discovers resources and relationships and creates a Discovery Library Book file. The Book follows the Discovery Library IdML schema version 2.9.2 and is used to populate the Configuration Management Database (CMDB) and Tivoli Business System Management products. The Tivoli Management Services DLA discovers Linux resources. For all Linux systems that are active and online at the Tivoli Enterprise Portal Server, information is included in the discovery book for those resources. The Tivoli Management Services DLA discovers active resources. It is run on-demand and can be run periodically to discover resources that were not active during previous discoveries.

The DLA discovers Linux components.

13.2. More information about DLAs

The following sources contain additional information about using the DLA program with all monitoring agents:

• The IBM Tivoli Monitoring Administrator's Guide contains information about using the Tivoli Management Services Discovery Library Adapter.
• For information about using a DLA with Tivoli Application Dependency Discovery Manager (TADDM), see the information center at http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.1/cmdb_welcome.html

13.3. Linux data model class types represented in CDM

This section contains information about how the various source application data objects map to classes in the Common Data Model (CDM) for the Monitoring Agent for Linux.

The following information is provided for each class where appropriate:

Relationships

CDM relationships (hierarchical) between currently identified model objects

CDM attributes, agent attributes, descriptions, and examples

CDM and agent attributes that are required to create an instance of a resource, descriptions of the attributes, and examples of the attributes

13.3.1. Linux class

The following information describes the Linux class.

CDM class name

sys.linux.Linux or sys.zOS.ZLinux

Relationships

• installedOn
• runsOn

CDM attributes, agent attributes, descriptions, and examples

• CDM attribute: ManagedSystemName
  • Agent attribute: none
  • Description: Managed System Name

• CDM attribute: OSVersion
  • Agent attribute: OSVER/LNXOSCON
  • Description: OS Version

• CDM attribute: Name
  • Agent attribute: none
  • Description: "Linux"

• CDM attribute: FQDN
  • Agent attribute: DNSNAME/LNXIPADDR
  • Description: Fully Qualified Domain Name

13.3.2. ComputerSystem class

The following information describes the ComputerSystem class.

CDM class name

sys.ComputerSystem

CDM attributes, agent attributes, descriptions, and examples

• CDM attribute: ManagedSystemName
  • Agent attribute: none
  • Description: Managed System Name

• CDM attribute: Name
  • Agent attribute: none
  • Description: Fully Qualified Host Name

• CDM attribute: Signature
  • Agent attribute: IPADDRESS/LNXIPADDR and MACADDRESS/LNXNET
  • Description: Lowest IP Address ( MAC Address )

• CDM attribute: PrimaryMACAddress
  • Agent attribute: MACADDRESS/LNXNET
  • Description: MAC Address of the network interface with the lowest IP Address (alpha order)

• CDM attribute: Type
  • Agent attribute: none
  • Description: "ComputerSystem"

• CDM attribute: Fqdn
  • Agent attribute: DNSNAME/LNXIPADDR
  • Description: Fully Qualified Domain Name

• CDM attribute: SystemBoardUUID
  • Agent attribute: UUID/LNXMACHIN
  • Description: System Board UUID

• CDM attribute: SerialNumber
  • Agent attribute: MACSERIAL/LNXMACHIN
  • Description: Serial Number

• CDM attribute: Model
  • Agent attribute: MODEL/LNXMACHIN
  • Description: Model

• CDM attribute: Manufacturer
  • Agent attribute: BRAND/LNXMACHIN
  • Description: Manufacturer

• CDM attribute: Label
  • Agent attribute: none
  • Description: Fully Qualified Host Name

13.3.3. IpInterface class

The following information describes the IpInterface class.

CDM class name

net.IpInterface

Relationships

• contains

CDM attributes, agent attributes, descriptions, and examples

none

13.3.4. IpV4Address class

The following information describes the IpV4Address class.

CDM class name

net.IpV4Address

Relationships

• bindsTo

CDM attributes, agent attributes, descriptions, and examples

• CDM attribute: DotNotation
  • IPADDRESS/LNXIPADDR
  • Description: IP Address of the network interface

• CDM attribute: Label
  • Description: IP Address of the network interface

13.3.5. IpV6Address class

The following information describes the IpV6Address class.

CDM class name

net.IpV6Address

Relationships

• bindsTo

CDM attributes, agent attributes, descriptions, and examples

• CDM attribute: StringNotation
  • Agent attribute: IPADDRESS/LNXIPADDR
  • Description: IP Address of the network interface

• CDM attribute: Label
  • Description: IP Address of the network interface

13.3.6. Fqdn class

The following information describes the Fqdn class.

CDM class name

net.Fqdn

CDM attributes, agent attributes, descriptions, and examples

• CDM attribute: Fqdn
  • Agent attribute: DNSNAME/LNXIPADDR
  • Description: Fully Qualified Domain Name

13.3.7. TMSAgent class

The following information describes the TMSAgent class.

CDM class name

app.TMSAgent

Relationships

• installedOn
• monitors

CDM attributes, agent attributes, descriptions, and examples

• CDM attribute: ManagedSystemName
  • Agent attribute: none
  • Description: Managed System Name

• CDM attribute: ManagedObjectName
  • Description: "p@" Managed System Name

• CDM attribute: SoftwareVersion
  • Description: OS Agent ITM version

• CDM attribute: ProductCode
  • Description: OS Agent Product Code (LZ)

• CDM attribute: Affinity
  • Description: OS Agent affinity

• CDM attribute: Label
  • Description: Managed System Name "- Linux OS"