-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gettting metrics from ALL guest instead of the selected instance #204
Comments
Thanks for the report. What you are observing is the intended behavior. Prometheus PVE exporter collects metrics by scraping resources via the PVE cluster API. |
Ok thank you! |
The
More examples in #54 and detailed explanation of joins in the robust perception blog. |
So the solution was for me to make this
|
by the way I did not find a way to get the cpu usage ratio for the whole cluster... I tried to sum all the |
For whole cluster, maybe you can try to using this
|
That was the trick thanks!!!
…On Tue, Dec 26, 2023, 05:27 Agnesius Santo Naibaho ***@***.***> wrote:
by the way I did not find a way to get the cpu usage ratio for the whole
cluster... I tried to sum all the pve_cpu_usage_ratio but that does not
really work in the gauge, it gives a gigantic percentage
For whole cluster, maybe you can try to using this
avg(pve_cpu_usage_ratio * on (id) group_left (name) pve_node_info)
—
Reply to this email directly, view it on GitHub
<#204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASJCUT2GFMIHZKSY2EUKE43YLJGZ5AVCNFSM6AAAAABABRJVBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGI2DINJSGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm having the exporter installed on prometheus host.
I using the prometheus config provided in the doc. I can collect the metrics and render them on the dashboard provided as a link.
In the target I put the IP of ONE proxmox host I want to get the metrics from ( 1 out of 24)
But for some magic reason, I'm getting ALL guests metrics, including the ones that are NOT on that proxmox host!
And filtering does not work of course
The text was updated successfully, but these errors were encountered: