proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-06-15 10:00:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

metric server: style, grammar improvements

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2020-11-23 13:33:43 +01:00
parent 13180d0c14
commit 08e75d1ab0
1 changed files with 16 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
pve-external-metric-server.adoc
View File

@ -7,16 +7,16 @@ endif::wiki[]
[thumbnail="screenshot/gui-datacenter-metric-server-list.png"] [thumbnail="screenshot/gui-datacenter-metric-server-list.png"]
In {pve}, you can define external metric servers, which will In {pve}, you can define external metric servers, which will periodically
be sent various stats about your hosts, virtual machines and storages. receive various stats about your hosts, virtual guests and storages.
Currently supported are: Currently supported are:
* Graphite (see http://graphiteapp.org ) * Graphite (see http://graphiteapp.org )
* InfluxDB (see https://www.influxdata.com/time-series-platform/influxdb/ ) * InfluxDB (see https://www.influxdata.com/time-series-platform/influxdb/ )
The server definitions are saved in '/etc/pve/status.cfg', and can be edited The external metric server definitions are saved in '/etc/pve/status.cfg', and
through the GUI. can be edited through the web interface.
[[metric_server_graphite]] [[metric_server_graphite]]
Graphite server configuration Graphite server configuration
@ -24,15 +24,15 @@ Graphite server configuration
[thumbnail="screenshot/gui-datacenter-metric-server-graphite.png"] [thumbnail="screenshot/gui-datacenter-metric-server-graphite.png"]
The default port is set to *2003* and the default path is *proxmox*. The default port is set to *2003* and the default graphite path is *proxmox*.
{pve} sends the data over UDP, so the graphite server has to be configured By default, {pve} sends the data over UDP, so the graphite server has to be
for this. Here the MTU can be configured for environments which require configured to accept this. Here the maximum transmission unit (MTU) can be
a different mtu than the standard *1500*. configured for environments not using the standard *1500* MTU.
Alternatively, the plugin can be configured to use TCP instead with You can also configure the plugin to use TCP. In order not to block the
a timeout. Here the timeout is important, as to not block the stat generating important `pvestatd` statistic collection daemon, a timeout is required to cope
process forever. with network problems.
[[metric_server_influxdb]] [[metric_server_influxdb]]
Influxdb plugin configuration Influxdb plugin configuration
@ -40,13 +40,13 @@ Influxdb plugin configuration
[thumbnail="screenshot/gui-datacenter-metric-server-influxdb.png"] [thumbnail="screenshot/gui-datacenter-metric-server-influxdb.png"]
{pve} sends the data over UDP, so the influxdb server has to be configured {pve} sends the data over UDP, so the influxdb server has to be configured for
for this. The MTU can also be configured here, if necessary. this. The MTU can also be configured here, if necessary.
Here is an example configuration for influxdb (on your influxdb server): Here is an example configuration for influxdb (on your influxdb server):
---- ----
​[[udp]] [[udp]]
enabled = true enabled = true
bind-address = "0.0.0.0:8089" bind-address = "0.0.0.0:8089"
database = "proxmox" database = "proxmox"
@ -54,6 +54,5 @@ Here is an example configuration for influxdb (on your influxdb server):
batch-timeout = "1s" batch-timeout = "1s"
---- ----
With this configuration, your server listens on all IP addresses on With this configuration, your server listens on all IP addresses on port 8089,
port 8089, and writes the data in the *proxmox* database and writes the data in the *proxmox* database