9 Commits

Author SHA1 Message Date
justin 7a45a9c49a Add VmSourceVRA label and resolve VRA names for VM metrics
- Add VmSourceVRA to _VM_LABELS, populated from vm['OwningHostName']
  resolved to a VRA name via a host→VRA lookup built from zvm.vras()
- VmRecoveryVRA now also resolves to the actual VRA name (e.g.
  Z-VRA-192.168.50.21) instead of the raw ESXi host IP
- Cloud-target VPGs (Azure/AWS) correctly emit VmRecoveryVRA="" since
  there is no local VRA on the recovery side
- Bump version to 3.1.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-21 11:39:35 -05:00
justin 1f591e20ef Bump version to 3.0.0 and remove leaked PyPI token
- Version bumped to 3.0.0 to reflect breaking changes: dropped zvma9_7,
  switched to prometheus_client + JSON stdout logging, removed legacy packages
- Remove app/.pypirc (contained leaked PyPI token, now gitignored)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-20 19:55:19 -05:00
justin a0ac6883f4 updates for zvma10 2024-05-30 20:57:39 -04:00
justin 0911a4eccc zvma10 wrapper module
Created a python module that has everything needed for comms with ZVMA version 10 in a seperate class. It does not have full api coverage, but is enough to start refactoring the exporter to use the class for ZVMa10
2023-12-08 11:05:50 -05:00
justin 48dc444166 dev updates
Not finished, but pushing for use on another machine
2023-10-24 19:52:09 -04:00
justin 94a3822353 multi-site readiness and VRA CPU and Memory
Added Site ID and Site Name to every metric. Moved all VRA metrics to a separate thread and started collecting VRA CPU and Memory usage from vCenter API.
2023-03-23 08:01:21 -04:00
justin 0688fe6aab exception handling and comments 2023-03-22 23:27:22 -04:00
justin 78943bf5f6 fixed version dunder 2023-03-20 19:37:41 -04:00
justin 84fa3d207d Added versioning 2023-03-20 19:21:45 -04:00