13 results found
-
Redfish Temperature Sensor
As a PRTG user, I want to monitor individual temperature readings from any Redfish-compliant server (HPE, Dell, Lenovo, Supermicro, etc.) — one sensor instance per temperature probe — so that I get granular thermal visibility and per-sensor alerting.
5 votesThe sensor was released in PRTG 26.3.124 today. Please update your system and try the new sensor. Thanks.
-
Proxmox VE sensor
As an IT Administrator who is moving off VMWare I would like to monitor Proxmox so that I have the metrics from the software which I am using today with my current virtualization sensors.
60 votes -
Enable PowerShell 7 Support for PRTG Custom Sensors
As a Systems Engineer/IT Administrator, I want to use PowerShell 7 as the execution environment for PRTG custom sensors so that I can leverage modern PowerShell features, improve script performance, and eliminate compatibility workarounds in my monitoring solutions.
25 votesThe feature was released in PRTG 26.3.124 today. Check the release notes at https://www.paessler.com/prtg/history/stable, update your system and try Powershell 7 with the Script v2 sensor. Thanks.
-
Kerberos authentication for Windows systems monitoring
Enabling Kerberos authentication for Windows sensors streamlines the authentication process while enhancing security and ensuring compliance with organizational security policies.
https://uservoice.paessler.com/discovery/roadmap/feature/159468
28 votes -
Redfish Fan State sensor
As a PRTG user, I want a single sensor per server (HPE, Dell, Lenovo, Supermicro, etc.) that monitors all fans via Redfish, so that I get a consolidated view of fan health and speeds without cluttering my device tree with one sensor per fan.
1 voteThe sensor was released in PRTG 26.3.124 today. Please update your system and try the new sensor. Thanks.
-
VEEAM 13 Backupjob Status Sensor
With the integration of VEEAM version 13, it is no longer possible to use the existing “backup job status sensors,” and you have to go to the trouble of building your own custom sensors to interact with PowerShell 7, which is only partially supported by PRTG. Native VEEAM sensors would be desirable here again.
2 votes -
Add Numeric Value Extraction to SNMP Custom String v2 Sensor
As a Network Engineer, I want the SNMP Custom String v2 Sensor to support Numeric Value Extraction (just like the legacy SNMP Custom String Sensor), so that I can extract and log numeric values from SNMP string responses (e.g., '25C') and use them for graphing, alerting, and trend analysis in PRTG.
2 votes -
Add support for SNMPv3 authNoPriv mode in PRTG
As a network engineer managing devices from ISPs and vendors with restricted SNMP configurations, I want PRTG to support SNMPv3 authNoPriv mode (authentication without encryption) so that I can monitor critical infrastructure devices that only allow this security level.
Currently, PRTG only supports SNMPv3 with authPriv (authentication + encryption). Many providers, e.g. Telekom, only offer SNMPv3 in authNoPriv mode.
Example configuration (as provided by Telekom, not changeable):
Mode: authNoPriv
Authentication Protocol: MD5
Privacy (Encryption): NoneSince PRTG does not support authNoPriv, monitoring such devices is currently impossible.
6 votes -
Configure channel limits when using Script V2
I would like to be able to set limits per channel in code when using the Script V2 Python sensor. This used to be possible with the Python Advanced sensor by adding attributes such as the following when adding the channel to the result JSON in Python:
islimitmode=True,
limitminerror=10,
limitmaxerror=90,
limiterrormsg="Percentage too high".I have attached the full Python Advanced sensor example where the excerpt above was taken from.
5 votes -
Stratum level channel for the SNTP Sensor
As a sysadmin I would like to see the stratum level as integer in the SNTP sensor. That way I can set limits/alerts on it when the required stratum level is not reached.
The correct stratum level is important for synchronisation of time on different machines.7 votes -
WMI Service sensor
As user I want to use the WMI Service sensor with an account which has only read access as long as I use the option "Do not start/restart the service (default)".
Because the WMI Service sensor has an option to restart the service in case it is not running, the user account for this sensor must be a write user. For optimal security I might want to use read-only accounts for monitoring. This would render the WMI restart option nonfunctional but allow me to not provide PRTG write access just to monitor the running status of a Windows service.
8 votes -
SSH Sensors on multi-platform probe
As a unix system administrator I would like to capture performance metrics via Secure Shell (SSH) so that I can avoid running additional daemons.
1 vote -
SSH Script v2 sensor
Provide an updated version of the SSH Script sensor. The new SSH Script v2 comes with the same benefits as the previous version:
- Versioned script output format for reliable updates
- Enhanced error handling
- Well-defined JSON schema for validation
1 vote
- Don't see your idea?