64 results found
-
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…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…
15 votes -
Local Time-Based Sensor Scheduling
As an IT Infrastructure Manager, I want to schedule PRTG sensors to run at specific times using our local system time (not UTC), so that I can align monitoring activities with our business hours, maintenance windows, and operational schedules without having to calculate time zone conversions.
4 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.15 votes -
Allow Creation of LUN v2 Sensors When the LUN’s Comment Metadata is Empty
As a Storage Administrator, I want to add and monitor LUNs with an empty or unset comment field using the LUN v2 sensor in PRTG, so that monitoring coverage is not blocked by optional metadata and I can ensure complete visibility and SLAs across all storage volumes.
Problem / Context:
In many storage environments, the comment/description attribute of a LUN is optional and frequently left blank (e.g., when provisioned by automation or 3rd‑party workflows).
When I attempt to add a LUN v2 sensor for such a LUN, PRTG fails with the error: “Das abgefragte Feld comment ist leer.” (“The queried…1 vote -
Support for Monitoring NetApp ASA r2 and AFX Systems in PRTG
As a Storage Administrator
I want PRTG to support monitoring of the new NetApp ONTAP-based systems ASA r2 and AFX
So that I can ensure full visibility and performance tracking of these devices within our existing monitoring environment.Context & Details
NetApp recently introduced two new ONTAP-based platforms:ASA r2: All-Flash SAN Array optimized for block storage.
AFX: High-performance NAS/S3 system designed for AI/ML workloads.Both systems leverage the ONTAP REST API but include specific changes and new endpoints:
ASA r2 introduces endpoints like /api/storage/storage-units and /api/storage/block-volumes for LUNs and NVMe namespaces, and recommends OAuth 2.0 for authentication.
AFX removes…
3 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…
28 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,…
9 votes -
Dell PowerStore Storage Sensors
As an IT Infrastructure Manager migrating from Dell EMC Unity to Dell PowerStore storage systems, I want native PRTG sensors for PowerStore monitoring (equivalent to current Unity sensors) plus dedicated replication health monitoring, so that I can maintain comprehensive storage visibility without manual REST API configuration.
PRTG has a lot of useful sensors for the Dell EMC Unity storage, which we are glad to have. Unfortunately Dell announced their end of sale in August 2025 and for the first hardware generation their end of service in July 2026.
The successor to Unity is the PowerStore storage system. Unfortunately the only…
4 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).
13 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)12 votes -
Enhance RADIUS v2 Sensor to comply with RFC 3579 Message-Authenticator
As a Network Engineer, I want the RADIUS v2 sensor to support RFC 3579 Message-Authenticator validation so that I can monitor RADIUS servers with enhanced security and ensure authentication packet integrity in my network infrastructure. The client (PRTG Sensor) computes the hash (HMAC-MD5) from its own packet and then adds the attribute as a signature to the request. This is required for secure implementations of RADIUS.
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.
9 votes -
Certificate Transparency Log Monitoring Sensor
As a Network Engineer, I want to monitor Certificate Transparency logs for my organization's domains so that I can detect unauthorized certificate issuance and maintain visibility over our certificate ecosystem in an era of automated certificate management.
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.
13 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.
7 votes -
HTTP Push Data Advanced Sensor: Graceful Resume from Paused Maintenance Windows
As a Systems Engineer managing servers with outbound-only connectivity, I want HTTP Push Data Advanced sensors to gracefully resume monitoring after maintenance windows by using the most recent push data received during the pause, so that I don't get false alarms and can maintain accurate monitoring continuity during planned maintenance.
1 vote -
Enhanced Windows Update Sensor with Time-Based Criticality Tracking
As a System Administrator responsible for security compliance, I want to see how long Windows updates of different criticality levels have been available so that I can prioritize patching efforts based on both severity and exposure duration, ensuring compliance requirements are met and security risks are minimized.
5 votes -
SNMP Trap Receiver sensor can persist its state
User Story:
As a Network Administrator managing critical infrastructure,
I want SNMP Trap Receiver sensors to maintain persistent alarm states until problems are resolved,
so that I don't miss critical issues that are only reported once via SNMP trapsAcceptance Criteria:
- SNMP Trap Receiver sensors can maintain error states until problems are actually resolved, not just until the next scan interval.
- Users have multiple ways to clear persistent trap alarms (automatic clear traps, manual reset, or timeout).
- The persistent state feature can be enabled/disabled to maintain compatibility with existing monitoring setups.3 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…
13 votes
- Don't see your idea?