The up.time Uptime Infrastructure Monitor Linux agent collects the following performance metrics from the systems on which it is installed:
...
...
Each set of performance metrics is averaged over an interval of one second.
...
CPU
...
The up.time Uptime Infrastructure Monitor agent uses the sar -urWqR 1
command to compare the system counters during a one-second interval. The statistics returned by the agent are averaged for all CPUs on the system.
...
\n\t \n\t \n \n\t \n \n\tThe percentage of time that the processor spends in user mode (a processing mode for applications and subsystems). |
\n\t \n \n \n\t \n\t | The percentage of time that the kernel spends processing system calls. |
\n\t \n \n \n\t \n\tThe amount of waiting time that a |
runnable runable process for a device takes to perform an I/O operation. |
\n\t \n \n \n\t \n\t | The total amount of User %, System %, and |
\nWait \n\t \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\t \n \n ...
Multi-CPU
...
The up.time The Uptime Infrastructure Monitor agent uses the sar
and mpstat
utilities on a Linux system to collect the metrics in the table below from Linux systems with multiple CPUs. The agent averages the statistics from each CPU using the sar -x SELF -I SUM -P ALL -wu 1
command, which compares the system counters during a one-second interval. The statistics that the agent returns are for the entire system, per CPU.
...
\n\t \n \n\t \n \n \n\t | The percentage of CPU user processes that are in use. |
\n \n \n\t \n\t | The 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\t | The 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 | The 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 \n \n\t \n\t | The number of CPU interrupts. |
\n \n \n \n\t \n\t | The total amount of User %, System %, and Wait I/O%. |
\n \n ...
Memory
...
The up.time Uptime Infrastructure Monitor agent uses the free
command to collect the Free Memory metric from a Linux system. The rest of the memory related metrics are gathered by the sar -urWqR 1
command which compares the system counters during a one-second interval. The statistics that the agent returns are for the entire system.
...
\n \n\t \n\t \n\t \n \n \n\t \n\t | The amount of physical memory available to the operating system, system library files, and applications. |
\n\t \n \n \n\t \n\tHow often the system accesses the CPU cache. |
\n\t \n \n \n\t \n\tThe rate at which pages were written to disk. |
\n\t \n \n \n\t \n\t | The rate at which pages were read from or written to the disk. |
\n\t \n \n \n\t \n\t | The number of pages that are freed from memory each second. |
\n\t \n \n \n\t \n\t | The average number of pages that are scanned each second. |
\n\t \n \n \n\t \n\tThe amount of available free swap space, as a percentage of total available free swap space. |
\n\t \n \n ...
Disk
...
The up.time Uptime Infrastructure Monitor agent gathers file system statistics for each file system using the df -lk
command. Disk statistics (e.g. %busy, reads per second and writes per second) are output per disk and compared between polling intervals using the iostat -d -x 1 2 command.
...
\n \n\t \n\t \n\t \n \n \n\t \n\t | The names of each disk on the system. |
\n\t \n \n \n\t \n\tThe percentage of time during which the disk drive is handling read or write requests. |
\n\t \n \n \n \n\t \n\tThe number of read and write operations on the disk that occur each second. |
\n\t \n \n \n\t \n\t | The average number of bytes that have been transferred to or from the disk during write or read operations. |
\n\t \n \n \n\t \n\t | The number of threads that are waiting for processor time. |
\n\t \n \n \n\t \n\t | The average amount of time, in milliseconds, that is required for a request to be carried out. |
\n\t \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\t \n \n ...
Network
...
The up.time Uptime Infrastructure Monitor agent uses the netstat -s
command to retrieve a combined total of TCP Retransmits for all network interfaces. Other network statistics (e.g. kbps, errors and collisions) are averaged, per interface, using the sar -n DEV -n EDEV 1
command, which compares the system counters during a one-second interval.
...
\n \n\t \n\t \n\t \n \n \n\t \n\t | The rate, in kilobytes per seconds, at which data is received over a specific network adapter. |
\n\t \n \n \n\t \n\t | The rate, in kilobytes per seconds, at which data is sent over a specific network adapter. |
\n\t \n \n \n\t \n\t | The number of inbound packets that contained errors, which preventing those packets from being delivered to a higher-layer protocol. |
\n\t \n \n \n\t \n\t | The number of outbound packets that could not be transmitted because of errors. |
\n\t \n \n \n\t \n\tThe number of signals from two separate nodes on the network that have collided. |
\n\t \n \n \n\t \n\t | The number of packets that have been re-sent over a network interface. The agent returns a combined total for all interfaces. |
\n\t \n \n ...
Process
...
The up.time The Uptime Infrastructure Monitor agent uses the ps -eo
command to collect the process information listed in the table below from a Linux system. By default, the agent gathers the top 20 processes and sorts them by the highest CPU usage.
...
\n \n\t \n\t \n\t \n \n \n\t \n\tThe unique identifier of a specific process. |
\n\t \n \n \n \n\t \n\tThe identifier of the process that the process that is currently running. |
\n\t \n \n \n\t \n\t | A value that identifies the current user. |
\n\t \n \n \n\t \n\t | A value that identifies a group of users. |
\n\t \n \n \n\t \n\t | The amount of memory that is being used by a process. |
\n\t \n \n \n\t \n\tThe amount of physical memory that is being used by a process. |
\n\t \n \n \n\tCPU % Utilization by Process |
\n\t | The percentage of CPU time that is being used by individual processes. |
\n\t \n \n \n\tMemory % Utilization by Process |
\n\t | The amount of physical memory that is being used by individual processes. |
\n\t \n \n \n\t \n\t | The time at which the process started. |
\n\t \n \n \n\t \n\tThe time at which the process started. |
\n\t \n \n \n \n\tNumber of Processes Running |
\n\tThe total number of processes that are currently running on the system. |
\n\t \n \n \n\t |
Number of Blocked Processes |
\n\t | The total number of processes that are blocking resources. |
\n\t \n \n\tNumber of Waiting Processes |
\n\tThe total number of processes that are waiting to be executed by the CPU. |
\n\t \n \n \n\t \n\t | The total number of system calls that are executed each second. |
\n\t \n \n \n\t \n\tThe total number of processes that are being spawned over a specified time period. |
\n\t \n \n ...
Workload
...
The up.time The Uptime Infrastructure Monitor agent uses the ps
utility to collect workload information from a Linux system. Workload statistics (based on the same 20 processes that were gathered from the Process method) are sorted within up.timeUptime Infrastructure Monitor's core. The workload processes that the agent gathers include the user/group/process name and their invividual individual statistics, which can be sorted based on the user's desired graph presentation (e.g. user, group or process name).
...
\n \n\t \n\t \n\t \n \n \n\t \n\t | The demand that network and local services are putting on a system, based on the processes that are running. |
\n\t \n \n \n\t \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\t \n \n \n\t \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\t \n \n \n\t |
Workload Top 10 by Process |
\n\t | The 10 processes that are consuming the most CPU resources. |
\n\t \n \n \n\t \n\t | The 10 processes the are consuming the most CPU resources, based on user ID. |
\n\t \n \n \n\t \n\t | The 10 processes the are consuming the most CPU resources, based on group ID. |
\n\t \n \n ...
User
...
The up.time The Uptime Infrastructure Monitor agent uses the following commands to collect user statistics from a system:
...
\nps -eo
\nlast | head 10
(login history for the last 10 users on the system) \nwho
(lists who is currently logged into the system) \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\t | The number of sessions or number of distinct users who are logged into a system during any 30 minute time interval. |
\n \n \n