This article applies as of PRTG 21.4.73

The Multi-Platform Probe (early alpha) for PRTG

With PRTG 21.4.73, we introduced the Multi-Platform Probe to extend the native monitoring capabilities on non-Windows platforms, for example Linux, Raspberry Pi, or NAS systems.

Info: ARM systems are now supported.

Content:

1. Disclaimer

2. Supported platforms

3. Limitations

4. Components

5. Download and installation

6. Frequently asked questions (FAQ)

7. Future

1. Disclaimer

Important: The Multi-Platform Probe is currently in the alpha phase. Unexpected issues can occur. We do not recommend that you use the feature on your production system.

2. Supported platforms

Disclaimer: We officially support the operating systems mentioned in the table below. You can try to run it on different operating systems on your own risk. We do not recommend that you use the probe on your production system.

Info:

• If you want to use the Multi-Platform Probe in one or more Docker containers, you can find a comprehensive installation guide here.
• If you want to follow a step-by-step guide, see here.
  

3. Limitations

The Multi-Platform Probe is currently in the early alpha phase. Be aware that features are still missing and that the functionality is limited. The following features are currently not supported:

• Paessler PRTG Hosted Monitor is not yet supported.
• Only the most recent version of PRTG is supported.
• Clusters aren't supported.
• Probes cannot be updated automatically.
• The auto-discovery, template, and System Information features are not yet available.
• Multi-Platform Probes currently support the following sensors:
  • Beckhoff IPC System Health
  • Cisco Meraki License
  • Cisco Meraki Network Health
  • Cloud HTTP v2
  • Cloud Ping v2
  • Dell EMC Unity Enclosure Health v2
  • Dell EMC Unity File System v2
  • Dell EMC Unity Storage Capacity v2
  • Dell EMC Unity Storage LUN v2
  • Dell EMC Unity Storage Pool v2
  • Dell EMC Unity VMware Datastore v2
  • DNS v2
  • FortiGate System Statistics
  • FortiGate VPN Overview
  • HPE 3PAR Common Provisioning Group
  • HPE 3PAR Drive Enclosure
  • HPE 3PAR Virtual Volume
  • Local Folder
  • Microsoft 365 Service Status
  • Microsoft 365 Service Status Advanced
  • Modbus RTU Custom
  • Modbus TCP Custom
  • MQTT Round Trip
  • MQTT Statistics
  • MQTT Subscribe Custom
  • NetApp Aggregate v2
  • NetApp I/O v2
  • NetApp LIF v2
  • NetApp LUN v2
  • NetApp NIC v2
  • NetApp Physical Disk v2
  • NetApp SnapMirror v2
  • NetApp System Health v2
  • NetApp Volume v2
  • Network Share
  • OPC UA Certificate
  • OPC UA Custom
  • OPC UA Server Status
  • Ping
  • Ping v2
  • Port v2
  • Redfish Power Supply
  • Redfish System Health
  • Redfish Virtual Disk
  • REST Custom v2
  • Script v2
  • Soffico Orchestra Channel Health
• The Scan Now option is not yet implemented.
• Simulated error states do not have an effect.
• The system time between probes and the PRTG core server are not synchronized. The probe always uses the time zone that the PRTG core server uses. This can cause gaps in graphs if the connection between the probe and the PRTG core server was lost.
• Ping sensors only support IPv4.

Note: The path in which you must place the scripts for the Script v2 sensor on a Windows Multi-Platform Probe differs from the path on the PRTG core server system and probe system.

• Script path for Windows: C:\Program Files\Paessler\PRTG_MPP\custom sensors\scripts

• Script path for Linux: /var/local/prtg/scripts

4. Components

The Multi-Platform Probe consists of three different components:

1. NATS server
   • The NATS server handles the communication between Multi-Platform Probes and the PRTG core server.
   • Note: We recommend that you do not install the NATS server on the PRTG core server system.
2. Probe adapter
   • The probe adapter on the PRTG core server system
3. Multi-Platform Probe
   • The Multi-Platform Probe is where the actual monitoring takes place.
   • Note: We recommend that you do not install the probe on the PRTG core server system.
     
     Click to enlarge.

5. Download and installation

Follow the steps below to enable the use of the Multi-Platform Probe with PRTG Network Monitor.

Notes:

• We recommend that you do not install the NATS server and the Multi-Platform Probe on the PRTG core server system.
• Even though we have signed the scripts with our official code signing certificate, PowerShell may ask if you want to run a script from an untrusted publisher. If you select A for 'Always Run', the Paessler code signing certificate will be added to your trusted publishers and you will not be asked again. Right-click the script to see the certificate chain for verification.
• You can find our setup tutorial videos here:
  • Linux: PRTG Tutorial - Setup multi-platform probe - Linux
  • Windows: PRTG Tutorial - Setup multi-platform probe - Windows

5.1 Download and install the NATS server

