Lumeta provides a number of map features designed to make it easier to stay apprised of network change without having to keep your eyes trained on the screen. These include beaconing, visual effects, on-screen messaging, more white space for the map, and the deliberate use of color.
Node Contrast
- Active nodes—those that are responsive to a Lumeta scan—are blue.
- Inactive nodes—those that are unresponsive to a Lumeta scan—are grey.
Beaconing
To draw your attention to a node in need of attention, you'll see a beaconing effect.
See Subscribing to Notifications to learn how to configure and subscribe to event notifications.
Hover Text
Those who use screen readers or anyone who does not know what buttons on the toolbar do.
| Full-screen mode - Clears the visual noise. Displays the map on the whole screen, hiding the page header, footer and controls |
| Preferences - This icon lets you set map preferences |
Highlighting
Active/Inactive Highlight View
Custom Attribute Highlighting - Highlights all nodes having and attribute value you specify.
Device Counter
The highlighting sidebar shows a list of categories with quantity counts beside each category. This count reflects visible nodes on the map only. When a node isn't displayed, it doesn't count. If you want to have all devices included in the total, then expand all devices.
To add a new item to the Highlight menu, add a new custom attribute.
To color devices on the map according to your custom attribute,
- Click the small box.
- Select a color.
- Exit.
Browse to Highlighting button > Custom Attribute
Select the custom attribute to highlight.
- If you define two custom attributes with different casing e.g., "Location" vs "location," both should work.
- If the user defines two different custom attributes with the same value, the user should be able to assign color preferences to each one without them overwriting each other (This requires a refactor to how the map saves highlight colors)
- The custom attribute selector should only appear if the Custom Attributes view is activated. In other words, we should not see this selector when the Active/Inactive view is activated.
- Long custom attribute names and values. The map UI should truncate these where necessary with a tooltip including the verbatim text, as we do elsewhere.