Related Documentation | \nVersion of up.time \naffected | \nAffected Platforms | \n
\n | \nAll | \nAIX | \n
The up.time AIX agent collects the following performance metrics from the systems on which it is installed:
\n \n \n \nThe AIX agent uses a number of utilities to gather these metrics including:
\n \n-
\n
sar
: collects information about system activity. This version of sar is bundled with AIX.
\nmpstat
: collects processor-related metrics.
\nifconfig
: configures the parameters for network interfaces.
\nps
: reports on the status of processes.
\n
Each set of performance metrics is averaged between the interval at which the up.time monitoring station polls the agent (e.g. every 10 minutes).
\n \nWhenever the sar
command uses the -f
option to specify a file, that file is generated using the sadc 1 1
command. The sadc
command polls the system counters at a one-second interval, and writes the information that it receives to a file. The sar
command then reads this file.
CPU
\n \nThe up.time agent uses the sar -u -f
command to collect CPU metrics from an AIX system. The statistics that the agent returns are averaged for all CPUs on the system and the sar
command compares the system counters during a one-second interval. If you have multiple CPUs, the CPU statistics output by the agent are an average of all the CPUs on the server.
Metric | \n\tExplanation | \n
% Usr | \n\tThe amount of time that the CPU spends in user mode. | \n
% Sys | \n\tThe amount of time that the kernel spends processing system calls. | \n
% WIO | \n\tThe amount of waiting time that a runnable process for a device takes to perform an I/O operation. | \n
Multi CPU Usage | \n\tWhether or not a system wity multiple CPUs is effectively balancing tasks between CPUs, or if processes are being forced off CPUs in certain circumstances. | \n
Run Queue Length | \n\tThe percentage of time that one or more services or processes are waiting to be served by the CPU. | \n
Run Queue Occupancy | \n\tThe percentage of time that one or more services or processes are waiting to be served by the CPU. | \n
Memory
\n \nThe up.time agent uses the vmstat 1 2
command to average statistics for the entire system. The agent also uses the sar
utility with the following options to collect memory metrics from an AIX system:
-
\n
-b -f
(cache metrics)
\n-r -f
(unused memory pages and disk blocks)
\n-q -f
(the average queue length while it is occupied, and the percentage of time the queue is occupied)
\n-c -f
(system calls)
\n
The sar
commands compare the system counters over a one-second interval.
Metric | \n\tExplanation | \n
Free Memory | \n\tThe amount of physical memory available to the operating system, system library files, and applications. | \n
Cache Hit Rate | \n\tHow often the system accesses the CPU cache. | \n
Page-outs/s | \n\tThe rate at which pages were written to disk. | \n
Page-ins/s | \n\tThe rate at which pages were read from or written to the disk. | \n
Page Free/s | \n\tThe number of pages that are freed from memory each second. | \n
Attaches/s | \n\tThe number of pages that get attached to memory each second. | \n
odio/s | \n\tThe number of non-paging disk I/O per operations that occur each second. | \n
slots | \n\tThe number of available initiators. | \n
cycle/s | \n\tThe number of page replacement cycles that occur each second. | \n
fault/s | \n\tThe number of page faults that occur each second. | \n
Software Locks/s | \n\tThe number of software locks that are issued each second. | \n
Disk
\n \nThe up.time agent uses the following commands to collect disk statistics:
\n \n-
\n
df -k
to gather file system capacity statistics, for file system.
\nsar -d -f
to output disk statistics (e.g. %busy, Read/Write/s) per disk, and compare those statisitics between polling intervals.
\n
By default, the disk statistics are generated for all disks (including disks that are not active). This can be changed within the agent by setting the ACTIVEONLY
flag in the perfparse.sh
file to 0.
Metric | \n\tExplanation | \n
Disk (Spindle) Name | \n\tThe names of each disk on the system. | \n
Usage (% Busy) | \n\tThe percentage of time during which the disk drive is handling read or write requests. | \n
Blocks per second | \n\tThe number of read and write operations on the disk that occur each second. | \n
Transfers/s | \n\tThe average number of bytes that have been transferred to or from the disk during write or read operations. | \n
Average Queued Requests | \n\tThe number of threads that are waiting for processor time. | \n
Average Service Time | \n\tThe average amount of time, in milliseconds, that is required for a request to be carried out. | \n
Average Wait Time | \n\tThe average time, in milliseconds, that a transaction is waiting in a queue. The wait time is directly proportional to the length of the queue. | \n
Network
\n \nThe up.time agent uses the netstat command with the following options to collect network metrics from an AIX system:
\n \n-
\n
netstat -s
to combine TCP retransmits for all interfaces
\nnetstat -I <interface>
to average statistics (e.g. kbps, errors and collisions) per interface.
\n
Metric | \n\tExplanation | \n
Receive Rate | \n\tThe rate, in kilobytes per seconds, at which data is received over a specific network adapter. | \n
Send Rate | \n\tThe rate, in kilobytes per seconds, at which data is sent over a specific network adapter. | \n
Packets Inbound Errors | \n\tThe number of inbound packets that contained errors, which preventing those packets from being delivered to a higher-layer protocol. | \n
Packets Outbound Errors | \n\tThe number of outbound packets that could not be transmitted because of errors. | \n
Collisions | \n\tThe number of signals from two separate nodes on the network that have collided. | \n
TCP Retransmits | \n\tThe number of packets that have been re-sent over a network interface. | \n
Process and Workload
\n \nThe up.time agent uses the ps -eo
command to collect process metrics from an AIX system. By default, the agent only gathers the top 20 processes and sorts them by the highest CPU usage.
Workload statistics are sorted within up.time's core. However, the core uses the same 20 processes that were gathered from the Process method. The following data are also gathered with the processes: the names of users, groups and processes along with their invividual statistics (e.g. memory and CPU usage). up.time's core will then sort the statistics based on the graph you want to generate (e.g. user, group or process name).
\n \nMetric | \n\tExplanation | \n
Number of Processes | \n\tThe number of processes that are currently running on a system. | \n
Process Creation Rate | \n\tThis metric determines whether or not there are runaway processes on a system or if a forking-based process (like a Web server) is spawning too many processes over a specified period of time. | \n
Processes Running | \n\tThe number of processes that are currently running. | \n
Processes Blocked | \n\tThe number of processes that are currently being blocked from running. | \n
Processes Waiting | \n\tThe number of processes that are currently waiting to runn. | \n
Workload - User | \n\tThe demand that network and local services are putting on the system, based on the IDs of the users who are logged into a system. | \n
Workload - Group | \n\tThe demand that network and local services are putting on the system, based on the IDs of the user groups that are logged into a system. | \n
Workload - Process Name | \n\tThe demand that network and local services are putting on a system, based on the processes that are running. | \n
Workload Top 10 - User | \n\tThe 10 network and local services that are are putting the most load on the system, based on the IDs of the users who are logged into a system. | \n
Workload Top 10 - Group | \n\tThe 10 network and local services that are are putting the most load on the system, based on the IDs of the user groups who are logged into a system. | \n
Workload Top 10 - Process Name | \n\tThe 10 network and local services that are are putting the most load on the system, based on the processes that are running. | \n
User
\n \nThe up.time agent uses the following utilities to collect user metrics from an AIX system:
\n \n-
\n
ps -eo
\nlast | head 10
(login history for the last 10 users on the system)
\nwho
(lists who is currently logged into the system)
\n
Metric | \n\tExplanation | \n
Login History | \n\tThe number of times or frequency at which a user has logged into a system during any 30 minute time interval. | \n
Sessions | \n\tThe number of sessions or number of distinct users who are logged into a system during any 30 minute time interval. | \n