IMPORTANT NOTICE: in UXI, test results and issues produced by the sensors have the context of their group. This helps us aggregate data in the dashboard, apply filters, build reports, and more. However, if you move a sensor from one group to another, only new data is represented in the updated group. This may result in some of the views in the dashboard appearing grey or "offline" until there is new data. The best way to see a sensor status page without the context of its parent group is to search for the sensor directly. This shows you all the data for the sensor regardless of the group.

Configuring your UXI sensors and agents just got easier. Instead of applying configuration one sensor at a time, you can now organize them in a hierarchy allowing for streamlined configuration, which is especially useful when managing a large number of sensors.

The new method allows you to create a hierarchical structure, up to 10 levels deep, that organizes your sensors, networks, and services. Sensors and Agents inherit their configuration from the level they are assigned to, eliminating the need for manual setup at the individual sensor level.

This article will walk you through the new process step-by-step.

You can create a hierarchy with up to 10 levels, providing flexibility in organizing your sensors.

Example hierarchy levels might include:

Note 1: We do not allow dragging groups under other groups. The group structure needs to be deliberately created. This is because inheritance is complicated. For example, if you drag a group under another group, there are complex questions about what should happen to the assignments and underlying resources associated with the groups. The group structure needs to be explicitly defined to avoid someone accidentally making a change they didn’t expect.

Note 2: You cannot delete a group if sensors are assigned to the group or any child group. The sensors need to be moved first before you can delete the group. If you delete a group with tests or networks assigned, you will see a warning but can still delete the group.

It’s recommended to start with network assignment so that when you assign sensors, the sensors immediately start testing.

The Manage tab allows you to create or modify networks you want to test in settings under Wireless or Wired.

Select the Assign tab in the top right corner to assign a network to the hierarchy.

On the Assign tab, you can search in both the left box for the network you want to assign and the box on the right for where you want the network assigned in the hierarchy.

Make your selection or deselection and click apply.

Sensors and agents also have Manage and Assign tabs in the top right corner. In the Manage tab you can search for a sensor or agent, or apply filters. Once you locate a sensor or agent you can edit a sensor to change the sensor name, set the pcap mode or update the notes.

On the Assign tab, sensors and agents can now be assigned at any level of the hierarchy. Once assigned, the sensors will inherit the configurations of all levels above.

Note that for agents, a network needs to be assigned to a group the agent is assigned to. This is a change from the previous behavior where the network the agent was going to test only needed to exist.

Services also have Manage and Assign tabs in the top right corner. In the Manage tab, you can add tests or search for a test, or apply filters. When you edit a test there are now two new options:

On the Assign tab, tests can now be assigned at any level of the hierarchy. When you assign tests, you can also select what networks you want the test to apply to. Untoggle the test on any network and choose the ones you want to apply the test to.

Instead of manually configuring each sensor, sensors and agents automatically inherit their configurations (networks, services, and tests) from their assigned hierarchy.

This reduces the need to repeat configurations for individual sensors and also ensures consistent configurations across sensors by leveraging inheritance.