12 results found
-
When will we get a 64-bit probe?
When will there be a 64-bit version for Windows Probe, or a Linux-based MultiProbe with full functionality?
The 32-bit version is overwhelmed in large environments with multiple remote probes, some with up to 6,000 sensors.19 votes -
High Availability Remote Probes with Automatic Sensor Replication and Failover
As an IT Infrastructure Manager, I want to deploy redundant remote probes that automatically replicate sensor configurations and provide seamless failover capabilities, so that I can ensure continuous monitoring coverage without manual intervention during probe outages and eliminate single points of failure in remote locations.
In environments where uptime and monitoring continuity are critical — especially in OT and industrial networks — a single PRTG Remote Probe represents a potential single point of failure. Currently, if a probe goes offline, all sensors assigned to it immediately lose visibility until the probe is restored.
I propose a High Availability (HA) Probe…
15 votes -
Synchronized Release of Multi-Platform Probe Updates with PRTG Core Server Releases
As a Systems Engineer responsible for patching and maintaining our PRTG environment, I want the matching multi-platform probe package to be published at the same time as each PRTG core server release, so that I can patch my entire PRTG environment (core server and all probes) in a single, coordinated maintenance window and keep my patch management process compliant and streamlined.
Currently, there is one week between the main release and the release of the MPP Version. This causes issues in our patch management which we would like to streamline. It would help for updates to be released immediately.
1 vote -
Centrally Managed Auto-Update for Multi-Platform Probes (Parity with Classic Remote Probes)
As a Systems Engineer managing PRTG multi-platform probes across multiple remote sites, I want multi-platform probes to update automatically from the PRTG core server when the core server is updated — the same way classic remote probes do — so that I don't need to obtain access to each remote system and perform manual package updates, saving time and keeping all probes on compatible, current versions without site-by-site effort.
Background:
We have the Multi-platform probe on multiple sites and would like the option to auto-update these sites together with the core-server in the same way the classic remote probe does.…1 vote -
Organize Probes by Division and Groups for Better Management
As a network administrator at a large company with multiple sub-divisions, I want to organize probes into hierarchical groups by division so that I can better manage and navigate our monitoring infrastructure.
Division 1
├── Probe 1
│ ├── Group 1
│ │ ├── Device 1
│ │ │ ├── Sensor 1
│ │ │ └── Sensor 2
│ │ └── Device 2
│ └── Group 2
├── Probe 2
└── Probe 3Division 2
├── Probe 1
├── Probe 2
└── Probe 310 votes -
Assisted sensor migration from classic Windows probes to multi-platform probes (with history preservation)
As a Systems Engineer decommissioning Windows hosts, I want a guided tool that maps existing sensors on a classic Windows probe to their equivalent multi-platform probe sensors, transfers their settings, and preserves (or links) their historic data, so that I can migrate my monitoring to Linux-based probes without days of manual re-creation and without losing the history my organization relies on for reporting and trend analysis.
Background:
The newly available MPP probe on a linux platform is a good move in the right direction, but we have discovered that sensors can not be moved from Windows probes to MPP probes,…1 vote -
Configurable Sensor Limit per Remote Probe (to prevent license overuse)
For us as an MSP, it is important to be able to define a clear upper limit for the number of sensors that can be used per remote probe.
Some remote probes run within our customers’ infrastructure. At the same time, customers have write permissions within their probe so they can independently add and manage devices and sensors in their environment. This creates a risk that more sensors may be activated than permitted by the license and billed by us.
Manually checking the sensor count per customer is no longer a modern approach and is difficult to scale reliably in…
5 votes -
Remote Probe Installation for PRTG Non-Admin Users
As a PRTG Administrator, I want to be able to allow PRTG users in non-administrator groups the ability to download and install remote probes.
We're an MSP with a wide variety of needs and technical staff, we've sought to develop PRTG groups in conjunction with SSO to better control access to our environment (admins, full control, read-only, etc.).
During that process we discovered that only select users who are members of the 'Administrators' group - the same group with control over user accounts, groups, and setup settings - have the ability to download and install remote probes to set up…
6 votes -
Streamline the multi-platform probe experience for PRTG
Integrate the NATS server and simplify the multi-platform probes installation and set up process with self-signed certificates.
10 votes -
Count of sensor types per probe
As a PRTG admin I want to know what sensor types are on each probe. For example if there are heavy probes like WMI running I have a more limited capacity on the probe so having the count would be helpful so that I can manage probe capacity (could be an addition to the PRTG Status page /status.htm?tabid=1).
10 votes -
Nagios/Icinga Check Results Push Probe for PRTG Integration
Organizations with existing Nagios/Icinga deployments have invested significant time and effort in configuring custom checks, plugins, and monitoring logic. Rather than recreating these checks in PRTG, they want to leverage their existing Nagios/Icinga check configurations and push the results directly into PRTG for centralized visibility and management.
As a Systems Engineer with existing Nagios/Icinga monitoring infrastructure,
I want a PRTG probe that can receive and process check results from my existing Nagios/Icinga checks,
so that I can leverage my current monitoring investments and display all check results within PRTG's interface without having to recreate or duplicate my monitoring configurations.Desired…
1 vote -
Multi-platform Probe on Kubernetes Cluster
User Story:
As a Platform Engineer managing distributed Kubernetes infrastructure,
I want to deploy PRTG Multi-Platform Probes natively within Kubernetes clusters
so that I can ensure continuous network monitoring with high availability and reduced infrastructure complexity.Acceptance Criteria:
- PRTG Multi-Platform Probes can be deployed as native Kubernetes resources (e.g., via Helm chart or Operator) without requiring Docker-specific host capabilities.
- The deployed probes support high availability and auto-recovery.
- All core probe monitoring features are functional and compatible when running inside Kubernetes, matching the capabilities available on standard Docker or VM-based deployments.2 votes
- Don't see your idea?