76 results found

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

   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

   Gathering Feedback  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. 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 SNMP-based network monitoring and not an exception.

   Example OIDs / vendor context:
   Aruba example table OIDs: .1.3.6.1.4.1.47196.4.1.1.3.15.1.2
   Aruba example table OIDs: .1.3.6.1.4.1.47196.4.1.1.3.15.1.4
   The Aruba OIDs show that many values are returned as strings rather than purely numeric values. This is standard practice in SNMP network monitoring.

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

   Under Review  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Redfish Fan State sensor

   As a PRTG user, I want a single sensor per server (HPE, Dell, Lenovo, Supermicro, etc.) that monitors all fans via Redfish, so that I get a consolidated view of fan health and speeds without cluttering my device tree with one sensor per fan.

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   On Roadmap  ·  AdminJörg Hollerith (Product Manager, Paessler) responded

   Hi there,

   Great news! Your idea has been reviewed and is now officially on our roadmap! This means we've committed to developing it in the future.

   While we don't have an exact release date yet, we're planning to implement this feature/improvement as part of our upcoming development cycles. We're excited about the value this will bring to our users.

   We appreciate your patience as we work to bring this to fruition. We'll let you know once it moves into active development.

   Thanks for helping us build a better Paessler!

   Best regards,

   The Paessler Product Team

4. Redfish Temperature Sensor

   As a PRTG user, I want to monitor individual temperature readings from any Redfish-compliant server (HPE, Dell, Lenovo, Supermicro, etc.) — one sensor instance per temperature probe — so that I get granular thermal visibility and per-sensor alerting.

   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

   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   On Roadmap  ·  AdminJörg Hollerith (Product Manager, Paessler) responded

   Hi there,

   Great news! Your idea has been reviewed and is now officially on our roadmap! This means we've committed to developing it in the future.

   While we don't have an exact release date yet, we're planning to implement this feature/improvement as part of our upcoming development cycles. We're excited about the value this will bring to our users.

   We appreciate your patience as we work to bring this to fruition. We'll let you know once it moves into active development.

   Thanks for helping us build a better Paessler!

   Best regards,

   The Paessler Product Team

