78 results found
-
Automated Token Renewal for API Monitoring Sensors
As a Systems Engineer monitoring APIs with PRTG, I want sensors to automatically renew expired authentication tokens so that I don't have to manually update credentials
4 votes -
PRTG Data Hub Windows Log Collection
Leverage PRTG Data Hub to efficiently manage Windows Event Logs by collecting, filtering, and forwarding critical log data.
4 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.3 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-connector3 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.
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 -
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 -
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.2 votes -
Implement GCP (Google Cloud) Monitoring Sensors with Azure-equivalent Functionality
As a Cloud/ DevOps engineer, I want to have sensors for Google Cloud Platform (GCP) similar to those available for Azure, so that I can monitor and manage my GCP infrastructure with the same level of visibility and control that I have for Azure environments.
2 votes -
HTTP Data Advanced Sensor - Historical Debug Data Retention
As a Systems Engineer, I want to retain multiple historical debug results, when the option "Result Handling -> Store result" is enabled in the HTTP Data Advanced sensor settings, so that I can compare different responses over time without losing debugging information between sensor scans. For now only the last result is stored.
2 votes -
XOA/XCP-ng Sensor
As an IT Infrastructure Manager migrating from VMware to XCP-ng, I want native PRTG sensors for XCP-ng hosts and XOA management so that I can maintain comprehensive virtualization monitoring without losing visibility or requiring custom development work during and after migration.
2 votes -
Sangfor Sensor Template
As an IT Infrastructure Manager or Systems Engineer, I want a pre-configured PRTG template for monitoring Sangfor hyperconverged infrastructure so that I can achieve comprehensive visibility into my virtualized environment without having to manually configure individual sensors or write custom scripts.
2 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…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
- Don't see your idea?