[GH-ISSUE #2] Add Metrics #3

Open
opened 2026-03-14 08:22:51 +03:00 by kerem · 0 comments
Owner

Originally created by @andrew-d on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/andrew-d/proxmox-service-discovery/issues/2

The service should expose metrics (likely Prometheus) on the debug port so that it's clearer if it's working as expected. Ideas:

  • Gauge with the last time we successfully fetched the Proxmox inventory
  • Gauge with number of discovered nodes/LXCs/VMs
  • Number of DNS requests, split by TCP/UDP and A/AAAA
  • Inventory fetch latency
  • Success/failure counters for fetching things from Proxmox (e.g. an inventory_fetch_failure metric with a reason attribute)
Originally created by @andrew-d on GitHub (Apr 5, 2025). Original GitHub issue: https://github.com/andrew-d/proxmox-service-discovery/issues/2 The service should expose metrics (likely Prometheus) on the debug port so that it's clearer if it's working as expected. Ideas: - [x] Gauge with the last time we successfully fetched the Proxmox inventory - [x] Gauge with number of discovered nodes/LXCs/VMs - [x] Number of DNS requests, split by TCP/UDP and A/AAAA - [ ] Inventory fetch latency - [ ] Success/failure counters for fetching things from Proxmox (e.g. an `inventory_fetch_failure` metric with a `reason` attribute)
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxmox-service-discovery#3
No description provided.