63 results found
-
Native Linux PSI (Pressure Stall Information) Sensor for Improved Resource Pressure Monitoring
As a Systems Engineer managing Linux server infrastructure with PRTG, I want a native Linux PSI sensor that reads CPU, memory, and I/O pressure stall metrics directly from /proc/pressure/, so that I can accurately detect resource contention, identify performance bottlenecks earlier, and replace fragile custom SSH script workarounds with a standardized, maintainable monitoring solution.
Many organizations using PRTG rely on the built-in SNMP Linux Load Average sensor to monitor system load on Linux servers. While this works for basic monitoring, the traditional load average metric has well-known limitations: it only reflects the number of runnable or waiting tasks and does…
1 voteThanks for submitting your idea, to Paessler! We really appreciate you taking the time to share your feedback and help us improve our products.
Your idea has been successfully received and is now in our review queue. Our team will carefully evaluate it, and we'll keep you updated on its status.
In the meantime, feel free to share your idea with others to gather more support and comments. The more input we get, the better!
Thanks again for your contribution.
Best regards,
The Paessler Product Team
-
Native Podman Container Monitoring Sensor
As a Systems Engineer managing containerized workloads across different operating systems and environments, I want a dedicated Podman container monitoring sensor in PRTG so that I can monitor the health, status, resource usage, and uptime of my Podman containers, with the same depth and ease that the existing Docker sensor provides for Docker environments.
1 voteThanks for submitting your idea, to Paessler! We really appreciate you taking the time to share your feedback and help us improve our products.
Your idea has been successfully received and is now in our review queue. Our team will carefully evaluate it, and we'll keep you updated on its status.
In the meantime, feel free to share your idea with others to gather more support and comments. The more input we get, the better!
Thanks again for your contribution.
Best regards,
The Paessler Product Team
-
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.1 voteThanks for submitting your idea, to Paessler! We really appreciate you taking the time to share your feedback and help us improve our products.
Your idea has been successfully received and is now in our review queue. Our team will carefully evaluate it, and we'll keep you updated on its status.
In the meantime, feel free to share your idea with others to gather more support and comments. The more input we get, the better!
Thanks again for your contribution.
Best regards,
The Paessler Product Team
-
Zerto Analytics Portal Integration for DRaaS Protection Monitoring
As an IT Infrastructure Manager responsible for disaster recovery operations,
I want PRTG to integrate with the Zerto Analytics portal to monitor Virtual Protection Groups (VPGs), their size, RPO compliance, and replication health,
so that I can proactively detect drift in DRaaS protection, ensure business continuity compliance, and receive alerts when disaster recovery SLAs are at risk—all from within my unified PRTG monitoring dashboard.1 vote -
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-connector1 voteHi 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
-
VMware Snapshot Monitoring Sensor
As an IT administrator managing VMware infrastructure, I would like a dedicated sensor to monitor virtual machine snapshots in PRTG, so that I can proactively detect and remediate snapshot-related issues before they cause performance degradation or storage outages.
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
-
Custom Sensor - add new tag for Value Mode of Channels
As a system administrator I use several custom sensors. For add new channels, the Value Mode can not be defined in custom sensor script e.g. powershell.
https://www.paessler.com/manuals/prtg/custom_sensorsPlease add a new tag "ValueMode" with Average/Minimum/Maximum
https://helpdesk.paessler.com/en/support/solutions/articles/76000063564-what-is-the-value-mode-in-channel-settings-Many thanks!
2 votes -
SNMP Custom Table Sensor: Auto-naming from String Columns & Multi-Column Monitoring
Problem:
The SNMP Custom Table Sensor has critical limitations:
Sensors are named by row identifiers (e.g., "Table: OID / 128.141.183.198.171.212") instead of human-readable names from string columns
Only one column per sensor - monitoring multiple metrics per table row requires multiple separate sensors
String columns cannot be used for naming or identification
This makes monitoring dynamic SNMP tables (APs, interfaces, VPN users) impractical at scale.Requested Features:
1. Automatic Naming from String Columns
Add option to specify which table column contains sensor names
Example: Use column .1.3 (AP Name) instead of MAC address
Result: Sensors named "AP-Office-Floor1" instead of "Table:…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
-
Flexible Channel Selection for Citrix XenServer Host Sensor
As a System Engineer monitoring large-scale Citrix XenServer environments,
I want the ability to selectively choose which channels to monitor in the Citrix XenServer Host sensor (e.g., specific CPU cores and hardware components),
so that I can reduce sensor complexity, improve performance, and maintain a clear overview when monitoring systems with 200+ CPU cores without being overwhelmed by hundreds of unnecessary channels.1 vote -
Monitoring of Individual Azure File Shares (per‑share capacity, usage, and performance)
Currently, the Azure Storage Account sensor in PRTG only provides metrics at the storage-account level.
As an IT admin, I need the ability to monitor each Azure File Share separately, including metrics such as used space,
free space, total capacity, file count, and I/O performance.Please introduce a new Azure File Share sensor that queries per-share metrics.
Possible channels:
Total capacity
Used space
Free space
File count
IOPS / throughput
Ingress / egress3 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
-
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…
3 votes -
Native F5 BIG-IP Sensors
As a Network Engineer, I want native F5 BIG-IP sensors (BIG-IP 17.x): LTM Nodes, Pools, Pool Members, Virtual Servers, and System sensors (CPU, Interface, Disk, Cluster). These sensors must auto-discover objects and create channels dynamically.
Customer Need:
Native, out‑of‑the‑box PRTG sensors for F5 BIG‑IP devices, designed similarly to other vendor-specific sensor types (e.g., FortiGate, HPE, NetApp).
These sensors should provide intelligent auto‑discovery and automatic channel creation, instead of requiring SNMP Custom sensors.We expect sensor types that automatically detect and monitor:
A. LTM Object Sensors (from LOCAL-MIB)
Each of these should be a dedicated native sensor type:F5 LTM Nodes…
11 votes -
Native vCenter Alarm Monitoring Sensor
As a Systems Engineer managing a VMware vSphere environment, I want a native PRTG sensor that monitors vCenter alarms directly, so that I can gain complete visibility into the health status of my virtualized infrastructure without relying on third-party scripts or workarounds, ensuring I'm immediately aware of critical issues flagged by vCenter's own alarm system.
There is a third party sensor (https://github.com/Jannos-443/PRTG-VMware-Alerts), but something this fundamental should be built in.
3 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 votes -
Add "Warning Duration" to Sensor Data (API & UI) to Identify Long-Standing Warning States
Currently, PRTG does not provide a way to determine how long a sensor has been in a warning state. This makes it difficult to distinguish between sensors that just entered a warning state and those that have been generating warnings for extended periods (hours, days, or weeks).
Feature Request:
Please add warning state duration information to PRTG with the following components:API Access (Most Important):
- Add a "warningduration" or "timeincurrentstate" field to the sensor API endpoints
- Enable filtering/querying sensors by warning duration via API parameters
- This would allow for automated reporting and custom…6 votes -
Expand SSL Certificate Monitoring Beyond HTTPS
As a PRTG network administrator, I want to monitor SSL certificates for both HTTPS and MS SQL Server connections, so that I can proactively manage certificate expiration across all critical services without relying on complex external scripts.
Since the current SSL Certificate is only for web (HTTPS) ports, it might be useful to update the name to "HTTPS SSL Certificate".
Within the scope of MS SQL Server's connection SSL Certificate for the 1433 port, it will be useful to provide a way to monitor the certificate's expiry date. There is a number of pages with Python scripts that will pull…
7 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.
2 votes -
Cisco ACI sensor
As an Enterprise Network Administrator managing Cisco ACI infrastructure I want a dedicated Cisco ACI sensor in PRTG so that I can monitor the health, performance, and status of my Application Centric Infrastructure fabric without needing separate monitoring tools or complex custom scripts.
Background:
With the increasing adoption of software-defined networking and the complexity of modern data center environments, customers using Cisco ACI need comprehensive monitoring capabilities. Currently, monitoring ACI requires either expensive third-party tools, custom API integrations, or basic SNMP monitoring that misses critical ACI-specific metrics like fabric health scores, policy compliance, and tenant-specific performance data.8 votes -
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…1 vote
- Don't see your idea?