1. Download the correct script for your operating system. The script guides you through the installation process of the NATS server that is used for the communication between the Multi-Platform Probe and the PRTG core server.

Note: If you run the NATS server on a system that is not the PRTG core server system or the probe system, you must open a port in the firewall of the system that runs the NATS server.

5.2 Download and install the Multi-Platform Probe

Note: These scripts are the same as for the NATS server installation. You do not have to download the scripts again if you already downloaded them.

1. Download the correct script for your operating system. The script guides you through the installation process of the Multi-Platform Probe.

5.3 Download and install the probe adapter

1. Download the script and run it.

2. Add an Access Key under Setup | System Administration | Core & Probes in PRTG. The default access key is multi-platform-probe.

Notes:

• After you successfully install the Multi-Platform Probe, a dialog box appears in PRTG. Click Approve to include the new probe in your device tree.
• Do not click Approve and auto-discover. The Multi-Platform Probe does not support auto-discovery.

5.4 Run the NATS server or the Multi-Platform Probe on Docker

1. You can find a comprehensive guide for running the NATS server or the Multi-Platform Probe in a Docker container here.

6. Frequently asked questions (FAQ)

6.1 NATS server

6.1.1 I'm getting the following error during the installation process on Windows. What should I do? .\install-mpp-nats.ps1 : File <File Path> cannot be loaded because running scripts is disabled on this system.”.

1. Execute the following command: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine 2. Enter Y to confirm and press enter.
3. Execute the install-mpp-nats.ps1 script again.

6.1.2 Where can I find the logs of the NATS server?

• Windows: C:\ProgramData\Paessler\PRTG_NATS
• Linux: /var/log/prtg/nats-server/

6.1.3 How can I change the configuration values?

Choose between the following approaches:

• Run the installation script again and select the settings you want.
• Modify the configuration without running the script again.
  • Windows: Modify the configuration under C:\ProgramData\Paessler\PRTG_NATS and restart the service PRTGNATSServerService after you made your changes.
  • Linux: Modify the configuration under /etc/prtg/nats-server/prtg-nats.config and restart the service by using the following command:

sudo systemctl restart prtg.nats-server.service

6.2 Probe adapter

6.2.1 Where can I find the logs of the probe adapter?

The probe adapter logs are stored in the PRTG program directory under C:\ProgramData\PRTG Network Monitor\ProbeAdapter. Additionally, the logs are written to the file Probe.log under C:\ProgramData\Paessler\PRTG Network Monitor\Logs\probe.

6.2.2 How can I change the configuration values?

Choose between the following approaches:

• Run the installation script again and select the settings you want.
• Modify the configuration without running the script again: Edit the file config.yaml under C:\Program Files (x86)\PRTG Network Monitor\ProbeAdapter\ and restart the PRTG core server service for your changes to take effect.

6.3 Multi-Platform Probe

6.3.1 Where can I find the logs of the Multi-Platform Probe?

• Windows: C:\ProgramData\Paessler\PRTG_MPP\probe_logs
• Linux: /var/log/prtg/mpprobe/

6.3.2 How can I change the configuration values?

• Windows: The configuration on Windows is done via environment variables.
  • The corresponding variables have the prefix PRTGMPPROBE_. Restart the service PRTGMultiPlatformProbeService after you made your changes.

• Linux: The configuration on Linux is done via environment variables as well.
  • Run prtgmpprobe –help for information about the relevant variables. The Multi-Platform Probe service uses the environment file at /etc/prtg/mpprobe/config.env. Run the following command after you made your changes:

sudo systemctl restart prtg.mpprobe.service

6.3.3 I'm getting the following errors when running the install script, what should I do?

Line 7: read: Illegal option -d
Line 85: function not found
Line 87: Syntax error: "}" unexpected

This likely means that you are trying to run the script with a shell other than Bash. Try to run the install script with the following command: sudo bash install-mpp-nats.sh

6.3.4 I'm getting the following errors in the probe log when running the probe adapter, what should I do? Could not create probe adapter: Initialization error ret: 7 for Dll="*PRTGPATH*\ProbeAdapter\probe_adapter.dll"

The error indicates that the probe adapter is unable to connect to the NATS server.

Try out the following:

• Install the NATS server on the same system where the probe adapter or probe is running to make sure you can make a connection.
• Check that your NATS server is listening on the correct port that has traffic being forwarded to it.
• Check the IP addresses and passwords in your configurations.
• Add debug:true to the NATS server configuration to see the incoming connection attempts. For more information about the NATS server configuration, see question 6.1.3 How can I change the configuration values?

7. Future

The Multi-Platform Probe is currently very limited with its supported features. In the upcoming weeks, we will introduce support for templates, auto-discovery, and other features. This will extend the available sensors on the probes by the following sensor families: Microsoft Azure, AWS, and Veeam. We would also love to hear your feedback about what else you would like to see on the Multi-Platform Probe.

Share your input with us in the Multi-Platform Probe survey here.