@olivierlambert Uh very nice now I got something to play with in the evening I'll let you know once I've created a PoC
Posts made by jmara
-
RE: Prometheus SD through REST API
-
RE: Prometheus SD through REST API
@olivierlambert As said, I would be a starting point if the fields of the
/vms
call will be extended to include ipaddesses, pool_name/id and maybe host_affinity -
RE: Prometheus SD through REST API
@olivierlambert sure its a new service discovery plugin in the prometheus core which scrapes http endpoints:
https://prometheus.io/docs/prometheus/latest/http_sd/It requires this json format:
[ { "targets": [ "<host>", ... ], "labels": { "<labelname>": "<labelvalue>", ... } }, ... ]
-
Prometheus SD through REST API
Hi,
I was wondering if we could get a REST API Endpoint to discover vms via the prometheus build-in http_sd?
As a starting point it would be nice the get the ips and pool association of vms through the
/vms
call so that it would be possible to write a wrapper script to match the http_sd format.Or is this possible and I haven't found the correct fields yet?
Cheers,
Jan -
RE: vCPU overcommitment stats
@olivierlambert ah good to know thats fine I'll take a look at the metrics maybe I'll write a small rrd stats pusher script as an interim solution for my usecase until XO6 is available.
Thanks for letting me know
-
RE: vCPU overcommitment stats
@olivierlambert I'll check later this afternoon, as the loads keeps increasing through the day and let you know if the counter moves.
Should I file a feature request for XOA as support ticket to get the counter into the stats section? Might be an interesting counter for others as well.
-
RE: vCPU overcommitment stats
@olivierlambert yeah i thought so too is there any way to visualize this in XOA/netdata?
-
vCPU overcommitment stats
Hi,
I'm trying to get some metrics and info about CPU overcommitment and if there are hosts in my cluster which are fairly unbalanced (not in a configuration kind of way, but where vms fighting to get CPU time).
I've read that other Hypervisors show this kind of data as "CPU ready" counter and that the Xen equivalent should be "runstate_full_contention" (Fraction of time that all vCPUs are runnable (that is, waiting for CPU)). Sadly this counter does not seem to move in my xen center and the netdata plugin does not track the value.
Does anyone have more info around that topic?
Cheers,
Jan