Versions Compared

Old Version 1

changes.mady.by.user Unknown User (adimopoulos)

Saved on

compared with

New Version 2

changes.mady.by.user Sam Sulu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

...

 

\n \n \n \n \n \n \n \n \n \n \n
Related DocumentationVersion of up.time \naffectedaffectedAffected Platforms
\nAllIRIX

...

 AllIRIX

 

The up.time IRIX agent collects the following performance metrics from the systems on which it is installed:

...

 

...

 

The IRIX agent uses a number of utilities to gather these metrics including:

...

 

    \n
  • sar: collects information about system activity.
    • \n
  • ifconfig: configures the parameters for network interfaces.
    • \n
  • ps: reports on the status of processes.
    • \n
  • netstat: reports on network status.
    • \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).

...

 

CPU

...

 

The up.time agent uses the sar utility (with the -u and -f options) to collect the metrics listed below from an IRIX system. The statistics returned by the agent are averaged for all CPUs on the system.

 

\

...

t\

...

t\

...

t \

...

t \t

...

\

...

t \t

...

\

...

t \

...

t\

...

t\t

...

\

...

t \

...

t\t

MetricExplanation
% UsrThe amount of time that the CPU spends in user mode.
\n
\n \n \n\t
% Sys
\n \n\t
The amount of time that the kernel spends processing system calls.
\n \n \n \n\t
% WIO
\n \n\t
The amount of waiting time that a runnable process for a device takes to perform an I/O operation.
\n \n \n \n\t
Multi CPU Usage
\n\t
Whether 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 \n \n\t
Run Queue Length
\n\t
The percentage of time that one or more services or processes are waiting to be served by the CPU.
\n \n \n \n\t
Run Queue Occupancy
\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 agent collects the metrics listed below from IRIX systems with multiple CPUs. The CPU statistics output by the agent are an average of all the CPUs on the server.

...

 

\t\t\t \t\t\t\t\t \t\t\t\t \t\t \t\t

\n \n\tMetric \n\tExplanation \n \n \n\tUser % \n \n\t
MetricExplanation
User %
The percentage of CPU user processes that are in use.
\n \n \n\t
System %
\n\t
The percentage of CPU kernel processes that are in use.
\n \n
\n\t
Wait I/O %
\n\t
The 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
SMTX
\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
XCAL
\n\t \n \n \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
Interrupts
\n\t
The number of CPU interrupts.
\n \n \n \n\t
Total %
\n\t
The total amount of User %, System %, and Wait I/O%.
\n \n

...

Memory

...

 

Memory

 

The up.time agent uses the sar utility with the following options to collect memory metrics from an IRIX system:

...

 

  • -w -f (swap activity)
    • \n
  • -b -f (buffer activity)
    • \n
  • -p -f (paging activity)
    • \n

...

 

The statistics the agent returns are for the entire system.

 

...

\t\t\t\t \t\t\t\t\t\t\t\t\t\t\t\t \t\t \t\t \t\t \t

MetricExplanation
Free Memory
\n \n\tMetric \n\tExplanation \n \n \n\tFree Memory \n\t
The amount of physical memory available to the operating system, system library files, and applications.
\n \n
\n \n\t
Cache Hit Rate
\n\t
How often the system accesses the CPU cache.
\n \n \n\t
Page-outs/s
\n\t
The rate at which pages were written to disk.
\n \n \n\t
Page-ins/s
\n\t
The rate at which pages were read from or written to the disk.
\n \n \n\t
Page Frees/s
\n\t
The number of pages that are freed from memory each second.
\n \n \n\t
Attaches/s
\n\t
The number of pages that get attached to memory each second.
\n \n \n\t
Page-out Requests/s
\n\t
The number of requests to perform a write operation that occur each second.
\n \n \n \n\t
Page-in reqs/s
\n\t
The number of requests to perform a read operation that occur each second.
\n \n \n \n\t
PageScans/s
\n\t
The number of pages that are scanned each second.
\n \n \n \n\t
PageFaults/s
\n\t
The number of page faults that occur each second.
\n
\n \n \n\t
Software Locks/s
\n
The number of software locks that are issued each second.
\n \n

