32 results found

1. 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 are unable to fetch or display available options, affecting: AWS Alarm v2, AWS Cost, AWS EBS v2, AWS EC2 v2, AWS ELB v2 and AWS RDS v2.

   Relying on custom script workarounds for standard metrics increases maintenance overhead and deviates from native platform standards required during official infrastructure evaluations.

   Required European Regions:
   AWS Europe (Spain) - EU Member -> Region Code: eu-south-2
   AWS Europe (Zurich) - Switzerland -> Region Code: eu-central-2

   References:
   PRTG Manual (Current supported list):
   https://www.paessler.com/manuals/prtg/list_of_supported_aws_regions_and_their_codes
   AWS Official Infrastructure:
   https://aws.amazon.com/es/about-aws/global-infrastructure/regions_az/
   https://docs.aws.amazon.com/general/latest/gr/cw_region.html

   Therefore, it is very important for the development team to align the native AWS sensors with current European regional availability. How important is this feature for your organization? Please vote and comment below to let us know which AWS services you are currently forced to monitor using workarounds.

   Best regards,

   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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  3 comments  ·  Delete…  ·  Admin →

2. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  2 comments  ·  Delete…  ·  Admin →

3. 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 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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

   Hi 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 the future of Paessler.

   Best regards,

   The Paessler Product Team

   Hi 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… more

4. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  2 comments  ·  Delete…  ·  Admin →

5. 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 their time in technologies with a longer lifecycle and a clearer future roadmap.
   Continuing to rely on an unencrypted protocol that has been deprecated for more than 14 years cannot reasonably be described as cyber-secure. I also note that your knowledge base contains discussions on this topic dating back to 2018, which makes it disappointing to see that your position has not evolved since then.
   Given the current threat landscape and regulatory pressure (e.g. NIS2), this is becoming increasingly difficult to justify.

   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… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  Jonah Kowall responded

   Hi 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

6. 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 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

   Thanks 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

7. 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:

   When a sensor value crosses a defined warning or error threshold, the sensor automatically reduces its scanning interval (e.g., from 5 minutes to 30 seconds)
   Once the value returns to normal for a configurable stabilization period, the sensor reverts to its standard interval

   Optional integration with Unusual Detection: trigger high-frequency sampling when anomalous patterns are detected, even before thresholds are breached

   Benefits:

   Better incident diagnostics: High-resolution data during incidents enables precise root cause analysis

   Resource optimization: Conserve system resources and storage during normal operations while ensuring detailed capture when it matters

   Proactive monitoring: Combined with Unusual Detection, catch emerging issues with granular data before they escalate

   Reduced MTTR: More data points during incidents accelerate troubleshooting and resolution

   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:

   … more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

   Hi 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

8. 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 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   Declined  ·  AdminLukas Cernohorsky (Admin, Paessler) responded

   Hi 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

9. Include SNMPv3 Context Name in Python Script Advanced Sensor Parameters

   As a Systems Engineer managing SNMPv3-enabled network devices with context-based access control, I want the Python Script Advanced Sensor to receive the SNMPv3 Context Name parameter so that my custom monitoring scripts can properly authenticate with and query devices that require specific SNMP contexts. Currently, all SNMPv3 parameters are passed into a Python Script Advanced Sensor, except "Context Name".

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

   Hello Michael,

   Thank you for your feature request.

   Unfortunately, we won't be able to implement this feature as we discontinued the Python Script Advanced sensor with PRTG 25.x.110. To ensure further monitoring, please use the successor Script v2 sensor instead. For more information, please have a look at the following pages:

   Why should I use the Script v2 sensor? | Paessler Knowledge Base

   How can I make my Python scripts work with the Script v2 sensor? | Paessler Knowledge Base

   After reviewing the Script v2 sensor, if you still need this functionality, please feel free to submit a new feature request.

   Best regards,

   The Paessler Product Team

10. Monitor primary storage platforms

    Expand PRTG sensors for primary storage platforms.

    Help us with our survey!
    https://forms.office.com/e/dSRZd1J0rX

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  Jonah Kowall responded

    Hi 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

11. Adding a OneDrive Sensor to the Existing Microsoft 365 Service Status Advanced Sensor

    As an IT Infrastructure Manager, I want OneDrive service status monitoring included in the Microsoft 365 Service Status Advanced sensor so that I can have comprehensive visibility into all critical Microsoft 365 services (including file storage/sharing) from a single monitoring point and proactively identify OneDrive outages that impact user productivity.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  Benjamin Hackenberg responded

    Hi 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. We already had a Microsoft OneDrive sensor, which was deprecated due to the low usage. The Microsoft 365 Service Status Advanced Sensor is currently having limitations regarding the service channels. If we rework this feature, we will consider adding a channel for OneDrive in the future.

    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

12. 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 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Thanks 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

13. 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 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Thanks 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

    
    

14. 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 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Thanks 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

    
    

15. 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.

    https://paessler.freshdesk.com/a/tickets/2792487

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Thanks 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

16. 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 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  Jonah Kowall responded

    Hi 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

17. 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 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Thanks 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

    
    

18. NetApp FlexCache Volume Monitoring Sensor

    As a Systems Engineer managing NetApp storage infrastructure, I want a dedicated sensor to monitor FlexCache volumes so that I can track their performance, capacity, and cache efficiency, ensuring complete visibility across my storage environment.
    Currently, they are not supported, and PRTG identifies them as normal volumes, so it gives the error "400 (bad request)".

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Hi there,

    Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.

    Based on your recent communication with our Technical Support team, we understand that your immediate need for NetApp FlexCache Volume monitoring has been resolved. We're therefore closing this feature request for now.

    However, if you need this functionality in the future, please don't hesitate to reach out with more details. In the meantime, you might also consider using our custom REST API sensor as an alternative solution.

    Thanks for your understanding and for helping us shape the future of Paessler.

    Best regards,

    The Paessler Product Team

19. Palo Alto IPsec VPN Sensor

    As a system admin I would like to monitor the IPsec tunnels of my Palo Alto firewalls with a PRTG native sensor to get a better overview of the status.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Declined  ·  1 comment  ·  Delete…  ·  Admin →

20. 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 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Declined  ·  AdminIsidora Jeremic (Admin, Paessler) responded

    Thanks 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