Some sensor types have been removed from PRTG! We removed some sensor types from PRTG as announced previously. Sensors of this type stop monitoring and show a down status as of the PRTG version you are about to install. See more below.
The Mobile WebGUI has been removed from PRTG! We have completely removed the Mobile WebGUI from PRTG as announced previously. You will not be able to login to this interface anymore as of the PRTG version you are about to install. See more below.
The SSL Security Check sensor changed the security rating of TLS 1.0! We changed the behavior of the SSL Security Check sensor. It will show a warning status (weak security) for accepted TLS 1.0 connections as of the version you are about to install.
This article applies to PRTG Network Monitor 16.x.23 or later
The PRTG Sensor Cleanup
You know PRTG as a powerful yet easy-to-use network monitoring solution. When we implement new features we always try to keep complexity as low as possible, so you can do what is important: monitor without configuration hassles. To keep PRTG usage simple for the future, we constantly analyze available features for their benefits and downsides.
We believe you prefer that we focus on features which the majority of PRTG customers use everyday. Niche issues that only affect special use cases of PRTG distract this focus and spending our precious energy on such topics does not improve your overall user experience of PRTG. It is also ineffective when niche problems create substantial workload for both our technical support team and developers while other inquiries have to wait.
To be able to focus on important and popular stuff it is necessary that we reduce code complexity and currently available features like, for example, some sensor types. In this context we recently evaluated the sensor types we ship with PRTG and discussed the following points for each one:
Is it useful for many of our users or is the usage rate very low?
Is it compatible with current systems or does it only support outdated target systems?
Is it easy-to-use and do target systems work flawlessly with it or does it create disproportional workload for you and our support team?
If a sensor type does not fulfill all of these requisites, then it is a potential candidate for removal from the software. Of course, whenever possible, we do not want to impair your monitoring experience, so we also considered options to provide alternatives for such sensor types.
As a result, starting with PRTG 16.x.23, we will deprecate several sensor types (see below) and finally remove them in PRTG 16.x.25. Note that many of the sensors which we remove have already been deprecated in previous versions. However, some of them still exist (but you could not add new instances of them any more). As soon as they are removed, you will not be able to use them anymore after you update to 16.x.25.
Deprecation and Removal of Sensors
The approach for sensors that are deprecated as of PRTG version 16.x.23 is the following:
Deprecated sensors will be marked as such in your PRTG installation.
You cannot add deprecated sensors anymore to PRTG, neither manually nor via Auto-Discovery.
PRTG will additionally inform you about deprecated sensors with tickets.
You can still use deprecated sensors that you added in versions previous to 16.x.23 so you will have enough time to prepare for the final removal, for example, by following a “plan B” (fallback option).
In version 16.x.25, the deprecated sensor will be removed from PRTG:
If you still run deprecated sensors, these sensors will show an error and be in down status as of version 16.x.25. They will not provide any monitoring data as of this version!
You will get a ticket that notifies you about these removed sensors.
Please delete these sensors now to avoid “false” alarms in your installation, or pause them to keep historic monitoring data.
Additionally check your maps, reports, and libraries if they include one of these sensor types. Manually delete them where necessary to avoid incorrect data.
Deprecated Sensor Types and Alternatives
After analyzing the current sensor situation we have decided to remove the following sensor types from PRTG. If possible, we provide also an alternative so you can still monitor the desired data.
There are two categories of deprecated sensor types. There are sensors which we deprecate with version 16.x.23. These are sensors that you can add until this version and run until 16.x.25.
There are also older sensor types which have been deprecated in previous versions (for example, in PRTG 12) and were not addable anymore. Some of them still run but will also stop when they are removed from PRTG 16.x.25. Please check your PRTG installation for such outdated sensors!
Sensor Types Deprecated as of PRTG 16.x.23
The following sensor types are deprecated as of PRTG 16.x.23 and will be removed with PRTG 16.x.25. Please take action if you use one of these sensors, as described here Please see below for translations of deprecated sensor types into your PRTG language version.
Please use the custom ScheduledTask2XML sensor by PRTG Tools Family instead. Note: This sensor type requires Windows 7 or later or Windows Server 2008 or later on the target system. It does not support the outdated operating systems Windows Server 2003, Windows Vista, Windows XP.
Note: We offer a migration path for the deprecated SQL sensors. If possible, gradually replace them with SQL v2 sensors nonetheless. The migration path is intended to give you more time to creating corresponding SQL v2 sensors if you use a large number of deprecated SQL sensors. On how this works exactly, see here.
Sensor Types Deprecated Before PRTG 16.x.23
The following sensor types have been deprecated in PRTG versions before 16.x.23. Some of them might still run on current PRTG versions but will be also removed, so please take action if you still use one of these sensors.
Active Directory Replication Errors (original version)