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

followup: metric-server: formating, line length, and other small improvements

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2019-05-08 07:21:43 +00:00
parent 67360d5786
commit 0a3aed9c94
1 changed files with 19 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -4,53 +4,57 @@ ifdef::wiki[]
:pve-toplevel: :pve-toplevel:
endif::wiki[] endif::wiki[]
Starting with {pve} 4.0, you can define external metric servers, Starting with {pve} 4.0, you can define external metric servers, which will
which will be sent various stats about your hosts, virtual machines and storages. be sent various stats about your hosts, virtual machines 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 The server definitions are saved in '/etc/pve/status.cfg'
/etc/pve/status.cfg
Graphite server configuration Graphite server configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The definition of a server is: The definition of a server is:
----
graphite: your-id graphite: your-id
server your-server server your-server
port your-port port your-port
path your-path path your-path
----
where your-port defaults to *2003* where your-port defaults to *2003* and your-path defaults to *proxmox*
and your-path defaults to *proxmox*
{pve} sends the data over udp, so the graphite server {pve} sends the data over UDP, so the graphite server has to be configured
has to be configured for this for this.
Influxdb plugin configuration Influxdb plugin configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The definition is: The definition is:
----
influxdb: your-id influxdb: your-id
server your-server server your-server
port your-port port your-port
----
{pve} sends the data over udp, so the influxdb server {pve} sends the data over UDP, so the influxdb server has to be configured
has to be configured for this for this.
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"
batch-size = 1000 batch-size = 1000
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, and writes the data in the *proxmox* database port 8089, and writes the data in the *proxmox* database
@ -59,10 +63,11 @@ Multiple Definitions and Example
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The *id* is optional, but if you want to have multiple definitions of a single The *id* is optional, but if you want to have multiple definitions of a single
type, then the ids must be different. type, then the ids must be defined and different from each other.
Here is an example of a finished status.cfg Here is an example of a finished status.cfg
----
graphite: graphite:
server 10.0.0.5 server 10.0.0.5
@ -73,3 +78,4 @@ Here is an example of a finished status.cfg
influxdb: influx2 influxdb: influx2
server 10.0.0.7 server 10.0.0.7
port 8090 port 8090
----