Glances/man

glances - An eye on your system

INTERACTIVE COMMANDS

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

ENTER Set the process filter

NOTE: On macOS please use CTRL-H to delete filter.

The filter is a regular expression pattern:

• gnome: matches all processes starting with the gnome string

• .*gnome.*: matches all processes containing the gnome string

a Sort process list automatically

• If CPU >70%, sort processes by CPU usage

• If MEM >70%, sort processes by MEM usage

• If CPU iowait >60%, sort processes by I/O read and write

A Enable/disable the Application Monitoring Process

b Switch between bit/s or Byte/s for network I/O

B View disk I/O counters per second

c Sort processes by CPU usage

C Enable/disable cloud stats

d Show/hide disk I/O stats

D Enable/disable Docker stats

e Enable/disable top extended stats

E Erase the current process filter

f Show/hide file system and folder monitoring stats

F Switch between file system used and free space

g Generate graphs for current history

G Enable/disable GPU stats

h Show/hide the help screen

i Sort processes by I/O rate

I Show/hide IP module

+ Increase selected process nice level / Lower the priority (need right) - Only in standalone mode.

- Decrease selected process nice level / Higher the priority (need right) - Only in standalone mode.

k Kill selected process (need right) - Only in standalone mode.

K Show/hide TCP connections

l Show/hide log messages

m Sort processes by MEM usage

M Reset processes summary min/max

n Show/hide network stats

N Show/hide current time

p Sort processes by name

P Enable/Disable ports stats

q|ESC|CTRL-C Quit the current Glances session

Q Show/hide IRQ module

r Reset history

R Show/hide RAID plugin

s Show/hide sensors stats

S Enable/disable spark lines

t Sort process by CPU times (TIME+)

T View network I/O as a combination

u Sort processes by USER

U View cumulative network I/O

w Delete finished warning log messages

W Show/hide Wifi module

x Delete finished warning and critical log messages

z Show/hide processes stats

0 Enable/disable Irix/Solaris mode

The task’s CPU usage will be divided by the total number of CPUs

1 Switch between global CPU and per-CPU stats

2 Enable/disable the left sidebar

3 Enable/disable the quick look module

4 Enable/disable all but quick look and load module

5 Enable/disable the top menu (QuickLook, CPU, MEM, SWAP, and LOAD)

6 Enable/disable mean GPU mode

9 Switch UI theme between black and white

/ Switch between process command line or command name

F5 or CTRL-R Refresh user interface

LEFT Navigation left through the process sort

RIGHT Navigation right through the process sort

UP Up in the processes list

DOWN Down in the processes list

In the Glances client browser (accessible through the --browser command line argument):

ENTER Run the selected server

UP Up in the servers list

DOWN Down in the servers list

q|ESC Quit Glances

CONFIGURATION

No configuration file is mandatory to use Glances.

Furthermore, a configuration file is needed to access more settings.

LOCATION

NOTE: A template is available in the /usr{,/local}/share/doc/glances (Unix-like) directory or directly on GitHub.

You can place your glances.conf file in the following locations:

           ┌─────────────────────────────────────────────────┐
           │ Linux, SunOS:                  │
           │   ~/.config/glances/,             │
           │   /etc/glances/,               │
           │   /usr/share/docs/glances/          │
           │ *BSD:                      │
           │   ~/.config/glances/,             │
           │   /usr/local/etc/glances/,          │
           │   /usr/share/docs/glances/          │
           │ macOS:                     │
           │   ~/.config/glances/,             │
           │   ~/Library/Application Support/glances/,   │
           │   /usr/local/etc/glances/,          │
           │   /usr/share/docs/glances/          │
           │ Windows:                    │
           │   %APPDATA%\eglances\eglances.conf      │
           │ All:                      │
           │   <venv_root_folder>/share/doc/glances/    │
           └─────────────────────────────────────────────────┘

• On Windows XP, %APPDATA% is: C:\Documents and Settings\<USERNAME>\Application Data.

• On Windows Vista and later: C:\Users\<USERNAME>\AppData\Roaming.

User-specific options override system-wide options, and options given on the command line overrides both.

SYNTAX

Glances read configuration files in the ini syntax.

A first section (called global) is available:

[global]

1. Refresh rate (default is a minimum of 2 seconds)
2. Can be overwritten by the -t <sec> option
3. It is also possible to overwrite it in each plugin section

refresh=2

1. Should Glances check if a newer version is available on PyPI ?

check_update=true

1. History size (maximum number of values)
2. Default is 1200 values (~1h with the default refresh rate)

history_size=1200