...

Disk

...

 

Disk

 

The up.time agent uses the sar utility with the -d and -f options to collect the disk metrics listed below from an IRIX system. The agent collects volume capacity statistics from each filesystem, while the disk statistics (%busy, Read/Write/s) returned are for each disk.

...

 

\t\t\t\t\t\t \t\t\t\t\t\t\t\t\t\t

\n \n\tMetric \n\tExplanation \n \n \n\t
MetricExplanation
Disk (Spindle) Name
\n\t
The names of each disk on the system.
\n \n
\n\t
Usage (% Busy)
\n\t
The percentage of time during which the disk drive is handling read or write requests.
\n \n \n \n\t
Blocks per second
\n\t
The number of read and write operations on the disk that occur each second.
\n \n \n\t
Transfers/s
\n\t
The average number of bytes that have been transferred to or from the disk during write or read operations.
\n \n \n\t
Average Queued Requests
\n\t
The number of threads that are waiting for processor time.
\n
\n \n\t
Average Service Time
\n\t
The average amount of time, in milliseconds, that is required for a request to be carried out.
\n \n \n\t
Average Wait Time
\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 agent uses the following utilities to collect network data from an IRIX system:

...

 

    \n
  • ifconfig -a
    • \n
  • netstat -s
    • \n

...

 

Except for TCP retransmits, the agent averages all statistics per interface.

...

 

\t\t\t\t \t\t\t\t\t\t\t\t\t\t

\n \n\tMetric \n\tExplanation \n \n \n\tReceive Rate \n\t
MetricExplanation
Receive Rate
The rate, in kilobytes per seconds, at which data is received over a specific network adapter.
\n \n \n \n\t
Send Rate
\n\t
The rate, in kilobytes per seconds, at which data is sent over a specific network adapter.
\n
\n \n\t
Packets Inbound Errors
\n\t
The number of inbound packets that contained errors, which preventing those packets from being delivered to a higher-layer protocol.
\n \n \n\t
Packets Outbound Errors
\n\t
The number of outbound packets that could not be transmitted because of errors.
\n
\n \n\t
Collisions
\n\t
The number of signals from two separate nodes on the network that have collided.
\n \n \n\t
TCP Retransmits
\n\t
The number of packets that have been re-sent over a network interface.
\n \n

...

Process

...

 

Process

 

The up.time agent uses the ps utility with the -ef option to collect the process data listed below from an IRIX system. By default, the agent only gathers the top 20 processes, and sorts them by the highest CPU usage.

 

...

\t\t\t\t \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t \t\t\t\t

MetricExplanation
Number of Processes
\n \n\tMetric \n\tExplanation \n \n \n\tNumber of Processes \n\t
The number of processes that are currently running on a system.
\n \n \n \n\t
Process Creation Rate
\n\t
This 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
Processes Running
\n\t
The number of processes that are currently running.
\n \n
\n\t
Processes Blocked
\n\t
The number of processes that are currently being blocked from running.
\n \n \n\t
Processes Waiting
\n\t
The number of processes that are currently waiting to runn.
\n \n \n\t
Workload - User
\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
Workload - Group
\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
Workload - Process Name
\n\t
The demand that network and local services are putting on a system, based on the processes that are running.
\n \n \n\t
Workload Top 10 - User
\n\t \n \n \n\t
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.
\n
Workload Top 10 - Group
\n\t
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.
\n
\n \n\t
Workload Top 10 - Process Name
\n\t
The 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 agent uses the following utilities to collect user information from an IRIX system:

...

 

  • ps -eo
    • \n
  • /usr/bsd/last /usr/bsd/head -10 (login history for the last 10 users on the system)
    • \n
  • /usr/bin/who (lists who is currently logged into the system)

 

\

...

t\

...

t\

...

t\

...

t\

...

t\t

Metric
\n\t
Explanation
\n
\n \n\t
Login History
\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\t
Sessions
\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