Add --pve.max-concurrent flag to spec

Configurable bounded concurrency for per-node API fan-out,
defaulting to 5.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Davíð Steinn Geirsson 2026-03-20 11:02:21 +00:00
parent 154a46f3cf
commit 5196a441ef

View file

@ -79,7 +79,7 @@ type ResourceAwareCollector interface {
3. Node list and resources data are passed to collectors that need them
4. All collectors run in parallel
5. Per-node API calls within collectors (subscription, replication, node_config)
are parallelized across nodes with bounded concurrency (5 concurrent requests)
are parallelized across nodes with bounded concurrency (`--pve.max-concurrent`)
6. Framework measures duration, catches errors, emits scrape meta-metrics
### API Client
@ -125,6 +125,7 @@ pve-exporter \
| `--pve.api-token` | — | API token string (mutually exclusive with token-file) |
| `--pve.token-file` | — | Path to file containing API token |
| `--pve.tls-insecure` | `false` | Disable TLS certificate verification |
| `--pve.max-concurrent` | `5` | Max concurrent API requests for per-node fan-out |
| `--web.listen-address` | `:9221` | Address to listen on |
| `--web.telemetry-path` | `/metrics` | Path for metrics endpoint |
| `--log.level` | `info` | Log level (debug, info, warn, error) |