49 results found
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we’ve decided not to move forward with automatically following a VM when it migrates to a different cluster node. The main reason is a technical one: the Proxmox API is node-specific. It only exposes the VMs running on the node we are connected to, and it doesn’t provide a way to track a VM once it moves to another node. Because of this limitation, we can’t reliably follow a migrated VM to its new host.
While this particular idea won’t be moving forward, please don’t be discouraged. Your input is incredibly valuable, and we encourage you to keep sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Built-in Migration from Old SNMP Sensors to Their v2 Successors with Historical Data Retention
As a Systems Engineee,
I want a built-in/ automatic migration from existing legacy SNMP sensors to their newer v2 sensor equivalents,
so that I can adopt the improved sensor types without manually recreating hundreds of sensors and without losing my historical monitoring data, alerts, and configurations.13 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we’ve decided not to move forward with a general, built-in migration from legacy SNMP sensors to their v2 equivalents. The main reason is a technical one: a v2 sensor is not simply a copy of its predecessor. We often improve, rewrite, and change the sensor, including its channels and other features. Because v1 and v2 sensors can differ this much, an automatic migration is often not possible.
Where we see the chance, we do migrate sensors under the hood and keep your historic data. However, this is a sensor-by-sensor decision, so we can’t offer it across the board.
If a manual migration is necessary, we recommend keeping the old sensor in a paused state. A paused sensor doesn’t count towards your license,…
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we’ve decided not to move forward with this idea. The main reason is a technical one: Metascans work independently of your existing sensors, so they have no knowledge of which sensors are already set up on a device. Because of this, they can’t reliably tell which interfaces or ports are “new” or “missing,” and building that capability would go against how Metascans are designed to work.
There is already a good way to achieve what you’re after. If you want to find new or missing interfaces or ports on a router, we recommend using an auto-discovery template. Unlike a Metascan, auto-discovery is aware of the sensors that already exist on a device, so it only suggests or creates sensors for what is…
-
Port Sensor: Support for Sending Raw Binary/Hex Data via the Command Field
As a Satellite Engineer/PRTG network administrator, I would like the ability to send raw binary/hex data through Port sensors command field. Security restrictions limit me from using the EXE/Script Advanced Sensor with a custom script to open a TCP port. With the port sensor I can manage devices on our network that don’t have SNMP.
2 votes -
Support for AWS Europe Regions (Spain eu-south-2 & Zurich eu-central-2) in AWS Sensors
As a Systems Technician, I want PRTG native AWS sensors to support current European regions so that we can meet standard data sovereignty requirements and maintain verified monitoring architecture without custom workarounds.
Under the framework of the EU GDPR, Swiss DPA, and regional national laws, many organizations and enterprise clients must guarantee strict data sovereignty. This requires that both critical workloads and their associated monitoring infrastructure remain within specific national borders to satisfy formal audits.
Currently, several native PRTG AWS v2 sensors cannot be deployed in these territories because the regions are missing from the built-in selection menu. The sensors…
1 vote -
Allow reserved JavaScript event terms (onerror, onload, onclick) in sensor names without sanitization to "***"
As a Systems Engineer configuring file monitoring in PRTG,
I want to name sensors (and reference file paths) containing the strings "onerror", "onload", or "onclick" without PRTG replacing them with "***",
so that I can monitor files whose real names contain these strings and keep sensor names that accurately identify the monitored object — without maintaining workarounds.Background:
Currently we are unable to name anything with the words onerror, onload, or onclick as it replaces the whole string with ***. This makes it not possible to do file monitoring for some files due to the name. I would really like…1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration, we've decided to decline this idea at this time — and we want to be transparent about why.
PRTG deliberately sanitizes user input fields rendered in the web UI (object names, certain settings). Strings that look like JavaScript event handlers — onerror, onload, onclick — are replaced with *** to prevent stored cross-site scripting. This is an intentional security control, not a bug, and a global opt-out would reopen exactly that XSS vector, which is why we can't offer one.
That said, there are several ways to monitor such files today:
- Sensor name – The display name is a free label and needn't match the file name exactly. Any inserted character breaks the filter pattern: "on_error.js monitor" or "on-error handler file" works fine.
- Script sensor…
-
Auto-Adaptive PRTG Sensors for Device Configuration Changes
As a PRTG administrator managing dynamic IT/OT infrastructure, I want PRTG sensors to automatically adapt to device configuration changes (such as volume label modifications or disk capacity expansions) by using persistent hardware identifiers, so that I can maintain continuous monitoring without sensor failures, avoid losing historical data, and reduce manual maintenance overhead when routine infrastructure changes occur.
When certain device-side properties change — such as a drive’s volume label or storage size — PRTG sensors (e.g., Disk Free Sensor) often fail, even though the hardware itself remains the same. For example: If the volume label of a hard drive changes,…
9 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Multicast Monitoring Sensor
As an Enterprise Network Administrator managing Multicast infrastructure I want a dedicated Multicast Monitoring sensor in PRTG so that I can monitor the multicast performance & matric such as groups , source, bandwidth, top groups etc. without needing separate monitoring tools or complex custom scripts.
2 votes -
Windows Update Sensor, which tracks all Windows updates
As a Systems Engineer, I want the Windows Updates Status sensor to detect and report all installed Windows updates — regardless of whether they were deployed via Windows Update Agent, WSUS, SCCM/MECM, manual installation, or any other software distribution method — so that I can have a single, reliable view of the patch status of my Windows systems and ensure compliance without needing to cross-reference multiple tools. The current Windows Update sensor only tracks updates installed by the Windows Update Agent. Updates installed manually or via software distribution are not tracked. The sensor should be expanded to track all installed…
1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. Here is why: design principle of PRTG sensors is one sensor = one service/technology. To cover updates installed via WSUS, SCCM/MECM, manual installation, and other distribution methods, the sensor would need to use multiple different monitoring technologies simultaneously. This would also introduce significant challenges around long-term maintainability and reliability - each deployment method has its own behavior, update cadence, and potential failure modes that would all need to be handled within a single sensor.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape…
-
Allow Creation of LUN v2 Sensors When the LUN’s Comment Metadata is Empty
As a Storage Administrator, I want to add and monitor LUNs with an empty or unset comment field using the LUN v2 sensor in PRTG, so that monitoring coverage is not blocked by optional metadata and I can ensure complete visibility and SLAs across all storage volumes.
Problem / Context:
In many storage environments, the comment/description attribute of a LUN is optional and frequently left blank (e.g., when provisioned by automation or 3rd‑party workflows).
When I attempt to add a LUN v2 sensor for such a LUN, PRTG fails with the error: “Das abgefragte Feld comment ist leer.” (“The queried…2 votesThank you for this suggestion. We regularly review open ideas to keep our backlog focused on what will benefit the most users. Since this one hasn't gathered enough support over time to justify prioritizing it, we're closing it for now. This doesn't mean it's off the table forever - if priorities or demand change, we're always open to revisiting. In the meantime, please keep the ideas coming!
Best regards,
The Paessler Product Team
Best regards,
The Paessler Product Team
-
Time-Period-Specific Calculation of Sensor Uptime
As an Network Engineer, I want uptime and downtime values to be calculated based on the selected time period (both in web interface tabs like "30 days" and API calls), so that I can get accurate availability metrics for specific reporting periods instead of misleading lifetime values that include the entire sensor history since creation.
Currently, PRTG calculates uptime/downtime values from sensor creation time regardless of the requested time period, which creates misleading availability statistics when users need period-specific reports.
2 votes -
Windows agent with small footprint
I understand that it is still technically possible to monitor Windows-based workstations and servers using SNMP—provided one is willing to invest the necessary time and effort to keep it running.
I would, however, like to give you a clear heads-up.
As described in this article: https://helpdesk.paessler.com/en/support/solutions/articles/76000067671-snmp-going-away, the SNMP feature is no longer available by default when upgrading from Windows 10 to Windows 11 or when performing a clean installation of Windows 11. This means your customers are required to spend increasing amounts of time maintaining a function that Microsoft has officially deprecated.
Realistically, most customers would prefer to invest…2 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Adding a sensor setting for shared mailbox size to the Microsoft 365 mailbox sensor
As an IT Network Administrator, I want the Microsoft 365 Mailbox sensor to display mailbox size in MB/GB and usage percentage against quota limits so that I can proactively alert on approaching capacity limits and prevent shared mailbox outages that disrupt business operations.
5 votesThanks for this suggestion and for everyone's input here. We regularly review open ideas to keep our backlog focused on what will benefit the most users. Since this one hasn't gathered enough support over time to justify prioritizing it, we're closing it for now. This doesn't mean it's off the table forever - if priorities or demand change, we're always open to revisiting. In the meantime, please keep the ideas coming!
Best regards,
The Paessler Product Team
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Adaptive Sensor Scanning Intervals Based on Threshold Breaches
As a Systems Engineer managing critical infrastructure, I want sensors to automatically switch to a higher sampling rate (down sampling interval) when a predefined threshold is exceeded, and revert to normal interval once the condition clears. This feature could be optionally combined with the existing "Unusual Detection" capability for intelligent, context-aware monitoring.
Currently, PRTG sensors operate at a fixed scanning interval regardless of the monitored value's state. This means that during critical events (threshold breaches, performance degradation, outages), we capture data at the same granularity as during normal operations—missing valuable diagnostic information precisely when we need it most.
Proposed behavior:
…
1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
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 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
- Don't see your idea?