5 results found
-
Migration-Aware Proxmox VE VM Monitoring: Automatically Track VMs Across Cluster Nodes
As a Systems Engineer running a Proxmox VE cluster,
I want PRTG's Proxmox VM monitoring to automatically detect and follow a virtual machine when it migrates to a different cluster node,
so that I receive accurate up/down status for the VM (including VMs I cannot monitor directly, e.g., in a DMZ) without false errors or manual sensor reconfiguration after routine host patching and migrations.4 votes -
Monitoring-status filter for SNMP interface selection when adding Traffic sensors
As a Network Engineer responsible for switch and bandwidth monitoring,
I want to filter the interface list in the SNMP sensor creation dialog by monitoring status — specifically to show only interfaces that do not yet have a sensor (and optionally hide those that do) —
so that I can quickly identify and add recently connected or overlooked ports without manually cross-checking the full interface list against existing sensors, avoiding both wasted time and accidental duplicate sensors.2 votes -
Document Required Windows Permissions per WMI Sensor (DCOM vs. WSMan) in the Sensor Manual Remarks
As a Systems Engineer setting up WMI-based sensors, I want each sensor’s manual page to list the specific Windows permissions and group memberships required (differentiated by DCOM and WSMan connection method where they differ) so that I can configure least-privilege monitoring credentials correctly on the first attempt instead of diagnosing permission failures through trial and error.
Background:
For sensors that retrieve data via WMI using WSMan, it appears that additional user permissions may be required depending on the type of monitoring performed.
For example, it took me some time to identify that the Event Log Readers group membership was required…1 vote -
Prevent Auto-Discovery from Creating a Ping v2 Sensor with Ping v1 Functionality
As a Network Engineer managing devices discovered via PRTG auto-discovery,
I want auto-discovery (including the default templates Generic Device (Ping Only) and Generic Device (SNMP Enabled)) to create ping sensors whose sensor type label matches their actual channel structure, settings, and documented functionality — i.e., a sensor labeled Ping v2 behaves as documented for Ping v2, or a sensor with Ping v1 behavior is labeled Ping v1,
so that I can trust that sensors were created correctly, reliably filter and manage sensors by type, and avoid wasting time investigating "broken" sensors that are actually just mislabeled.Background:
In PRTG 26.3.122.1665,…1 vote -
Proxmox Credential Placeholders for Custom Script Sensors
As a Systems Engineer monitoring Proxmox hypervisors with both native PRTG sensors and custom EXE/Script Advanced (PowerShell) sensors, I want the device-level "Credentials for Proxmox" fields (API Token ID, Secret, Port) to be available as placeholders (e.g., %proxmoxtokenid, %proxmoxtokensecret, %proxmoxport) in my script parameters, so that I maintain the API token in one single place and token rotation no longer requires redundant, error-prone updates across two credential sections.
Background:
We heavily rely on Custom EXE/Script Advanced Sensors (PowerShell) to monitor our hypervisors for specific metrics, like aging snapshots. While migrating to Proxmox, we noticed that we cannot pass the newly…1 vote
- Don't see your idea?