From: Alexandre DERUMIER <aderumier@odiso.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Telegraf added in-built Proxmox support - thoughts versus our external metric support?
Date: Mon, 7 Sep 2020 15:47:46 +0200 (CEST) [thread overview]
Message-ID: <532694180.424495.1599486466603.JavaMail.zimbra@odiso.com> (raw)
In-Reply-To: <fffdf263-4b5b-b02e-a8da-7b123075e37a@proxmox.com>
Hi,
>>Anyway, I do not think that we should drop our direct plugins (yet), some
>>people like me, are happy feeding directly to InfluxDB without anything
>>in-between.
me too ;)
I'm not sure, but I think than we send more metrics to influxdb, than we stream through the cluster.
and the plugin does seem to use /cluster/resources api, but seem to do 1 api request by vm.
(So with a lot of vm, maybe it'll flood the api)
----- Mail original -----
De: "Thomas Lamprecht" <t.lamprecht@proxmox.com>
À: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>, "Victor Hooi" <victorhooi@yahoo.com>
Envoyé: Lundi 7 Septembre 2020 08:57:31
Objet: Re: [pve-devel] Telegraf added in-built Proxmox support - thoughts versus our external metric support?
Hi,
On 07.09.20 03:42, Victor Hooi wrote:
> I know that Proxmox has it's own inbuilt InfluxDB client:
>
> https://pve.proxmox.com/wiki/External_Metric_Server
>
> However, Telegraf recently added first-party support for Proxmox:
>
> https://github.com/influxdata/telegraf/tree/master/plugins/inputs/proxmox
great!
> Telegraf lets you output to InfluxDB, Graphite, Prometheus, as well as a
> bunch of others (Telegraf in-built output clients
> <https://github.com/influxdata/telegraf/tree/master/plugins/outputs>)
>
> What do you think of using the above and contributing to that, instead of
> maintaining our own Proxmox InfluxDB support?
>
> Or are there advantages to maintaining our own code here?
The pvestatd, which queries statistics periodically, does also the sending
of said statistics without extra overhead. API request may get, at least
partially, up to date information with an extra overhead, e.g., if storage
stats are to be queried too. That could be addressed by providing a pvestatd
fed cache in /run (fast memory tmpfs) or so and provide access to that over
the API.
Anyway, I do not think that we should drop our direct plugins (yet), some
people like me, are happy feeding directly to InfluxDB without anything
in-between.
But, we definitively want to mention this in the documentation and see how
we can improve integration.
cheers,
Thomas
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2020-09-07 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUJMy_HFbYmceV5s+kN8j=3_0K0SPqn9NramQxnePvAJyw.ref@mail.gmail.com>
2020-09-07 1:42 ` Victor Hooi
2020-09-07 6:57 ` Thomas Lamprecht
2020-09-07 13:47 ` Alexandre DERUMIER [this message]
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=532694180.424495.1599486466603.JavaMail.zimbra@odiso.com \
--to=aderumier@odiso.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