Organize Probes by Division and Groups for Better Management
As a network administrator at a large company with multiple sub-divisions, I want to organize probes into hierarchical groups by division so that I can better manage and navigate our monitoring infrastructure.
Division 1
├── Probe 1
│ ├── Group 1
│ │ ├── Device 1
│ │ │ ├── Sensor 1
│ │ │ └── Sensor 2
│ │ └── Device 2
│ └── Group 2
├── Probe 2
└── Probe 3
Division 2
├── Probe 1
├── Probe 2
└── Probe 3
-
Jürgen Cechak
commented
When devices are distributed across multiple probes, PRTG automatically organizes them in the Devices tab under their respective probe and group hierarchy. There is currently no way to display all devices of a given type (e.g. all Windows servers) in a single, flat, alphabetically sorted list that spans all probes.
The Libraries function does not solve this either: each library node only accepts one linked object, and creating multiple nodes simply recreates the same separated structure. Maps are a visual workaround but not a true list/table view with sorting, filtering and sensor status columns.
Proposed solution:
Add a cross-probe "flat view" option to the Devices tab (or extend Libraries to accept multiple linked devices in a single node), allowing users to:list all devices across every probe in one combined view
sort alphabetically by device name
filter by tag, device type or status
keep full access to sensor data and context actionsUse case / benefit:
Faster troubleshooting in environments with many probes
Consistent overview comparable to single-probe setups
No need to maintain Maps purely for inventory purposes
Better scalability as installations grow and more remote probes are added -
Jens Tore Fremmegaard
commented
As an MSP with tons of remote probes grouping of them is a highly needed feature
-
Chee Keong Yong commented
easy manage remote probe in grouping
-
Maxime Pixel Pixel
commented
We are an IT service provider for many companies and sometimes need to deploy multiple probes for a single client. It would be relevant to be able to group these probes together under a group named after the client. Currently, PRTG does not allow this with the existing hierarchy, which only supports groups below a probe.