From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common/storage/manager/docs] implement http api for influxdb status plugin
Date: Wed, 2 Dec 2020 10:21:03 +0100 [thread overview]
Message-ID: <20201202092113.15911-1-d.csapak@proxmox.com> (raw)
this series adds the possibility to write influxdb data via their
v2 api. For influxdb 1.x there is a forwards compatible api since 1.8.0
i am not so sure about how i integrated the http api part into the
existing influxdb plugin, another alternative would be to have
a new InfluxDB2 Plugin that does only http(s).
this way i could omit the permanent 'cfg->proto' check, but i am not
sure if we want to have a new plugin for this..
manager/storage patches depend on common, but the storage patch is not needed for
it to work
pve-common:
Dominik Csapak (1):
tools: add extract_sensitive_params
src/PVE/Tools.pm | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
pve-storage:
Dominik Csapak (1):
api: storage/config: use extract_sensitive_params from tools
PVE/API2/Storage/Config.pm | 29 ++++-------------------------
1 file changed, 4 insertions(+), 25 deletions(-)
pve-manager:
Dominik Csapak (7):
api: cluster/metricserver: prevent simultaneosly setting and deleting
of property
status/plugin: extend send/_connect/_disconnect/test_connection
status/plugin: extend with add/update/delete hooks
status/influxdb: implement influxdb 2.x http api
status/influxdb: remove unnecessary comment
ui: add necessary fields for influxdb http api
ui: dc/MetricServerView: add onlineHelp to edit windows
PVE/API2/Cluster/MetricServer.pm | 41 ++++-
PVE/ExtMetric.pm | 4 +-
PVE/Status/InfluxDB.pm | 222 ++++++++++++++++++++++++++--
PVE/Status/Plugin.pm | 38 ++++-
www/manager6/dc/MetricServerView.js | 105 ++++++++++++-
5 files changed, 375 insertions(+), 35 deletions(-)
pve-docs:
Dominik Csapak (1):
external metrics server: extend docs to explain http api
pve-external-metric-server.adoc | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
--
2.20.1
next reply other threads:[~2020-12-02 9:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 9:21 Dominik Csapak [this message]
2020-12-02 9:21 ` [pve-devel] [PATCH common 1/1] tools: add extract_sensitive_params Dominik Csapak
2020-12-03 8:47 ` Thomas Lamprecht
2020-12-03 9:16 ` Wolfgang Bumiller
2020-12-03 9:35 ` Thomas Lamprecht
2020-12-03 15:52 ` [pve-devel] applied: " Thomas Lamprecht
2020-12-02 9:21 ` [pve-devel] [PATCH storage 1/1] api: storage/config: use extract_sensitive_params from tools Dominik Csapak
2021-01-28 16:31 ` [pve-devel] applied: " Thomas Lamprecht
2020-12-02 9:21 ` [pve-devel] [PATCH manager 1/7] api: cluster/metricserver: prevent simultaneosly setting and deleting of property Dominik Csapak
2020-12-03 9:05 ` Thomas Lamprecht
2020-12-04 11:30 ` Dominik Csapak
2020-12-04 11:57 ` Thomas Lamprecht
2020-12-04 12:45 ` Thomas Lamprecht
2020-12-02 9:21 ` [pve-devel] [PATCH manager 2/7] status/plugin: extend send/_connect/_disconnect/test_connection Dominik Csapak
2020-12-02 9:21 ` [pve-devel] [PATCH manager 3/7] status/plugin: extend with add/update/delete hooks Dominik Csapak
2020-12-02 9:21 ` [pve-devel] [PATCH manager 4/7] status/influxdb: implement influxdb 2.x http api Dominik Csapak
2020-12-02 9:21 ` [pve-devel] [PATCH manager 5/7] status/influxdb: remove unnecessary comment Dominik Csapak
2020-12-02 9:21 ` [pve-devel] [PATCH manager 6/7] ui: add necessary fields for influxdb http api Dominik Csapak
2020-12-02 9:21 ` [pve-devel] [PATCH manager 7/7] ui: dc/MetricServerView: add onlineHelp to edit windows Dominik Csapak
2020-12-02 9:21 ` [pve-devel] [PATCH docs 1/1] external metrics server: extend docs to explain http api Dominik Csapak
2021-01-28 16:36 ` [pve-devel] applied-series: [PATCH common/storage/manager/docs] implement http api for influxdb status plugin Thomas Lamprecht
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=20201202092113.15911-1-d.csapak@proxmox.com \
--to=d.csapak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal