76 results found
-
As a suggestion for future versions, it would be great to implement a filtering system when discovering sensors via SNMP (which reveals all
As a suggestion for future versions, it would be great to implement a filtering system when discovering sensors via SNMP (which reveals all connections on a device like a switch). Specifically, we would like a filter to exclude interfaces that are already being monitored, and—perhaps even more usefully—a filter to show only those connections that are not currently being monitored; this would help us catch any recently added connections we might have overlooked.
This latter filter would be extremely useful, as it would save us from wasting time manually selecting all the connections again.
1 vote -
Dynamic sensor assignment to Business Process channels via tags
As a Systems Engineer managing a large or frequently changing PRTG environment, I want to define a sensor tag as a dynamic filter for a Business Process channel, so that sensors are automatically added to or removed from the channel when their tags change — eliminating manual reconfiguration of Business Process Sensors every time the environment changes.
Background:
Business Process Sensor configurations are currently largely static. Sensors have to be manually assigned to individual Business Process channels.
For larger PRTG environments, it would be very useful to have the option to dynamically populate Business Process channels based on sensor tags.…1 vote -
Bulk-add sensors to Business Process channels (multi-select & ID list)
As a Systems Engineer setting up Business Process Sensors with many underlying sensors, I want to add multiple sensors to a BP channel in one operation — via multi-select in the device tree or by pasting a list of sensor IDs — so that I can configure large Business Processes in minutes instead of adding each of e.g. 50 sensors individually.
Background:
When configuring a Business Process Sensor, sensors currently have to be added one by one, either by entering the sensor ID or by selecting each sensor individually from the Device Tree.
This becomes extremely time-consuming when a Business…1 vote -
Show full object context (probe → device → sensor) in Business Process channel sensor lists
As a Systems Engineer validating or troubleshooting a Business Process Sensor configuration, I want the list of assigned sensors per channel to display the full object path (probe, device, sensor name, sensor ID, and optionally sensor status) with sorting and filtering, so that I can immediately identify which sensor belongs to which device without looking up each sensor ID individually.
Background:
When configuring a Business Process (BP) Sensor, the objects assigned to a channel are currently displayed mainly by sensor name and sensor ID. For larger Business Process Sensors, this makes it difficult to see which device and probe a…1 vote -
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.3 votes -
More Essential Sensors for the Multi-Platform Probe on Linux
As a Systems Engineer running PRTG multi-platform probes on Linux in environments without Windows probe systems, I want more essential sensors, for example, native NTP/SNTP and LDAP(S) sensors to be available on the multi-platform probe,
so that I can monitor time synchronization and directory service availability — two services critical for authentication and infrastructure health — directly from my Linux probes, without maintaining a Windows remote probe or building custom script workarounds.1 vote -
Proxmox Credential Placeholders for Custom Script Sensors
As a Systems Engineer monitoring Proxmox hypervisors with both native PRTG sensors and custom EXE/Script Advanced (PowerShell) sensors, I want the device-level "Credentials for Proxmox" fields (API Token ID, Secret, Port) to be available as placeholders (e.g., %proxmoxtokenid, %proxmoxtokensecret, %proxmoxport) in my script parameters, so that I maintain the API token in one single place and token rotation no longer requires redundant, error-prone updates across two credential sections.
Background:
We heavily rely on Custom EXE/Script Advanced Sensors (PowerShell) to monitor our hypervisors for specific metrics, like aging snapshots. While migrating to Proxmox, we noticed that we cannot pass the newly…1 vote -
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
-
DNSSEC Sensor
As an operator of security‑critical DNS infrastructure, I want a native PRTG sensor that monitors DNSSEC signature status and trust chain integrity for my DNS zones, so that I can detect issues such as missing DS records, expiring signatures, or failed validation before they impact production.
Therefore, a sensor must check the following DNSSEC components:
AD flag (validation status)
Presence of RRSIG records and their signature expiration time (warn if remaining time is low!)
Count of DNSKEY records including KSK (257) and ZSK (256)
Count of DS records in the parent zone (=0 is error)
Trust chain consistency (DS ->…1 vote -
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
-
Redfish Fan State sensor
As a PRTG user, I want a single sensor per server (HPE, Dell, Lenovo, Supermicro, etc.) that monitors all fans via Redfish, so that I get a consolidated view of fan health and speeds without cluttering my device tree with one sensor per fan.
1 voteHi 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
-
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
-
Add "Output Source" Channel to SNMP UPS Status Sensor for Utility Power Loss Detection
As a Systems Engineer responsible for monitoring UPS infrastructure,
I want the SNMP UPS Status sensor to include an "Output Source" channel that indicates whether the UPS is supplying power from utility (mains) or battery,
so that I am immediately alerted when a UPS switches to battery power due to a utility outage, without having to wait for the battery charge to drop to a warning or error threshold.Background:
I've just started testing the SNMP UPS Status (NEW) sensor with Eaton UPSs. Having the Battery Status, Charge Remaining, Current Load, and Estimated Time Remaining are all super handy.
However,…2 votes -
Proxy Support for SSL Certificate Sensor
As an IT Infrastructure Manager operating PRTG in a network without direct internet access,
I want the SSL Certificate sensor to natively support the HTTP proxy settings configured on the parent device,
so that I can monitor the SSL/TLS certificates of external websites through our proxy — just like I already can with HTTP-based sensors — without needing to rely on a separate monitoring tool.Background: We are using PRTG without direct internet access. With the proxy setting of the device we can monitor a HTTPS website, but not the SSL certificate of that site. That is a problem for…
1 vote -
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 -
SNMP Cisco System Health Sensor: Add "Used Memory " Channel
As a Network Engineer, I want to see a 'Used Memory (%)' channel alongside the existing 'Available Memory' channel in the SNMP Cisco System Health sensor, so that I can choose the metric that best fits my alerting thresholds and dashboards.
2 votes -
Synology NAS Sensor Support on the Multi-Platform Probe
As a Systems Engineer, I want to be able to use Synology NAS sensors on the multi-platform probe, so that I can monitor my Synology storage devices from Linux-based or containerized probe environments without depending on a Windows remote probe
2 votesHi there,
Great news! Your idea has been reviewed and is now officially on our roadmap! This means we've committed to developing it in the future.
While we don't have an exact release date yet, we're planning to implement this feature/improvement as part of our upcoming development cycles. We're excited about the value this will bring to our users.
We appreciate your patience as we work to bring this to fruition. We'll let you know once it moves into active development.
Thanks for helping us build a better Paessler!
Best regards,
The Paessler Product Team
-
HPE ProLiant Sensor Support on the Multi-Platform Probe
As a Systems Engineer, I want to be able to use HPE ProLiant sensors on the multi-platform probe, so that I can monitor my HPE server hardware from Linux-based or containerized probe environments without depending on a Windows remote probe.
1 vote -
Enhanced Cisco Catalyst 9800 WLC Monitoring Sensors
As a Network Engineer, I want comprehensive, out-of-the-box sensors for the Cisco Catalyst 9800 Wireless LAN Controller — covering SSID status, per-SSID client counts, per-SSID traffic, WLC high-availability status, and disk space — so that I can proactively manage my wireless infrastructure without relying on manual CLI checks or custom workarounds.
2 votes
- Don't see your idea?