49 results found
-
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,…
-
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
-
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
-
Support for sensor templates (same common settings for same sensor types)
As a PRTG admin deploying multiple sensors we must make manual adjustments after auto discovery we would like to use a template to apply defaults similar to device templates so that we could reduce the manual effort the team does today.
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
-
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
-
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
-
Keyword detection on O365 sensor
As a PRTG user I would like to use the O365 sensor to be able to detect when I get an email with specific text in the subject or body so that I can monitor other processes for errors which are sending emails to report errors. Also, there's currently no option "If No Email Matches the Above Filters" for the MS365 Mailbox sensor as in the IMAP sensor.
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
-
Prometheus sensor which can scrape prometheus exporters
As a syadmin who is a current Prometheus user I would like to get metrics from Prometheus exporters so that I can have my metrics in PRTG along with my other infrastructure data.
Ideally I could also scrape these from other Prometheus compatible endpoints such as the OpenTelemetry collector.
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
-
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
-
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
-
Monitor primary storage platforms
Expand PRTG sensors for primary storage platforms.
Help us with our survey!
https://forms.office.com/e/dSRZd1J0rX4 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
-
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
-
Add a setting field for a TSIG key to the DNS v2 sensor
As a PRTG user I want to monitor if my DNS server is delivering any addresses or the correct addresses depending on an internal or external request. DNS servers use TSIG keys to identify the type of request and answer it should deliver. If PRTG would support TSIG keys the answer of the server could be checked from one probe. The current workaround would be to create a probe for every context view the DNS server needs to be aware of.
4 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
-
Flood of notifications after PRTG restart
As user, I have a lot of alarms which I am aware of. When I restart PRTG, I get flooded with notification emails, stuffing my already full inbox and being an annoyance instead of being helpful.
I am aware that such option comes with the risk that a new alert might be overlooked. But this is a risk I as a user would take in order to work efficiently with PRTG.
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
-
Dynamic File Content Monitoring
As a system administrator using PRTG,
I want to configure a file content sensor using simple date placeholders or regex patterns to automatically find the correct log file each day,
so that monitoring dynamic log files becomes straightforward and less time-consuming.4 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
-
Tag support in Sensor Factory
As a PRTG admin setting up sensors using Sensor Factory we have the need to dynamically update sensors using the API to add tagging to aggregate upstream traffic across links so that I can have the right data for monitoring and reporting purposes due to constant changes in our network.
4 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
-
SQL sensor cluster awareness
As a database administrator I want to monitor my SQL servers that are part of a cluster avoiding false positives due to cluster failover or health. If a failover happens PRTG and the SQL sensors should be aware of it so that I can get the right notification and not be overwhelmed by notifications
3 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
-
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 -
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
- Don't see your idea?