78 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 -
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.
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 -
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…
7 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 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 Azure Monitoring Sensors at AutoMonX Parity
As a PRTG user monitoring an Azure environment,
I want native Azure sensors in PRTG that provide the same depth and coverage as those offered by AutoMonX,
so that I can monitor my Azure infrastructure comprehensively without relying on a third-party solution, incurring additional costs, or managing a separate contract.Background / Context:
PRTG's current Azure-related sensors cover only basic functionality. While AutoMonX (automonx.com/azure) fills this gap on a commercial basis, prospects and customers increasingly expect a native, fully integrated solution from PRTG itself — one that requires no additional vendor relationship or cost.6 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
-
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 -
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 -
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.
6 votes -
Developer API for creating SNMP sensors
As an advanced user, I would like to use a framework in the form of a sensor API. This could be a Python library that allows me to use PRTG's internal SNMP stack with connection establishment, authentication, querying, etc., while also giving me the ability to build advanced SNMP sensors. This allows different OID trees to be combined in the code, which is not possible with SNMP custom sensors. This framework is intended to abstract the complexity of pure SNMP communication and allow developers to focus on logic and data processing.
6 votes -
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 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
-
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 -
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.
4 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…4 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
-
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 -
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 -
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
- Don't see your idea?