57 results found
-
Enhanced Windows Update Sensor with Time-Based Criticality Tracking
As a System Administrator responsible for security compliance, I want to see how long Windows updates of different criticality levels have been available so that I can prioritize patching efforts based on both severity and exposure duration, ensuring compliance requirements are met and security risks are minimized.
4 votes -
WMI Service sensor
As user I want to use the WMI Service sensor with an account which has only read access as long as I use the option "Do not start/restart the service (default)".
Because the WMI Service sensor has an option to restart the service in case it is not running, the user account for this sensor must be a write user. For optimal security I might want to use read-only accounts for monitoring. This would render the WMI restart option nonfunctional but allow me to not provide PRTG write access just to monitor the running status of a Windows service.
4 votes -
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.
4 votes -
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.
4 votes -
Add support for SNMPv3 authNoPriv mode in PRTG
As a network engineer managing devices from ISPs and vendors with restricted SNMP configurations, I want PRTG to support SNMPv3 authNoPriv mode (authentication without encryption) so that I can monitor critical infrastructure devices that only allow this security level.
Currently, PRTG only supports SNMPv3 with authPriv (authentication + encryption). Many providers, e.g. Telekom, only offer SNMPv3 in authNoPriv mode.
Example configuration (as provided by Telekom, not changeable):
Mode: authNoPriv
Authentication Protocol: MD5
Privacy (Encryption): NoneSince PRTG does not support authNoPriv, monitoring such devices is currently impossible.
3 votesHi 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
-
Enhance RADIUS v2 Sensor to comply with RFC 3579 Message-Authenticator
As a Network Engineer, I want the RADIUS v2 sensor to support RFC 3579 Message-Authenticator validation so that I can monitor RADIUS servers with enhanced security and ensure authentication packet integrity in my network infrastructure. The client (PRTG Sensor) computes the hash (HMAC-MD5) from its own packet and then adds the attribute as a signature to the request. This is required for secure implementations of RADIUS.
3 votes -
Add Maximum Bandwidth Tracking Channel to SNMP Traffic Sensors for Enhanced Capacity Planning
As a Network Engineer, I want PRTG's SNMP Traffic sensor to include additional channels that track maximum bandwidth values (In/Out) over configurable time periods, so that I can accurately assess true network capacity utilization for effective capacity planning and infrastructure decision-making.
3 votes -
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.
3 votes -
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.
3 votes -
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.
3 votes -
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.3 votes -
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.
3 votes -
Native Support for Sensors with Client Certificate Authentication
As a Systems Engineer monitoring secure enterprise services, I want built-in HTTP/HTTPS sensors to support client certificate authentication (mutual TLS), so that I can monitor certificate-protected administrative interfaces, APIs, and customer portals without having to create and maintain custom scripts for each endpoint.
In secure environments, many web-based services—especially administrative interfaces, APIs, and customer portals—are only accessible via HTTPS with client certificate authentication. These URLs cannot be accessed using standard HTTP/HTTPS sensors in PRTG, as there is currently no way to specify a client certificate and private key.
Currently, the only workaround is to use custom scripts (e.g., PowerShell or…
2 votes -
SNMP Custom Table Sensor for Multi-Platform Probes
As an Infrastructure Administrator managing a mixed IT environment with Multi-Platform Probes, I want the SNMP Custom Table sensor functionality on my Linux-based probes, so that I can efficiently create sensors from SNMP table data
2 votes -
HTTP Data Advanced Sensor Placeholder Support
As a Systems Engineer, I want HTTP Data Advanced sensors to support placeholders in URL, POST body, and custom headers fields, so that I can centrally manage sensitive credentials and API configurations while maintaining security best practices and reducing sensor configuration complexity.
2 votesHi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
-
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…
2 votes -
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
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 -
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.
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
- Don't see your idea?