57 results found
-
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.
53 votes -
Dynamic Interface Naming with ifIndex-Based Port Identification for SNMP Traffic Sensors
As a Network Engineer, I want PRTG SNMP Traffic sensors to dynamically update interface descriptors (ifAlias, ifDesc, ifName) on every scanning interval while using ifIndex as the primary immutable identifier for port identification, so that sensor names remain accurate and searchable when network device interface descriptions are changed through configuration management.
In cases where ifAlias, ifDesc, and ifName are used in port name templates, PRTG SNMP Traffic sensors should always pull these values and update them.
ifIndex should be used by default to identify the ports and the other OIDs should be used as dynamically updating fields on every scanning…
15 votes -
Native F5 BIG-IP Sensors
As a Network Engineer, I want native F5 BIG-IP sensors (BIG-IP 17.x): LTM Nodes, Pools, Pool Members, Virtual Servers, and System sensors (CPU, Interface, Disk, Cluster). These sensors must auto-discover objects and create channels dynamically.
Customer Need:
Native, out‑of‑the‑box PRTG sensors for F5 BIG‑IP devices, designed similarly to other vendor-specific sensor types (e.g., FortiGate, HPE, NetApp).
These sensors should provide intelligent auto‑discovery and automatic channel creation, instead of requiring SNMP Custom sensors.We expect sensor types that automatically detect and monitor:
A. LTM Object Sensors (from LOCAL-MIB)
Each of these should be a dedicated native sensor type:F5 LTM Nodes…
7 votesHi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
-
Cisco ACI sensor
As an Enterprise Network Administrator managing Cisco ACI infrastructure I want a dedicated Cisco ACI sensor in PRTG so that I can monitor the health, performance, and status of my Application Centric Infrastructure fabric without needing separate monitoring tools or complex custom scripts.
Background:
With the increasing adoption of software-defined networking and the complexity of modern data center environments, customers using Cisco ACI need comprehensive monitoring capabilities. Currently, monitoring ACI requires either expensive third-party tools, custom API integrations, or basic SNMP monitoring that misses critical ACI-specific metrics like fabric health scores, policy compliance, and tenant-specific performance data.7 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.
12 votes -
Expand SSL Certificate Monitoring Beyond HTTPS
As a PRTG network administrator, I want to monitor SSL certificates for both HTTPS and MS SQL Server connections, so that I can proactively manage certificate expiration across all critical services without relying on complex external scripts.
Since the current SSL Certificate is only for web (HTTPS) ports, it might be useful to update the name to "HTTPS SSL Certificate".
Within the scope of MS SQL Server's connection SSL Certificate for the 1433 port, it will be useful to provide a way to monitor the certificate's expiry date. There is a number of pages with Python scripts that will pull…
5 votes -
Add "Warning Duration" to Sensor Data (API & UI) to Identify Long-Standing Warning States
Currently, PRTG does not provide a way to determine how long a sensor has been in a warning state. This makes it difficult to distinguish between sensors that just entered a warning state and those that have been generating warnings for extended periods (hours, days, or weeks).
Feature Request:
Please add warning state duration information to PRTG with the following components:API Access (Most Important):
- Add a "warningduration" or "timeincurrentstate" field to the sensor API endpoints
- Enable filtering/querying sensors by warning duration via API parameters
- This would allow for automated reporting and custom…5 votes -
Enhanced Script v2 Sensor Placeholder Support
As a Systems Engineer, I want Script v2 sensors to support built-in PRTG placeholders (like %snmpcommunity) so that my scripts can automatically access device credentials without manual configuration (so that Script v2 sensors can do all of the same work that older script sensors could do).
8 votesHi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
-
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.
1 vote -
Scheduled tasks sensor
As a Windows Admin using PRTG I need to be able to monitor my business processes running as scheduled tasks so that I can ensure my business processes are executing.
Today this is done via external tools and managing them is not ideal. There was a deprecated sensor for this but nothing really took its place. See https://www.reddit.com/r/prtg/comments/1lececg/if_youre_using_scheduledtask2xmlexe_from_prtg/
10 votes -
Work on scalability and reduce the number of installations in multi-server setups
Push the maximum sensor count possible on a single PRTG installation.
10 votes -
Enable receiving SNMP Traps v3
As a PRTG admin I would like to collect SNMP v3 traps from my devices that support this extra security level. My company and/or customers demand this security step in order to be 100% compliant.
Affected Application
PRTG // PRTG Network Monitor // Sensors and ProbeHow does this improve your daily work?
Hi we got several requests from customers who want to receive SNMPv3 Traps in PRTG.
At the moment only v1 and v2c traps are possible to be received.Our customers request these so to get the software 100% BSI-compliant.
Otherwise they're refraining from procuring the tool at…9 votes -
WMI Service Group Sensor
As a systems engineer, I want to monitor groups of related Windows services in a single sensor so that I can quickly identify if any critical service group is not running properly without having to create and manage multiple individual service sensors.
Examples:
- services set with "automatic start"
- multiple services with a specific name in it (e.g. all backup services)5 votes -
Enhanced SNMP Interface Speed Monitoring with Built-in ifSpeed Channels
As a Network Engineer, I want to monitor interface speeds (ifSpeed) as additional channels in SNMP Traffic sensors so that I can detect speed mismatches, auto-negotiation failures, and hardware issues without creating multiple custom sensors for each interface.
6 votes -
Auto-Adaptive PRTG Sensors for Device Configuration Changes
As a PRTG administrator managing dynamic IT/OT infrastructure, I want PRTG sensors to automatically adapt to device configuration changes (such as volume label modifications or disk capacity expansions) by using persistent hardware identifiers, so that I can maintain continuous monitoring without sensor failures, avoid losing historical data, and reduce manual maintenance overhead when routine infrastructure changes occur.
When certain device-side properties change — such as a drive’s volume label or storage size — PRTG sensors (e.g., Disk Free Sensor) often fail, even though the hardware itself remains the same. For example: If the volume label of a hard drive changes,…
4 votes -
Docker sensor
As a sysadmin or developer I would like to get metrics on the health and performance of the containers within a single Docker runtime so that I can monitor the health of the containers.
12 votes -
SNMP Interface Traffic Sensor with ifLastChange Channel for Interface Flapping Detection
As a Network Engineer managing critical network infrastructure, I want the SNMP Interface Traffic sensor to include an 'Interface Last Change' channel that monitors the ifLastChange timestamp, so that I can detect interface flapping and instability without having to create separate custom sensors for each interface or rely on SNMP traps.
5 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.
3 votesHi there,
Exciting news! Your idea is now in progress! Our team has started working on bringing this feature/improvement to life.
We're diligently developing and testing, and we'll keep you updated on our progress. We're excited about the positive impact this will have for Paessler users.
Thanks for your patience and for helping us enhance our products.
Best regards,
The Paessler Product Team
-
Native Support for Sensors with Client Certificate Authentication
As a Systems Engineer monitoring secure enterprise services, I want built-in HTTP/HTTPS sensors to support client certificate authentication (mutual TLS), so that I can monitor certificate-protected administrative interfaces, APIs, and customer portals without having to create and maintain custom scripts for each endpoint.
In secure environments, many web-based services—especially administrative interfaces, APIs, and customer portals—are only accessible via HTTPS with client certificate authentication. These URLs cannot be accessed using standard HTTP/HTTPS sensors in PRTG, as there is currently no way to specify a client certificate and private key.
Currently, the only workaround is to use custom scripts (e.g., PowerShell or…
2 votes -
Turn two devices into one - unifying PRTG device credential
As a system administrator, I would like my physical devices to be represented in PRTG by a single virtual device in the UI to make things less confusing for me and my colleagues. Unfortunately, for certain devices and sensor technologies (MQTT, controller-managed devices), I need to create a second device in order to specify the address of the MQTT Broker or other "central" controller for sensor queries. Ideally, PRTG would allow the address of a device's controller to be defined in it's settings so that only one device is sufficient. Having one physical device mapped to one PRTG device would…
6 votes
- Don't see your idea?