As an IT Infrastructure Manager, I want the "Add Sensor" catalog to reflect all protocols and target system types that PRTG supports (including REST API, OPC UA, Modbus, and IoT/OT protocols), so that I can quickly discover the right sensor for any device in my environment - whether it's a traditional IT asset, an IoT device, or an OT system.

Furthermore, I want the sensor catalog to show the latest version (v2) of a sensor type first when I search or browse, so that I naturally adopt the most current and best-supported sensor without having to scroll past outdated alternatives.

Background:

The "Add Sensor" catalog page in PRTG serves as the primary interface where users discover and select sensors to deploy. It is also used during presales demonstrations to showcase PRTG's monitoring breadth. Currently, this page has two significant shortcomings:

1. Missing protocols and target system categories: The catalog does not reflect the full range of protocols and device types that PRTG actually supports. Newer protocols such as REST API, OPC UA, Modbus, and other OT/IoT protocols are absent from the catalog's filter/category structure, even though PRTG has sensors that use them. Similarly, target system categories like IoT devices, load balancers, and application-level systems are not represented. This makes PRTG appear less capable than it actually is.

2. Legacy (v1) sensors are promoted over modern (v2) sensors: When a user searches for a common sensor type (e.g., Ping), the catalog displays the legacy v1 sensor first and prominently, while the improved v2 version appears further down the list — often below unrelated sensor types. This actively steers users toward outdated sensors and undermines the adoption of newer, better-performing v2 sensor types.