Standalone mode

Simply run:

$ glances

Client/Server mode

If you want to remotely monitor a machine, called server, from another one, called client, just run on the server:

server$ glances -s

and on the client:

client$ glances -c @server

where @server is the IP address or hostname of the server.

In server mode, you can set the bind address -B ADDRESS and listening TCP port -p PORT.

In client mode, you can set the TCP port of the server -p PORT.

Default binding address is 0.0.0.0 (Glances will listen on all the network interfaces) and TCP port is 61209.

In client/server mode, limits are set by the server side.

You can also set a password to access to the server -P password.

Glances is IPv6 compatible. Just use the -B ::1 option to bind to all IPv6 addresses.

Command-line options

Interactive commands

The following commands (key pressed) are supported while in Glances:

a

Automatic mode. The processes are sorted automatically.

• If CPU iowait >60%, sort processes by IO read and write
• If CPU >70%, sort processes by CPU usage
• If MEM >70%, sort processes by memory usage

b

Switch between bit/s or Byte/s for network IO

c

Sort processes by CPU%

d

Show/hide disk I/O stats

f

Show/hide file system stats

h

Show/hide the help message (with the keys you can press and the limits)

i

Sort processes by IO rate (need root account on some OS)

l

Show/hide log messages

m

Sort processes by MEM%

n

Show/hide network stats

p

Sort processes by name

s

Show/hide sensors stats (only available with -e flag; pysensors library is needed; Linux-only)

t

View network IO as combination

u

View cumulative network IO

w

Delete finished warning log messages

x

Delete finished warning and critical log messages

1

Switch between global CPU and per-CPU stats

q

Quit

Legend

Header

The header shows the OS name, release version, platform architecture and the hostname. On Linux, it shows also the kernel version.

CPU

Short view:

If enough horizontal space is available, extended CPU informations are displayed.

Extended view:

To switch to per-CPU stats, just hit the 1 key:

The CPU stats are shown as a percentage and for the configured refresh time. The total CPU usage is displayed on the first line.

Note: limit values can be overwritten in the configuration file under the [cpu] section.

Load

On the No Sheep blog, Zachary Tirrell defines the average load [1]:

"In short it is the average sum of the number of processes waiting in the run-queue plus the number currently executing over 1, 5, and 15 minute time periods."

Glances gets the number of CPU core to adapt the alerts. Alerts on average load are only set on 5 and 15 min. The first line also display the number of CPU core.

Note: limit values can be overwritten in the configuration file under the [load] section.

Memory

Glances uses two columns: one for the RAM and another one for the Swap.

If enough space is available, Glances displays extended informations:

With Glances, alerts are only set for on used memory and used swap.

Note: limit values can be overwritten in the configuration file under the [memory] and [swap] sections.

Network

Glances displays the network interface bit rate. The unit is adapted dynamically (bits per second, kbits per second, Mbits per second, etc).

Alerts are only set if the network interface maximum speed is available.

For example, on a 100 Mbps ethernet interface, the warning status is set if the bit rate is higher than 70 Mbps.

Sensors

Glances can displays the sensors informations trough lm-sensors (only available on Linux) and hddtemp daemon.

As of lm-sensors, a filter is processed in order to display temperature only.

To enable the lm-sensors module:

$ glances -e

To enable the hddtemp module:

$ glances -y

There is no alert on this information.

Note: limit values can be overwritten in the configuration file under the [temperature] and [hddtemperature] sections.

Disk I/O

Glances displays the disk I/O throughput. The unit is adapted dynamically.

There is no alert on this information.

File system

Glances displays the used and total file system disk space. The unit is adapted dynamically.

Alerts are set for used disk space:

Note: limit values can be overwritten in the configuration file under [filesystem] section.

Processes list

Compact view:

Full view:

Three views are available for processes:

• Processes summary
• Optional monitored processes list (new in 1.7)
• Processes list

By default, or if you hit the a key, the processes list is automatically sorted by CPU of memory usage.

Note: limit values can be overwritten in the configuration file under the [process] section.

The number of processes in the list is adapted to the screen size.

VIRT

Virtual memory size

RES

Resident memory

CPU%

% of CPU used by the process

MEM%

% of MEM used by the process

PID

Process ID

USER

User ID per process

NI

Nice level of the process

S

Process status

TIME+

Cumulative CPU time used

IOR/s

Per process IO read rate (in Byte/s)

IOW/s

Per process IO write rate (in Byte/s)

NAME

Process name or command line

Process status legend:

R

running

S

sleeping (may be interrupted)

D

disk sleep (may not be interrupted)

T

traced/stopped

Z

zombie

Monitored processes list

New in version 1.7. Optional.

The monitored processes list allows user, through the configuration file, to group processes and quickly show if the number of running process is not good.

Each item is defined by:

• description: description of the processes (max 16 chars).
• regex: regular expression of the processes to monitor.
• command (optional): full path to shell command/script for extended stat. Should return a single line string. Use with caution.
• countmin (optional): minimal number of processes. A warning will be displayed if number of processes < count.
• countmax (optional): maximum number of processes. A warning will be displayed if number of processes > count.

Up to 10 items can be defined.

For example, if you want to monitor the NGINX processes on a Web server, the following definition should do the job:

[monitor]
list_1_description=NGINX server
list_1_regex=.*nginx.*
list_1_command=nginx -v
list_1_countmin=1
list_1_countmax=4

If you also want to monitor the PHP-FPM daemon processes, you should add another item:

[monitor]
list_1_description=NGINX server
list_1_regex=.*nginx.*
list_1_command=nginx -v
list_1_countmin=1
list_1_countmax=4
list_1_description=PHP-FPM
list_1_regex=.*php-fpm.*
list_1_countmin=1
list_1_countmax=20

Logs

A log messages list is displayed in the bottom of the screen if (and only if):

• at least one WARNING or CRITICAL alert was occurred
• space is available in the bottom of the console/terminal

Each alert message displays the following information:

1. start date
2. end date
3. alert name
4. {min/avg/max} values (or monitored processes list description)

Footer

Glances displays the current date & time and access to the embedded help screen.

If you have ran Glances in client mode -c, you can also see if the client is connected to the server.

If client is connected:

else:

On the left, you can easily see if you are connected to a Glances server.