5. 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, there's one critical thing missing. While the Charge Remaining channel does have warning/error limits configured for alerting (by default, 50% remaining and 20% remaining, respectively), the Battery Status always shows "Battery Normal". It may be that the battery status is indeed normal and functioning, but when the UPS has lost utility power and is running on battery, there's no way to know that the UPS is now on battery without looking at the charge level or waiting for it to hit a charge limit for alerting, because the Battery Status remains "Battery Normal", even when utility power is lost. It would be handy to have a way to determine on the next sensor scan if a UPS has switched to battery power, indicating utility power has failed.
   I'd propose a new channel for this sensor, in addition to Battery Status, called "Output Source". If I check the Eaton MIB, the OID 1.3.6.1.2.1.33.1.4.1.0 shows a value of either "normal" (when the UPS is on utility power), or "battery" (when the UPS has switched to supplying power via the battery). This would be a perfect addition to this built in SNMP UPS Status Sensor, where "normal" would be an OK status, and "battery" would be a Warning status in PRTG.
   Alerting on the Output Source channel could also be disabled by the user if they have a UPS that operates in such a way that the output source is always the battery, and is constantly being topped up by AC power.

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

   Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Proxy Support for SSL Certificate Sensor

   As an IT Infrastructure Manager operating PRTG in a network without direct internet access,
   I want the SSL Certificate sensor to natively support the HTTP proxy settings configured on the parent device,
   so that I can monitor the SSL/TLS certificates of external websites through our proxy — just like I already can with HTTP-based sensors — without needing to rely on a separate monitoring tool.

   Background: We are using PRTG without direct internet access. With the proxy setting of the device we can monitor a HTTPS website, but not the SSL certificate of that site. That is a problem for us (we are currently still using our old monitoring tool for just that purpose because PRTG can't do it).

   As an IT Infrastructure Manager operating PRTG in a network without direct internet access,
   I want the SSL Certificate sensor to natively support the HTTP proxy settings configured on the parent device,
   so that I can monitor the SSL/TLS certificates of external websites through our proxy — just like I already can with HTTP-based sensors — without needing to rely on a separate monitoring tool.

   Background: We are using PRTG without direct internet access. With the proxy setting of the device we can monitor a HTTPS website, but not the SSL certificate of that site. That is a problem for… 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

   In Progress  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   Under Review  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Enable Auto-Acknowledge for Ping v2 Sensor Alerts

   As an IT Infrastructure Manager managing a large-scale monitoring environment,
   I want the ability to enable automatic acknowledgment of alerts on Ping v2 sensors,
   so that I can use Ping sensors for lightweight availability tracking and state logging without being burdened by a high volume of alerts that require manual acknowledgment.

   Background:
   In the legacy Ping sensors, there was a feature that allowed automatic acknowledgment of alerts (auto-ack).
   We use Ping sensors across a large number of devices primarily for visibility. They act as a lightweight form of logging and state tracking.
   Notifications are still triggered as needed, but we do not require manual acknowledgment for every alert.
   Without auto-ack, managing a high volume of alerts becomes operationally heavy and reduces the usability of these sensors in our environment.

   As an IT Infrastructure Manager managing a large-scale monitoring environment,
   I want the ability to enable automatic acknowledgment of alerts on Ping v2 sensors,
   so that I can use Ping sensors for lightweight availability tracking and state logging without being burdened by a high volume of alerts that require manual acknowledgment.

   Background:
   In the legacy Ping sensors, there was a feature that allowed automatic acknowledgment of alerts (auto-ack).
   We use Ping sensors across a large number of devices primarily for visibility. They act as a lightweight form of logging and state tracking.
   Notifications are still triggered as needed, but we… 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

   In Progress  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   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

   Gathering Feedback  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Synology NAS Sensor Support on the Multi-Platform Probe

    As a Systems Engineer, I want to be able to use Synology NAS sensors on the multi-platform probe, so that I can monitor my Synology storage devices from Linux-based or containerized probe environments without depending on a Windows remote probe

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. HPE ProLiant Sensor Support on the Multi-Platform Probe

    As a Systems Engineer, I want to be able to use HPE ProLiant sensors on the multi-platform probe, so that I can monitor my HPE server hardware from Linux-based or containerized probe environments without depending on a Windows remote probe.

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Enhanced Cisco Catalyst 9800 WLC Monitoring Sensors

    As a Network Engineer, I want comprehensive, out-of-the-box sensors for the Cisco Catalyst 9800 Wireless LAN Controller — covering SSID status, per-SSID client counts, per-SSID traffic, WLC high-availability status, and disk space — so that I can proactively manage my wireless infrastructure without relying on manual CLI checks or custom workarounds.

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. HPE VM Essentials (VME) Cluster Monitoring Sensor

    As an IT Infrastructure Manager,
    I want native PRTG sensors for HPE VM Essentials (VME) clusters that monitor cluster health, host performance, VM status, and resource utilization,
    so that I can maintain unified visibility across my virtualization environment after migrating away from VMware, without relying on manual custom sensor configurations.

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    6 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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. 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 Enterprise Manager as V13 provide API endpoint.

    This will provide Veeam Backup job monitoring to PRTG customers who don't have any Enterprise Manager Console license and for a security improvement, will not require an admin user for this monitoring purpose.

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

    13 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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. 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 not clearly indicate which resource (CPU, memory, or I/O) is causing contention.

    Modern Linux kernels provide a more advanced metric called Pressure Stall Information (PSI) that directly measures resource pressure. PSI exposes how long tasks are stalled waiting for CPU, memory, or I/O resources, providing a much clearer indicator of real performance bottlenecks and system saturation.

    PSI metrics are available in modern kernels via:
    /proc/pressure/cpu
    /proc/pressure/memory
    /proc/pressure/io

    Why PSI support would benefit PRTG users:

    • More accurate detection of CPU, memory, and I/O contention

    • Earlier identification of performance bottlenecks

    • Better alerting and capacity planning

    • Alignment with modern Linux observability practices

    • Reduced need for custom SSH script sensors

    • Currently, PSI monitoring can only be implemented via custom scripts, which reduces maintainability and standardization in larger environments.

    Suggested implementation:

    • Introduce a dedicated “Linux PSI Sensor”

    • Or extend existing Linux sensors to include PSI channels (CPU, memory, I/O pressure)

    Native PSI support would greatly improve Linux performance monitoring in PRTG.

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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    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

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating