Linux Server performance monitoring tool glances installation process and brief introduction

First, glances:

glances is a very good cross-platform performance monitoring tool that provides CPU, CPU queue, memory, virtual memory, network, I/O, and the list of processes that most occupy the server's resources.

Indicator monitoring information, and at run time depending on the resource usage of different color labeling its importance, very intuitive, the following are in use:

Second, glances installation:

Glances installation is relatively simple and convenient, because glances is written by Python, preferably Python's Library management tool PIP from the installation. and using tools

The installation process is also simple.

The systems supported by glances are: CentOS, Linux, Windows, Mac OX there seems to be something else here that I used to share:

CentOS 6.4 64bit: Note Using the root account and updating the Yum data:

# RPM-IVH http://fr2.rpmfind.net/linux/epel/6/x86_64/epel-release-6-7.noarch.rpm #  #  pip-python Install glances

Ubuntu: In addition to the second line to do a description, originally I do not too understand its meaning, to check the next "Python-pip will not talk about, Python package management tools; build-essential compiled A/C + + program, Python-dev is a python development kit. 】

# sudo apt-get update # sudo apt-get install python-pip build-essential python-dev # sudo pip install glances

Third, the use of glances:

Glances I looked at the official website of the document, there are four main ways, here are some of the words:

The first : Single use, this is very simple to use, log on to the server, or in the local command-line mode to run:

# glances

Note that I use the SSH link tool is securecrt, when using glances encountered some problems, the default settings will be wrong to run the next time, use the following settings for normal use:

The second type: client mode, assuming that there are two servers that have glances installed, A and B, and B with an IP address of 192.168.1.117, then:

First, use the following command on Server B as the monitored side:

# glances-s

Then use the following command on server A as the monitor side:

# glances-c 192.168.1.117

The test will display Server B's monitoring information on Server A

In addition, the official website uses the concept of the document, which is said to be the server side of the monitoring side (server), and the monitoring side as the client.

In addition, some commonly used parameter description, basically is the official translation of the document.

On the monitored side, the server side, you can use the- B address to bind the addresses with the TCP port specified with- p port for listening .

On the monitor side, which is the client, you can also use the-p port to specify the port used by the server .

If you need to set a password to connect to the server, you can use --password.

Note The default binding address is 0.0.0.0 (glances listens on all network interfaces) and the default TCP port is 61209 ( If you do not specify a port, make sure that the port is accessible from the firewall ...). ).

Either on the server or the client, the restrictions are set on the server side.

Third: Export glances monitoring data to CSV to generate graphs using other software, if you want to do this you can use the following command:

$ glances--output-csv/tmp/glances.csv

This is relatively simple, add a point, export CSV can specify the path, so it is much easier to find

Fourth: Finally, the use of Glances provides the API when the glances run can be real-time access to server monitoring data, so that more customized performance data can be analyzed.

Performances test is definitely a big weapon ah, and if it is a distributed cluster, it can also be used in this way to monitor more than one server.

This has not yet been tried, and intends to write another supplement using Glances's API to supplement

Four, the final description of some of the glances in the rules of labeling:

GreenRepresented by"OK"BlueRepresented by"Careful"Purplish RedRepresented by"WARNING"RedRepresented by"CRITICAL"In addition, the rules for the color display of the monitoring data are available within the configuration items. Read more about Yourself official documents: https://github.com/nicolargo/glances/blob/master/docs/glances-doc.rst#glances