If I have a Remote Probe at a branch office, is there a way to have the devices/sensors send their status/data to the Core server during the time the remote probe is offline for a reboot? Is there such a setting as precedence for sensors, so that if primary (Remote Probe) is offline, then use a secondary (Core server)? I appreciate the Remote Probe can be paused for normal downtime, but if the remote probe has a major issue, then the Core server would think all devices connecting to the remote probe are down too when in fact they weren't.
Sensors and Remote Probes
Modified on 2025-06-10 16:28:49 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The main objective of a remote probe is to provide access to its network to the Core Server. If the Probe is not available, the Core Server can't reach the target network (in most cases, that won't apply for Remote Probes in the same network as the Core). When the remote probe is down, it should simply state it's disconnected, while ignoring the devices beneath it, as PRTG has no data for them then.
In short - it's not possible to redirect sensors to the core once it's corresponding remote probe is not available due to a disconnect.
PRTGapi | Feature Requests | WMI Issues | SNMP Issues
Kind regards,
Stephan Linke, Tech Support Team
Apr, 2019 - Permalink