65 results found
-
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 / egress7 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 -
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 -
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:…6 votes -
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…
6 votes -
Native Nginx Status Sensor
As a Systems Engineer running nginx as my web server, I want a dedicated PRTG sensor that reads nginx's built-in status page and turns it into real-time channels for active connections, request throughput, connection states, and dropped connections, so that I can monitor my web server's actual load and health and get alerted before it starts refusing traffic.
5 votes -
SNMP Custom Table Sensor: Enable String Value Handling in Channels
As a Network Engineer monitoring multi-vendor network infrastructure,
I want the SNMP Custom Table sensor to support string value handling in its channels (e.g., mapping strings to sensor states or displaying them in the sensor message),
so that I can monitor all relevant data from SNMP tables - including string-based status fields, names, and descriptors, without needing to create individual string sensors or custom scripts for each OID.Background:
In SNMP Custom Table sensors, it is currently not possible to evaluate string returns within channel strings. The user considers this a notable gap, because string returns are very common in…5 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
-
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…
5 votes -
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 -
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 -
Enable Auto-Acknowledge for Ping v2 Sensor Alerts
As an IT Infrastructure Manager managing a large-scale monitoring environment,
I want the ability to enable automatic acknowledgment of alerts on Ping v2 sensors,
so that I can use Ping sensors for lightweight availability tracking and state logging without being burdened by a high volume of alerts that require manual acknowledgment.Background:
In the legacy Ping sensors, there was a feature that allowed automatic acknowledgment of alerts (auto-ack).
We use Ping sensors across a large number of devices primarily for visibility. They act as a lightweight form of logging and state tracking.
Notifications are still triggered as needed, but we…4 votes -
Microsoft Exchange Certificate Status Monitoring Sensor
As a Systems Engineer responsible for Microsoft Exchange servers,
I want a native PRTG sensor that can automatically monitor the status and expiration of Microsoft Exchange SMTP certificates (the default self-signed certificate used for internal server-to-server encryption (opportunistic TLS), and a separate "Microsoft Exchange Server Auth Certificate" used for server-to-server authentication (OAuth)),
so that I can proactively detect certificate expiration or validity issues before they cause email delivery failures, authentication problems, or security vulnerabilities in my Exchange environment.Similar requests in the past:
https://helpdesk.paessler.com/en/support/solutions/articles/76000078074-feature-request-smtp-cetificate-sensor
and
https://helpdesk.paessler.com/en/support/solutions/articles/76000076583-feature-request-ssl-certificate-sensor-for-smtp-connector4 votes -
Custom Sensor - add new tag for Value Mode of Channels
As a system administrator I use several custom sensors. For add new channels, the Value Mode can not be defined in custom sensor script e.g. powershell.
https://www.paessler.com/manuals/prtg/custom_sensorsPlease add a new tag "ValueMode" with Average/Minimum/Maximum
https://helpdesk.paessler.com/en/support/solutions/articles/76000063564-what-is-the-value-mode-in-channel-settings-Many thanks!
4 votes -
SNMP Custom Table Sensor for Multi-Platform Probes
As an Infrastructure Administrator managing a mixed IT environment with Multi-Platform Probes, I want the SNMP Custom Table sensor functionality on my Linux-based probes, so that I can efficiently create sensors from SNMP table data
4 votes -
HTTP Data Advanced Sensor Placeholder Support
As a Systems Engineer, I want HTTP Data Advanced sensors to support placeholders in URL, POST body, and custom headers fields, so that I can centrally manage sensitive credentials and API configurations while maintaining security best practices and reducing sensor configuration complexity.
4 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 -
MQTT Sensors: Support the full MQTT QoS spectrum (QoS 0 / 1 / 2), not only QoS 2
Problem / Current Limitation:
PRTG's MQTT sensors currently hard-require QoS 2 as a fixed, non-configurable part of their implementation — none of PRTG's available MQTT sensor types offer QoS 0 or QoS 1 as an alternative. QoS 0, 1, and 2 are all standard, valid delivery levels defined by the MQTT protocol itself — a broker or service that only offers QoS 0/1 is not doing anything non-standard or unusual, it's simply choosing a different (and very common) point on the QoS spectrum. By hard-coding QoS 2 across the board, PRTG effectively excludes any MQTT broker or managed service that…3 votes -
OCSP Support for SSL Certificate Monitoring Without CRL Dependency
As a Systems Engineer responsible for monitoring SSL/TLS certificates,
I want PRTG's SSL Certificate sensor (and related sensors) to support OCSP (Online Certificate Status Protocol) as a standalone certificate revocation verification method,
so that I can accurately monitor certificate validity and revocation status even when the Certificate Authority no longer provides a CRL (Certificate Revocation List), avoiding false alerts or "Unable to Check Revocation Status" warnings that undermine the reliability of my monitoring setup.3 votes -
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 -
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
- Don't see your idea?