znerol

Use the `target` url parameter to specify the target PVE host. See the readme and the wiki for more docs.

Metrics for nodes, VMs and containers are gathered via the PVE API. See the [docs](https://pve.proxmox.com/pve-docs/api-viewer/#/cluster/resources) for all the values which are available. You can also check what is available from...

Thanks for this feature request. This seems like an interesting idea. The API documentation for the [pools](https://pve.proxmox.com/pve-docs/api-viewer/index.html#/pools/{poolid}) endpoint regrettably is quite sparse. But judging from the [go-proxmox source](https://github.com/luthermonson/go-proxmox/blob/fe3dbec855e9bef20dd2284f7dcc4df041cc07ba/types.go#L1005-L1011), there should...

Thanks for the report. I haven't found any of those in my logs yet. That said, I'm not too happy on how the application hard codes gunicorn internals. On the...

Ok, good to know.

> To maintainers: The metric type should probably be counter instead of gauge. And the metric should have _total suffix. This is true. PR welcome. Add the counters and deprecate...

My current workaround to avoid the race is this: Add a file to the project with the following content (name it something like `_autoload-otel.php`): ```php

Thank you for filing this PR. I'm not too happy with the metric structure though. This project follows the common practice of exposing an `X_info` gauge with a complete set...

I think this should be doable via `pve.yml`. All config under the module is passed to proxmoxer directly. And it looks like the [HTTP Backend](https://github.com/proxmoxer/proxmoxer/blob/develop/proxmoxer/backends/https.py#L45) takes a `timeout` parameter which...

That would be a typical use case for [tracing](https://opentelemetry.io/docs/concepts/signals/traces/). I have some experience with that but not yet with python apps.