Paessler has announced a public beta around their on-demand and cloud-based PRTG monitoring software offering! I decided to give their new solution a spin and connect it to my lab environment. Dive into this article to learn more.
As mentioned, the on-demand offering is still in public beta so it is still under development. With this offering, you will no longer require an on-premise installation of PRTG and can start monitoring your infrastructure within minutes.
The following features come with PRTG On-Demand:
- Near-instant deployment (I got mine up and running in less than 5 minutes)
- No need for on-premise monitoring systems
- Automatic up- and downscaling based on the number of systems you want to monitor (sensors)
- No initial investment required (just consume the number of sensors you require)
- Automatic updates
To get PRTG On-Demand up and running, you need to follow these three steps:
- Create an account at PRTG On-Demand here
- Deploy a remote probe that connects your internal infrastructure with the PRTG On-Demand service
- Set up monitoring by adding devices and sensors
The remote probe should preferably be deployed on Windows Server 2012 R2 and the installation package can be fetched from the PRTG On-Demand web interface, as shown in the next paragraph around Setup.
Initial setup and configuration
This paragraph describes how to set up PRTG On-Demand and start monitoring the first system in your infrastructure.
First of all, you’re going to need an account for the PRTG On-Demand trial. Please head to this link and create a new account. See the screenshots below as a reference. The domain name you choose will be used to access the PRTG web interface.
After subscribing, the deployment process will be initiated on Paessler’s end and will change from in progress (first screenshot below) to complete (second screenshot below). After completion, the link highlighted in blue and matching your domain name will be reachable and will give you access to the PRTG web interface (third screenshot below)
At this point, PRTG is ready for consumption and should already contain some basic items as shown below.
Remote Probe Setup
The next step is to link PRTG On-Demand with your environment. This requires you to deploy a so called “Remote Probe”. It’s a piece of software that should be deployed on a Windows Server 2012 R2 system inside your environment. From this system, all monitoring data will be forwarded to PRTG. So make sure that this system can access all systems you want to monitor.
In case that you have a complex network, you might need multiple remote probes to gain access to all systems.
To set up a remote probe, navigate to Setup and click Remote Probe Installer (right hand side under Optional Downloads and Tools in the screenshot below).
The following page will appear and display a download button on the bottom. The software should be downloading and needs to be placed and installed on your designated remote probe system.
The following screenshots display how the setup wizard looks (next-next-finish).
If the connection fails, please make sure port 23560 (TCP) is open from the remote probe system to your PRTG domain name (snowvm.my-prtg.com in my example).
After the remote probe finishes installing, you should get a notification like the screenshot below in PRTG, displaying the system name you installed the probe on.
Approve the new probe like displayed below.
At this point, you can see the new remote probe in the PRTG overview:
The health sensors for your remote probe are automatically added, like disk space, network utilization and overall system health.
Having your remote probe ready, you can now start monitoring your systems. I won’t go into detail here but in the example below you can see that I’ve added a new system (my vCenter server) and included sensors for host hardware and VM health.
All groups and devices you place under your remote probe system (BU01 in my case) will be monitored by that probe. In a case where you have multiple remote probes, make sure devices are under the correct one (based on connectivity).
That’s all! I think it’s very simple to start working with PRTG and enjoy all features in a scalable way. Especially if you’ve never tried PRTG before and don’t want to spin up an on-premise system, just create an account and deploy a remote probe somewhere!
To wrap this article up, I would like to refer to the following other writings I’ve published about PRTG in case you want to learn more about PRTG functionality: