Topographical maps are visualizations that display the connectivity between devices in a user's network. LogicMonitor's Maps (Topology) feature was historically not well liked or widely used by our users.
The Topology Maps redesign more than doubled customer adoption of the Maps features and Maps is featured in all sales demos to potential customers. Further, the Maps features were added to other modules throughout LogicMonitor, including for Cloud Monitoring, Tracing Analysis, and Applications Monitoring.
In collecting feedback on LogicMonitor's Topology Maps we discovered the most common response from users was "We gave it a try, but..." followed by comments that it was difficult to use and not very useful. It was this observation, combined with usage data from Pendo that convinced us that we needed to completely redesign and re-engineer Maps.
One area where Maps was failing our users was the "Welcome" screen for Maps. It lacked visual impact and conveyed almost no information about the map except for the name.
Another area of concern was that the Map provided very little information to the users. It would display the devices, the connection, and the status (if the device was in Alert), but little else. The user could not see any details or properties of the map. And, if the device was in Alert, they could not effectively explore the nature of the problem.
Maps were present in several places with LogicMonitor, however, the controls for Maps changed in each location. This made for a very confusing user experience.
Maps are essentially a Data Visualization. As such, it needs to be aesthetically pleasing and impactful. The feedback from users and other stakeholders was that the existing Topology Maps where neither.
The initial testing of the existing Topology Maps features was to interview several customers and observe them as they worked with maps in their company's environment (Contextual Inquiry). From this, we were able to identify the issues discussed above and to create a set of broad Use Cases for map usage.
What is the structure of my network? What is THIS device connected to? How are THOSE devices connected?
Is there a problem in my network? Are any devices in alert? What is the scope of the problem?
What is the Root Cause of the problem? Is THIS device the root cause? Or, is some OTHER device the cause?
I need to show the network to others to help them understand the network.
From these broad Use Cases we were able to understand how the current design failed and guide us in the design.
We reviewed the Topologies in several competative products, including Solar Winds, Data Dog, and Auvik.
In the review we documented a number of common patterns:
Clear delineation between devices with problems and those without.
Device type was clearly marked with clear iconography (outer shape and interior icon) and by color.
Metrics reported on the topology (e.g. thickness of the connecting line indicating traffic).
A 'drill in' experience.
Extensive information presented about each device presented with the Topology.
"Welcome" pages that were inviting, informative, and visually interesting.
Based on the extensive information we collected, we began a process of trying and testing different designs with users and stakeholders, iteratively testing and redesigning.
This early design included several of the ideas discussed with users, including an emphasis on drill down. Several elements of this design will be part of the final Topology product.
This version of the design explored both the idea of grouping devices in the view (a request from certain users) and of using a richer iconography for the nodes.
This version was one of the last iterations before the design was approved for development. It removes the header graph and sidebar navigation for MVP, but has the look of the final map and the details within the bottom panel.
The new Topology was released in certain environments in July of 2021 and the full MVP of the "Maps" feature was released in February of 2022. The images below are taken the MVP released to users.
The new Topology Maps was very well received by our users and is now a central feature of LogicMonitor. Maps are now used for Cloud Monitoring, APM, Traces, and Website monitoring.
The user can now select from several layouts for the Topology. The Type and Alert Status of each node is now clearly marked on the Map.
Selection of a node opens a Detail's panel that contains the properties of the device, information about active alerts, graphs, etc. Future releases will include more detailed information.
Users can select nodes above to easily compare the details from different nodes quickly without breaking the workflow.
The Map displayed in the details of an Alert is identical to the Map that appears elsewhere in LogicMonitor.