This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
nethserver-glances [2015/05/03 16:38] stephdl |
nethserver-glances [2019/06/05 19:48] (current) |
||
---|---|---|---|
Line 7: | Line 7: | ||
see https:// | see https:// | ||
- | Add my repository | + | Add my repository, [[nethserver|see how to do it]] |
- | + | ||
- | yum install http:// | + | |
then install the module | then install the module | ||
- | yum install nethserver-glances--enablerepo=stephdl | + | yum install nethserver-glances --enablerepo=stephdl |
after that you need to launch the sensor detection | after that you need to launch the sensor detection | ||
sensors-detect | sensors-detect | ||
+ | |||
+ | ==== Usage ==== | ||
+ | <WRAP center round important 60%> | ||
+ | For now there is no way to protect the Glances browser by a password, when this option will be available then I will implement it. Therefore Glances is accessible by the browser **only** from the local network. If it is an issue, then you can disable the service glances as written below, only the glances CLI will stay workable (launch it by ' | ||
+ | </ | ||
After the installation the service which control the web interface is launched, if you want to control it | After the installation the service which control the web interface is launched, if you want to control it | ||
Line 25: | Line 28: | ||
can be also {restart, | can be also {restart, | ||
- | or you can use the neth way (enabled/ | + | or you can use the neth way (enabled/ |
config setprop glances status disabled | config setprop glances status disabled | ||
Line 32: | Line 35: | ||
each time you launch that signal-event, | each time you launch that signal-event, | ||
- | see config db | + | you can see the internal configuration database |
# config show glances | # config show glances | ||
Line 40: | Line 43: | ||
status=enabled | status=enabled | ||
- | The purpose is to see in direct the server activities (you can see raid, disk IO, sensors, bandwithd, memory, docker, ....) | + | once you have modified a property you need to launch a signal-event : |
- | Well a lot of good stuffs. | + | * Private/ |
- | + | by default glances | |
- | In order to use it go to Dashboard-> | + | if you want to modify |
- | + | | |
- | **in order to disable the glances | + | |
+ | *in order to disable the glances web interface (and continue to use the CLI) | ||
+ | if you want to modify it (enabled|disabled) | ||
config setprop glances status disabled | config setprop glances status disabled | ||
signal-event nethserver-glances-update | signal-event nethserver-glances-update | ||
- | **You can change the default TCP port** | + | |
+ | if you want to modify it | ||
config setprop glances TCPPort 55555 | config setprop glances TCPPort 55555 | ||
signal-event nethserver-glances-update | signal-event nethserver-glances-update | ||
+ | | ||
+ | The purpose is to see in direct the server activities (you can see raid, disk IO, sensors, bandwithd, memory, docker, ....) | ||
- | sources : http:// | + | Well a lot of good stuffs. |
+ | In order to use it go to Dashboard-> | ||
+ | |||
+ | |||
+ | |||
+ | sources : https:// | ||
+ | ==== Issues ==== | ||
+ | |||
+ | Please raise Issues on [[https:// | ||
==== RPM from epel ==== | ==== RPM from epel ==== | ||
collectd | collectd | ||
Line 63: | Line 78: | ||
hddtemp | hddtemp | ||
python-pip | python-pip | ||
+ | pwauth | ||
+ | mod_authnz_external | ||
+ | {{tag> |