znerol

> but some metrics of the cluster will be duplicated. I have made changes to the process of collecting replication tasks status. Not sure what you mean by duplicated metrics....

I released `3.0.0` and also merged #198. This PR now needs a little refactoring for the new file layout.

Closing in favor of #243 (also credited @themoriarti over there for the original work).

Thanks for the report. What you are observing is the intended behavior. Prometheus PVE exporter collects metrics by scraping resources via the PVE [cluster](https://pve.proxmox.com/pve-docs/api-viewer/index.html#/cluster) API.

The `node` label is on the `pve_guest_info` metric. In order to make that available on any other metric, it is necessary to join it to `pve_guest_info`. E.g.: ``` pve_up *...

There is [prometheus-pve-sd](https://pypi.org/project/prometheus-pve-sd/). So maybe we do not need to implement that here at all.

Filled the form like this:  Might come in handy next time.

``` From: Open Source Project To: ... Subject: Welcome back to the Docker-Sponsored Open Source program! Date: Tue, 12 Mar 2024 05:08:28 +0000 (GMT) Sender: [email protected] ``` Dear ..., Congratulations!...

Thanks! This needs tests though. Current test vectors were extracted from the [reference implementation](http://isthe.com/chongo/src/fnv/test_fnv.c), but it does not look like that was updated for hash sizes `> 64bit`. I'm happy...

A preliminary caveat, this repository holds the artifacts produced during a students thesis. The only purpose of this work is to demonstrate that the algorithm discussed in the paper isn't...