From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] metric server: remove whitespace in front of config section
Date: Mon, 10 Aug 2020 13:42:25 +0200 [thread overview]
Message-ID: <20200810114225.23205-1-a.lauterer@proxmox.com> (raw)
The leading whitespace in the first lines of the examples caused some
confusion and problems [0] because the config would not work with it.
Removing the whitespace will make it easier to copy and paste the
examples, causing less frustation and confusion.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
[0] https://forum.proxmox.com/threads/issue-setting-up-influxdb.70687
---
pve-external-metric-server.adoc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/pve-external-metric-server.adoc b/pve-external-metric-server.adoc
index c9e1107..4eadb2f 100644
--- a/pve-external-metric-server.adoc
+++ b/pve-external-metric-server.adoc
@@ -20,7 +20,7 @@ Graphite server configuration
The definition of a server is:
----
- graphite: your-id
+graphite: your-id
server your-server
port your-port
path your-path
@@ -37,7 +37,7 @@ Influxdb plugin configuration
The definition is:
----
- influxdb: your-id
+influxdb: your-id
server your-server
port your-port
----
@@ -48,7 +48,7 @@ for this.
Here is an example configuration for influxdb (on your influxdb server):
----
- [[udp]]
+[[udp]]
enabled = true
bind-address = "0.0.0.0:8089"
database = "proxmox"
@@ -68,14 +68,14 @@ type, then the ids must be defined and different from each other.
Here is an example of a finished status.cfg
----
- graphite:
+graphite:
server 10.0.0.5
- influxdb: influx1
+influxdb: influx1
server 10.0.0.6
port 8089
- influxdb: influx2
+influxdb: influx2
server 10.0.0.7
port 8090
----
--
2.20.1
next reply other threads:[~2020-08-10 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 11:42 Aaron Lauterer [this message]
2020-08-11 13:36 ` [pve-devel] applied + followup: " Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200810114225.23205-1-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox