58 results found
-
Native Veeam Backup & Replication API Integration for PRTG Backup Job Monitoring (Without Enterprise Manager)
As a Systems Engineer managing my organization's IT infrastructure with PRTG, I want PRTG to monitor Veeam Backup & Replication job statuses by connecting directly to the Veeam B&R REST API (v13+), so that I can monitor backup jobs without requiring a Veeam Enterprise Manager license or a portal administrator account, reducing both licensing costs and security exposure.
The current Veeam Backup Job Status (and Advanced) sensors still require and use Veeam Enterprise Manager (and require portal administrator role).
Would be great to refactor or build new sensors to use/connect directly to the Veeam B&R server instead of the Veeam…
18 votes -
Dynamic Interface Naming with ifIndex-Based Port Identification for SNMP Traffic Sensors
As a Network Engineer, I want PRTG SNMP Traffic sensors to dynamically update interface descriptors (ifAlias, ifDesc, ifName) on every scanning interval while using ifIndex as the primary immutable identifier for port identification, so that sensor names remain accurate and searchable when network device interface descriptions are changed through configuration management.
In cases where ifAlias, ifDesc, and ifName are used in port name templates, PRTG SNMP Traffic sensors should always pull these values and update them.
ifIndex should be used by default to identify the ports and the other OIDs should be used as dynamically updating fields on every scanning…
28 votes -
Native Azure Monitoring Sensors at AutoMonX Parity
As a PRTG user monitoring an Azure environment,
I want native Azure sensors in PRTG that provide the same depth and coverage as those offered by AutoMonX,
so that I can monitor my Azure infrastructure comprehensively without relying on a third-party solution, incurring additional costs, or managing a separate contract.Background / Context:
PRTG's current Azure-related sensors cover only basic functionality. While AutoMonX (automonx.com/azure) fills this gap on a commercial basis, prospects and customers increasingly expect a native, fully integrated solution from PRTG itself — one that requires no additional vendor relationship or cost.6 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
-
SNMP Custom Table Sensor: Enable String Value Handling in Channels
As a Network Engineer monitoring multi-vendor network infrastructure,
I want the SNMP Custom Table sensor to support string value handling in its channels (e.g., mapping strings to sensor states or displaying them in the sensor message),
so that I can monitor all relevant data from SNMP tables - including string-based status fields, names, and descriptors, without needing to create individual string sensors or custom scripts for each OID.Background:
In SNMP Custom Table sensors, it is currently not possible to evaluate string returns within channel strings. The user considers this a notable gap, because string returns are very common in…4 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
-
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.10 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…
15 votes -
Native Nginx Status Sensor
As a Systems Engineer running nginx as my web server, I want a dedicated PRTG sensor that reads nginx's built-in status page and turns it into real-time channels for active connections, request throughput, connection states, and dropped connections, so that I can monitor my web server's actual load and health and get alerted before it starts refusing traffic.
4 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…
15 votes -
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.
9 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.14 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…11 votes -
Enable receiving SNMP Traps v3
As a PRTG admin I would like to collect SNMP v3 traps from my devices that support this extra security level. My company and/or customers demand this security step in order to be 100% compliant.
Affected Application
PRTG // PRTG Network Monitor // Sensors and ProbeHow does this improve your daily work?
Hi we got several requests from customers who want to receive SNMPv3 Traps in PRTG.
At the moment only v1 and v2c traps are possible to be received.Our customers request these so to get the software 100% BSI-compliant.
Otherwise they're refraining from procuring the tool at…27 votes -
MQTT Sensors: Support the full MQTT QoS spectrum (QoS 0 / 1 / 2), not only QoS 2
Problem / Current Limitation:
PRTG's MQTT sensors currently hard-require QoS 2 as a fixed, non-configurable part of their implementation — none of PRTG's available MQTT sensor types offer QoS 0 or QoS 1 as an alternative. QoS 0, 1, and 2 are all standard, valid delivery levels defined by the MQTT protocol itself — a broker or service that only offers QoS 0/1 is not doing anything non-standard or unusual, it's simply choosing a different (and very common) point on the QoS spectrum. By hard-coding QoS 2 across the board, PRTG effectively excludes any MQTT broker or managed service that…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 / egress7 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:…6 votes -
SNMP Cisco System Health Sensor: Add "Used Memory " Channel
As a Network Engineer, I want to see a 'Used Memory (%)' channel alongside the existing 'Available Memory' channel in the SNMP Cisco System Health sensor, so that I can choose the metric that best fits my alerting thresholds and dashboards.
2 votes -
Add "Output Source" Channel to SNMP UPS Status Sensor for Utility Power Loss Detection
As a Systems Engineer responsible for monitoring UPS infrastructure,
I want the SNMP UPS Status sensor to include an "Output Source" channel that indicates whether the UPS is supplying power from utility (mains) or battery,
so that I am immediately alerted when a UPS switches to battery power due to a utility outage, without having to wait for the battery charge to drop to a warning or error threshold.Background:
I've just started testing the SNMP UPS Status (NEW) sensor with Eaton UPSs. Having the Battery Status, Charge Remaining, Current Load, and Estimated Time Remaining are all super handy.
However,…2 votes -
Enhanced Script v2 Sensor Placeholder Support
As a Systems Engineer, I want Script v2 sensors to support built-in PRTG placeholders (like %snmpcommunity) so that my scripts can automatically access device credentials without manual configuration (so that Script v2 sensors can do all of the same work that older script sensors could do).
13 votes -
WMI Service Group Sensor
As a systems engineer, I want to monitor groups of related Windows services in a single sensor so that I can quickly identify if any critical service group is not running properly without having to create and manage multiple individual service sensors.
Examples:
- services set with "automatic start"
- multiple services with a specific name in it (e.g. all backup services)12 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.
7 votes
- Don't see your idea?