65 results found
-
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 -
Monitoring-status filter for SNMP interface selection when adding Traffic sensors
As a Network Engineer responsible for switch and bandwidth monitoring,
I want to filter the interface list in the SNMP sensor creation dialog by monitoring status — specifically to show only interfaces that do not yet have a sensor (and optionally hide those that do) —
so that I can quickly identify and add recently connected or overlooked ports without manually cross-checking the full interface list against existing sensors, avoiding both wasted time and accidental duplicate sensors.2 votes -
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 -
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
-
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 -
Document Required Windows Permissions per WMI Sensor (DCOM vs. WSMan) in the Sensor Manual Remarks
As a Systems Engineer setting up WMI-based sensors, I want each sensor’s manual page to list the specific Windows permissions and group memberships required (differentiated by DCOM and WSMan connection method where they differ) so that I can configure least-privilege monitoring credentials correctly on the first attempt instead of diagnosing permission failures through trial and error.
Background:
For sensors that retrieve data via WMI using WSMan, it appears that additional user permissions may be required depending on the type of monitoring performed.
For example, it took me some time to identify that the Event Log Readers group membership was required…1 vote -
Make PRTG's XML sensor interface parse real-world XML reliably and consistently
As a Systems Engineer who builds custom integrations (e.g., wrapping NRPE/Nagios plugin output for PRTG via a web server),
I want the XML processing of the HTTP Data Advanced sensor (and related advanced custom sensors) to behave like a real, standards-compliant XML parser — accepting comments, matching values to channels by name rather than position, and letting me explicitly designate the primary channel —
so that I can generate sensor output from any standard tool or library (hash tables, XSLT, alphabetically sorted REST responses) without fragile ordering hacks, and get consistent results regardless of which sensor type consumes the data.…
1 vote -
Modernized Citrix XenServer Sensors with TLS 1.2+ Support
As a Systems Engineer responsible for virtualization infrastructure, I want PRTG's Citrix XenServer Host and Virtual Machine sensors to fully support TLS 1.2 or higher, so that I can monitor my XenServer hosts and VMs without weakening the hypervisor's security configuration or losing visibility as older TLS versions are deprecated.
Background:
The current Citrix sensors do not support TLS 1.2 or higher. Since older TLS versions are being phased out and not supported, the current sensors need to be updated, or new sensors need to be created.1 vote -
Prevent Auto-Discovery from Creating a Ping v2 Sensor with Ping v1 Functionality
As a Network Engineer managing devices discovered via PRTG auto-discovery,
I want auto-discovery (including the default templates Generic Device (Ping Only) and Generic Device (SNMP Enabled)) to create ping sensors whose sensor type label matches their actual channel structure, settings, and documented functionality — i.e., a sensor labeled Ping v2 behaves as documented for Ping v2, or a sensor with Ping v1 behavior is labeled Ping v1,
so that I can trust that sensors were created correctly, reliably filter and manage sensors by type, and avoid wasting time investigating "broken" sensors that are actually just mislabeled.Background:
In PRTG 26.3.122.1665,…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 -
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 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
-
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 -
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 -
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 -
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 -
HPE VM Essentials (VME) Cluster Monitoring Sensor
As an IT Infrastructure Manager,
I want native PRTG sensors for HPE VM Essentials (VME) clusters that monitor cluster health, host performance, VM status, and resource utilization,
so that I can maintain unified visibility across my virtualization environment after migrating away from VMware, without relying on manual custom sensor configurations.1 vote -
Native Linux PSI (Pressure Stall Information) Sensor for Improved Resource Pressure Monitoring
As a Systems Engineer managing Linux server infrastructure with PRTG, I want a native Linux PSI sensor that reads CPU, memory, and I/O pressure stall metrics directly from /proc/pressure/, so that I can accurately detect resource contention, identify performance bottlenecks earlier, and replace fragile custom SSH script workarounds with a standardized, maintainable monitoring solution.
Many organizations using PRTG rely on the built-in SNMP Linux Load Average sensor to monitor system load on Linux servers. While this works for basic monitoring, the traditional load average metric has well-known limitations: it only reflects the number of runnable or waiting tasks and does…
1 vote
- Don't see your idea?