From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-user@lists.proxmox.com, sam@lorch.net
Subject: Re: [PVE-User] Cluster Status Missing From External Metric Server Metrics
Date: Fri, 15 Jan 2021 10:12:34 +0100 [thread overview]
Message-ID: <1610701788.cjsty5xk9w.astroid@nora.none> (raw)
In-Reply-To: <9deb517da529b746fed36bd69d7895c6@lorch.net>
On January 15, 2021 8:59 am, Samuel Lorch wrote:
> Dear all,
>
> recently i have deployed allot of small Proxmox VE Clusters which now
> have a need for Monitoring. I have used Influx and Grafana to monitor
> Containers and VM's in the past and was very surprised to see that the
> External Metric Server doesn't supply any Metrics about the Cluster
> status (eg if quorate, number of votes, ...) even though this data is
> available in the api (pvesh get /cluster/ha/status/current or pvesh get
> /cluster/ha/status/manager_status). After investigating the source a bit
> with my limited knowledge of perl i think that all needed librarys
> already exists and that one could with very low effort add this data to
> the External Metric Servers Metrics.
>
> Is there a reason why these Metrics aren't exposed here or has this just
> been forgotten about?
likely the latter
>
> Is this something that the Proxmox team could implement?
yes. might be worth opening an enhancement request over at
https://bugzilla.proxmox.com
not that for clusters, corosync also provides quite some metrics via
corosync-cmapctl -m stats that might be interesting to pick up as well..
>
> This would make the External Metric Server a good & simple option for
> Monitoring Clusters as nothing has to be installed on the Hosts
> themselves and its now Configurable via the GUI.
>
> Thanks in advance
> Samuel
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
>
prev parent reply other threads:[~2021-01-15 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 7:59 Samuel Lorch
2021-01-15 9:12 ` Fabian Grünbichler [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=1610701788.cjsty5xk9w.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=sam@lorch.net \
/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.