\n \n \nRelated Documentation | \nVersion of up.time \naffected | \nAffected Platforms | \n
\n \n \n | \nAll | \nTru64 | \n
\n \n
...
The up.time The Uptime Infrastructure Monitor 4 Tru64 agent collect the following performance metrics from the systems on which it is installed:
...
...
The Tru64 agent uses a number of utilities to gather these metrics including:
...
\ncollect
: a utility that is bundled with Tru64 and collects operating system and process information. The collect utility comes with Tru64 versions 4.x and 5.x. \nsar
: collects information about system activity. \nvmstat
: collects virtual memory metrics. \nifconfig
: configures the parameters for network interfaces. \nps
: reports on the status of processes. \nswapon
: a Tru64 utility that reports on the allocation and usage of swap space. \n
...
Each set of performance metrics is averaged between the interval at which the up.time Uptime Infrastructure Monitor monitoring station polls the agent (e.g. every 10 minutes).
...
CPU
...
The up.time The Uptime Infrastructure Monitor agent uses the sar
utility (with the -u
and -f
options) to collect the metrics listed below from a Tru64 agent. The statistics returned by the agent are averaged for all CPUs on the system.
...
\n\t \n \n \n\t \n\t | The amount of time that the CPU spends in user mode. |
\n \n \n \n\t \n \n\t | The amount of time that the kernel spends processing system calls. |
\n \n \n \n\t \n \n\tThe amount of waiting time that a |
runnable runable process for a device takes to perform an I/O operation. |
\n \n \n \n\t \n\t wity with multiple CPUs is effectively balancing tasks between CPUs, or if processes are being forced off CPUs in certain circumstances. |
\n \n \n\t \n\tThe percentage of time that one or more services or processes are waiting to be served by the CPU. |
\n \n \n \n\t \n\t | The percentage of time that one or more services or processes are waiting to be served by the CPU. |
\n \n ...
Multi-CPU
...
The up.time Uptime Infrastructure Monitor agent uses the psrinfo
utility on a Tru64 system to collect information about CPUs, then uses the sar
and mpstat
utilities to collect the metrics listed below from systems with multiple CPUs. The CPU statistics output by the agent are an average of all the CPUs on the server.
...
\n \n\t \n\tt \n \n \n\ \n \n\t | The percentage of CPU user processes that are in use. |
\n \n \n\t \n\tThe percentage of CPU kernel processes that are in use. |
\n \n \n\t \n\tThe percentage of time that a process which can be run must wait for a device to perform an I/O operation. |
\n \n \n \n\t \n\tThe number of read or write locks that a thread was not able to acquire on the first attempt, as reported by the mpstat command. |
\n \n \n\t \n\t \n \n \n\tThe number of interprocess cross-calls. In a multi-processor environment, one processor sends cross-calls to another processor to get that processor to do work. Cross-calls can also be used to ensure consistency in virtual memory. Heavy file system activity such as NFS can result in a high number of cross-calls. |
\n \n\t | The number of CPU interrupts. |
\n \n \n \n\t \n\tThe total amount of User %, System %, and Wait I/O%. |
\n \n ...
Memory
...
The up.time Uptime Infrastructure Monitor agent uses the following commands to collect memory metrics from a Tru64 system:
...
\nvmstat
\nswapon -s
(free swap) \nsar -b -f
(cache) \nsar -g -f
(paging and swapping) \nsar -p -f
(page-in activity) \n
...
The statistics that the agent returns are for the entire system.
...
\n\t \n\t \n \n \n\t \n\tThe amount of physical memory available to the operating system, system library files, and applications. |
\n \n \n \n\t \n\tHow often the system accesses the CPU cache. |
\n \n \n\t \n\tThe rate at which pages were written to disk. |
\n \n \n\t \n\tThe rate at which pages were read from or written to the disk. |
\n \n \n\t \n\tThe number of pages that are freed from memory each second. |
\n \n \n\t \n\tThe number of pages that get attached to memory each second. |
\n \n \n\t \n\t | The number of requests to perform a write operation that occur each second. |
\n \n \n \n\t \n\t | The number of requests to perform a read operation that occur each second. |
\n \n \n \n\t \n\tThe number of pages that are scanned each second. |
\n \n \n \n\t \n\tThe number of page faults that occur each second. |
\n \n \n \n\t \n\t | The number of software locks that are issued each second. |
\n \n ...
Disk
...
The up.time The Uptime Infrastructure Monitor agent uses the following commands to collect disk metrics from a Tru64 system:
...
collect -i1 -R7s -sd
\nsar -d -f
(free swap) \n
...
The agent collects volume capacity statistics from each filesystem, while the disk statistics (%busy, Read/Write/s) are returned for each disk.
...
\n \n\t \n\t \n \n \n\t \n\t | The names of each disk on the system. |
\n \n \n\t \n\tThe percentage of time during which the disk drive is handling read or write requests. |
\n \n \n \n\t \n\t | The number of read and write operations on the disk that occur each second. |
\n \n \n\t \n\tThe average number of bytes that have been transferred to or from the disk during write or read operations. |
\n \n \n\t \n \n\tThe number of threads that are waiting for processor time. |
\n \n \n\t \n\t | The average amount of time, in milliseconds, that is required for a request to be carried out. |
\n \n \n\t \n\t | The 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 \n ...
Network
...
The up.time The Uptime Infrastructure Monitor agent uses the following commands to collect network metrics from a Tru64 system:
...
ifconfig
\nnetstat -I
(free swap) \n
...
Except for TCP retransmits, the agent averages all statistics per interface.
...
\n \n\t \n\t \n\t \n \n \n\t | The rate, in kilobytes per seconds, at which data is received over a specific network adapter. |
\n \n \n \n\t \n\tThe rate, in kilobytes per seconds, at which data is sent over a specific network adapter. |
\n \n \n\t \n\tThe number of inbound packets that contained errors, which preventing those packets from being delivered to a higher-layer protocol. |
\n \n \n\t \n\tThe number of outbound packets that could not be transmitted because of errors. |
\n \n \n\t \n\t | The number of signals from two separate nodes on the network that have collided. |
\n \n \n\t \n\t | The number of packets that have been re-sent over a network interface. |
\n \n ...
Process
...
The up.time Uptime Infrastructure Monitor agent uses the following commands to collect process metrics from a Tru64 system:
...
\nvmstat
(blocked, running, and waiting processes \nps
\n
...
By default, the agent only gathers the top 20 processes, and sorts them by the highest CPU usage.
...
\n \n\t \n\t \n \n \n\t \n\tThe number of processes that are currently running on a system. |
\n \n \n \n\t \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 \n \n\t \n\tThe number of processes that are currently running. |
\n \n \n\t \n\tThe number of processes that are currently being blocked from running. |
\n \n \n\t \n\tThe number of processes that are currently waiting to |
runn \n \n\t \n \n\t | 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. |
\n \n \n\t \n\t | 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. |
\n \n \n\t \n\tThe demand that network and local services are putting on a system, based on the processes that are running. |
\n \n \n\t \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 \n \n \n\t \n\t \n \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. |
\nWorkload 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
...
The up.time Uptime Infrastructure Monitor agent uses the following commands to collect user statistics from a Tru64 system:
...
\nps -eo
\nlast
(login history for the last 10 users on the system) \n
...
\n \n\t \n\t \n \n \n\t \n\t | The number of times or frequency at which a user has logged into a system during any 30 minute time interval. |
\n \n \n \n\t \n\tThe number of sessions or number of distinct users who are logged into a system during any 30 minute time interval. |
\n \n \n