1. Set the way Glances should display the date (default is %Y-%m-%d %H:%M:%S %Z)
2. strftime_format="%Y-%m-%d %H:%M:%S %Z"
3. Define external directory for loading additional plugins
4. The layout follows the glances standard for plugin definitions
5. plugin_dir=/home/user/dev/plugins

than a second one concerning the user interface:

[outputs]

1. Options for all UIs
2. --------------------
3. Separator in the Curses and WebUI interface (between top and others plugins)

separator=True

1. Set the the Curses and WebUI interface left menu plugin list (comma-separated)
2. left_menu=network,wifi,connections,ports,diskio,fs,irq,folders,raid,smart,sensors,now
3. Limit the number of processes to display (in the WebUI)

max_processes_display=25

1. Options for WebUI
2. ------------------
3. Set URL prefix for the WebUI and the API
4. Example: url_prefix=/glances/ => https://localhost/glances/
5. Note: The final / is mandatory
6. Default is no prefix (/)
7. url_prefix=/glances/
8. Set root path for WebUI statics files
9. Why ? On Debian system, WebUI statics files are not provided.
10. You can download it in a specific folder
11. thanks to https://github.com/nicolargo/glances/issues/2021
12. then configure this folder with the webui_root_path key
13. Default is folder where glances_restfull_api.py is hosted
14. webui_root_path=
15. CORS options
16. Comma separated list of origins that should be permitted to make cross-origin requests.
17. Default is *
18. cors_origins=*
19. Indicate that cookies should be supported for cross-origin requests.
20. Default is True
21. cors_credentials=True
22. Comma separated list of HTTP methods that should be allowed for cross-origin requests.
23. Default is *
24. cors_methods=*
25. Comma separated list of HTTP request headers that should be supported for cross-origin requests.
26. Default is *
27. cors_headers=*

Each plugin, export module, and application monitoring process (AMP) can have a section. Below is an example for the CPU plugin:

[cpu] disable=False refresh=3 user_careful=50 user_warning=70 user_critical=90 iowait_careful=50 iowait_warning=70 iowait_critical=90 system_careful=50 system_warning=70 system_critical=90 steal_careful=50 steal_warning=70 steal_critical=90

an InfluxDB export module:

[influxdb]

1. Configuration for the --export influxdb option
2. https://influxdb.com/

host=localhost port=8086 user=root password=root db=glances prefix=localhost

1. tags=foo:bar,spam:eggs

or a Nginx AMP:

[amp_nginx]

1. Nginx status page should be enabled (https://easyengine.io/tutorials/nginx/status-page/)

enable=true regex=\/usr\/sbin\/nginx refresh=60 one_line=false status_url=https://localhost/nginx_status

With Glances 3.0 or higher, you can use dynamic configuration values by utilizing system commands. For example, if you want to set the pre‐ fix of an InfluxDB export to the current hostname, use:

[influxdb] ... prefix=`hostname`

Or if you want to add the Operating System name as a tag:

[influxdb] ... tags=system:`uname -a`

LOGGING

Glances logs all of its internal messages to a log file.

DEBUG messages can be logged using the -d option on the command line.

The location of the Glances log file depends on your operating system. You can display the full path of the Glances log file using the glances -V command line.

The file is automatically rotated when its size exceeds 1 MB.

If you want to use another system path or change the log message, you can use your logger configuration. First of all, you have to create a glances.json file with, for example, the following content (JSON format):

{ "version": 1, "disable_existing_loggers": "False", "root": { "level": "INFO", "handlers": ["file", "console"] }, "formatters": { "standard": { "format": "%(asctime)s -- %(levelname)s -- %(message)s" }, "short": { "format": "%(levelname)s: %(message)s" }, "free": { "format": "%(message)s" } }, "handlers": { "file": { "level": "DEBUG", "class": "logging.handlers.RotatingFileHandler", "formatter": "standard", "filename": "/var/tmp/glances.log" }, "console": { "level": "CRITICAL", "class": "logging.StreamHandler", "formatter": "free" } }, "loggers": { "debug": { "handlers": ["file", "console"], "level": "DEBUG" }, "verbose": { "handlers": ["file", "console"], "level": "INFO" }, "standard": { "handlers": ["file"], "level": "INFO" }, "requests": { "handlers": ["file", "console"], "level": "ERROR" }, "elasticsearch": { "handlers": ["file", "console"], "level": "ERROR" }, "elasticsearch.trace": { "handlers": ["file", "console"], "level": "ERROR" } } }

and start Glances using the following command line:

LOG_CFG=<path>/glances.json glances

NOTE: Replace <path> with the directory where your glances.json file is hosted.