69 results found
-
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…
21 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…
12 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.
21 votes -
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.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…
10 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…9 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…22 votes -
Native Veeam Backup & Replication API Integration for PRTG Backup Job Monitoring (Without Enterprise Manager)
As a Systems Engineer managing my organization's IT infrastructure with PRTG, I want PRTG to monitor Veeam Backup & Replication job statuses by connecting directly to the Veeam B&R REST API (v13+), so that I can monitor backup jobs without requiring a Veeam Enterprise Manager license or a portal administrator account, reducing both licensing costs and security exposure.
The current Veeam Backup Job Status (and Advanced) sensors still require and use Veeam Enterprise Manager (and require portal administrator role).
Would be great to refactor or build new sensors to use/connect directly to the Veeam B&R server instead of the Veeam…
4 votes -
VMware Snapshot Monitoring Sensor
As an IT administrator managing VMware infrastructure, I would like a dedicated sensor to monitor virtual machine snapshots in PRTG, so that I can proactively detect and remediate snapshot-related issues before they cause performance degradation or storage outages.
4 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)11 votes -
Built-in Migration from Old SNMP Sensors to Their v2 Successors with Historical Data Retention
As a Systems Engineee,
I want a built-in/ automatic migration from existing legacy SNMP sensors to their newer v2 sensor equivalents,
so that I can adopt the improved sensor types without manually recreating hundreds of sensors and without losing my historical monitoring data, alerts, and configurations.3 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).
9 votes -
Native vCenter Alarm Monitoring Sensor
As a Systems Engineer managing a VMware vSphere environment, I want a native PRTG sensor that monitors vCenter alarms directly, so that I can gain complete visibility into the health status of my virtualized infrastructure without relying on third-party scripts or workarounds, ensuring I'm immediately aware of critical issues flagged by vCenter's own alarm system.
There is a third party sensor (https://github.com/Jannos-443/PRTG-VMware-Alerts), but something this fundamental should be built in.
5 votes -
Monitoring of Individual Azure File Shares (per‑share capacity, usage, and performance)
Currently, the Azure Storage Account sensor in PRTG only provides metrics at the storage-account level.
As an IT admin, I need the ability to monitor each Azure File Share separately, including metrics such as used space,
free space, total capacity, file count, and I/O performance.Please introduce a new Azure File Share sensor that queries per-share metrics.
Possible channels:
Total capacity
Used space
Free space
File count
IOPS / throughput
Ingress / egress4 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,…
7 votes -
Add Maximum Bandwidth Tracking Channel to SNMP Traffic Sensors for Enhanced Capacity Planning
As a Network Engineer, I want PRTG's SNMP Traffic sensor to include additional channels that track maximum bandwidth values (In/Out) over configurable time periods, so that I can accurately assess true network capacity utilization for effective capacity planning and infrastructure decision-making.
8 votes -
SNMP Custom Table Sensor: Auto-naming from String Columns & Multi-Column Monitoring
Problem:
The SNMP Custom Table Sensor has critical limitations:
Sensors are named by row identifiers (e.g., "Table: OID / 128.141.183.198.171.212") instead of human-readable names from string columns
Only one column per sensor - monitoring multiple metrics per table row requires multiple separate sensors
String columns cannot be used for naming or identification
This makes monitoring dynamic SNMP tables (APs, interfaces, VPN users) impractical at scale.Requested Features:
1. Automatic Naming from String Columns
Add option to specify which table column contains sensor names
Example: Use column .1.3 (AP Name) instead of MAC address
Result: Sensors named "AP-Office-Floor1" instead of "Table:…3 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.
8 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.
12 votes -
Kubernetes Sensor
As a DevOps Engineer, I need a native PRTG sensor to monitor the health and performance of my custom applications running in Kubernetes, so that I can gain immediate, centralized visibility into their operational status, proactively identify issues at the cluster, pod, and application level, and ensure the continuous availability and performance of my services.
Kubernetes-Aware Monitoring:
- Ability to target and understand applications deployed via Kubernetes constructs (e.g., Deployments, Pods, Namespaces).
- Provide insights into the overall health and status of application deployments (e.g., how many instances are running vs. expected).
- Report on the status and lifecycle of individual application pods…
10 votes
- Don't see your idea?