Page History
...
The sar commands compare the system counters over a one-second interval.
| Metric | Explanation |
|---|---|
| Free Memory | The amount of physical memory available to the operating system, system library files, and applications. |
| Cache Hit Rate | How often the system accesses the CPU cache. |
| Page-outs/s | The rate at which pages were written to disk. |
| Page-ins/s | The rate at which pages were read from or written to the disk. |
| Page Free/s | The number of pages that are freed from memory each second. |
| Attaches/s | The number of pages that get attached to memory each second. |
| odio/s | The number of non-paging I/O per operations that occur each second. |
| slots | The number of available initiators. |
| cycle/s | The number of page replacement cycles that occur each second. |
| fault/s | The number of page faults that occur each second. |
| Software Locks/s | The number of software locks that are issued each second. |
Disk
The UIM agent uses the following commands to collect disk statistics:
...
By default, the disk statistics are generated for all disks including disks that are not active. You can change this option within the agent by setting the ACTIVEONLY flag in the perfparse.sh file to 0.
| Metric | Explanation |
|---|---|
| Disk (Spindle) Name | The name of each disk on the system. |
| Usage (% Busy) | The percentage of time during which the disk drive is handling read or write requests. |
| Blocks per second | The number of read and write operations on the disk that occur each second. |
| Transfers/s | The average number of bytes that are transferred to or from the disk during write or read operations. |
| Average Queued Requests | The number of threads that are waiting for processor time. |
| Average Service Time | The average amount of time, in milliseconds, required to carry out a request. |
| Average Wait Time | The average amount of time, in milliseconds, that a transaction waits in a queue. The wait time is directly proportional to the length of the queue. |
Network
The Uptime Infrastructure Monitor UIM agent uses the the netstat command with the following options to collect network metrics from an AIX system:
| Code Block | ||
|---|---|---|
| ||
netstat -s to combine TCP retransmits for all interfaces netstat -I <interface> to average statistics (e.g. kbps, errors and collisions) per interface. |
| Metric | Explanation |
|---|---|
| Receive Rate | The rate, in kilobytes per seconds, at which data is received over a specific network adapter. |
| Send Rate | The rate, in kilobytes per seconds, at which data is sent over a specific network adapter. |
| Packets Inbound Errors | The number of inbound packets that contained errors, which prevent those packets from being delivered to a higher-layer protocol. |
| Packets Outbound Errors | The number of outbound packets that could not be transmitted because of errors. |
| Collisions | The number of signals from two separate nodes on the network that have collided. |
| TCP Retransmits | The number of packets that were re-sent over a network interface. |
Process and
...
workload
The Uptime Infrastructure Monitor UIM agent uses the the ps -eo command to collect , and 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 Uptime Infrastructure MonitorUIM's core. However, the core uses the same 20 processes that were gathered from the Process method. The following data are Data also gathered with the processes : include the names of users, groups and processes, along with their individual statistics (e.g. , such as memory and CPU usage). Uptime Infrastructure MonitorUIM's core will then sort sorts the statistics based on the graph you want to generate (e.g. , for example user, group, or process name.
| Metric | Explanation |
|---|---|
| Number of Processes | The number of processes that are currently running on a system. |
| Process Creation Rate | Determines whether 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. |
| Processes Running | The number of processes that are currently running. |
User
| Processes Blocked | The number of processes that are currently blocked from running. |
| Processes Waiting | The number of processes that are currently waiting to run. |
| Workload - User | The demand that network and local services are putting on the system, based on the IDs of the users who are logged into a system. |
| Workload - Group | The 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. |
| Workload - Process Name | The demand that network and local services are putting on a system, based on the processes that are running. |
| Workload Top 10 - User | The 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. |
| Workload Top 10 - Group | The 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. |
| Workload Top 10 - Process Name | The 10 network and local services that are are putting the most load on the system, based on the processes that are running. |
User
The UIM The Uptime Infrastructure Monitor agent uses the following utilities to collect user metrics from an AIX system:
| Code Block | ||
|---|---|---|
| ||
ps -eo last | head 10 (login history for the last 10 users on the system) who (lists who is currently logged into the system) |
| Metric | Explanation |
|---|---|
| Login History | The number of times or frequency at which a user logs into a system during any 30-minute interval. |
| Sessions | The number of sessions or number of distinct users who are logged into a system during any 30-minute interval. |