Map

The map provides a visual view of the objects in your SquaredUp environment, their health states and the relationships between them. It includes SquaredUp objects, such as workspaces, dashboards and monitors, alongside objects imported from your data sources.

Use the map to easily understand dependencies, explore connected objects and identify where issues originate or what they may affect.

The connective power of the Map

Modern environments are sprawling, and the connections between the different objects you rely on are usually the hardest part to keep track of. The map gives you those connections in one place.

It's a live, interactive model of your environment, built automatically from everything SquaredUp knows: the workspaces, dashboards, and tiles you create, plus every object indexed from your connected data sources.

Because all of this is meshed into a single object graph, you can explore how everything fits together and watch health flow across those relationships in real time. That live picture is what makes the map genuinely useful day to day.

When something breaks, health states follow the relationships, so you can start from a struggling object and trace it back through everything it touches to find the cause. And because the map is always current, it's a great way to get your bearings in an unfamiliar part of your environment, or to notice problems quietly forming before they start to have an impact.

Accessing the map

You can access the map via three methods:

Select Map from the left-hand pane when in a workspace
From the Map tile of the workspace home
From the Map tile of an object drilldown

Opening the map from a workspace’s Map tab or overview displays the workspace and the dashboards it contains.

Opening the map from an object drilldown displays the selected object and its connected objects.

Each entry point opens the same connected map. You can start from a workspace and navigate to data source objects, or start from a data source object and navigate back to related SquaredUp content.

Map components

The map represents various objects as nodes, with connecting lines showing the relationships between them.

Nodes

Icon	Type	Description
	Workspace / Dashboard / Monitor	An openable container you can drill down into to view its dashboards, monitors, or contents
	Grouped objects	Several objects of the same type collapsed into one node to reduce clutter, select to expand and see them individually
	Object	A single item, such as a host, service, or resource

Halos

The ring around an object is called the halo, which represents the health state of an object and whether the node is currently pinned.

Health states

An object’s health state reflects the state of its monitors and rolls up to the root of the map. If a node enters a warning or error state, that state cascades towards the root, updating the color of each node and relationship along the path.

State	Color	Description
Error	Red	One or more critical checks are failing and need immediate attention
Warning	Amber	A non-critical issue has been detected and should be reviewed
Healthy	Green	Operating normally, all checks are passing
No health	Grey	No health data available or monitoring not yet configured

Pinned status

Icon	State	Description
	Pinned	A solid halo indicates that the node is pinned. Pinned nodes remain visible when connected nodes are collapsed.
	Unpinned	A dashed halo indicates that the node is unpinned. Unpinned nodes may be hidden when their connected nodes are collapsed.

Relationships

Lines between nodes represent relationships between objects. Each relationship has a direction and a label that describes how the objects are connected.

SquaredUp automatically creates relationships between its own objects, such as a workspace containing a dashboard. Relationships between data source objects are imported when those objects are indexed.

Relationship direction also determines how health states roll up through the map. A warning or error state cascades from a child node towards the root, updating the color of the nodes and relationships along that path.

Keywords

Relationship keywords describe how the source object is connected to the destination object. They help clarify the direction and purpose of each relationship shown on the map.

Relationship	Description
`contains`	The source object includes the destination object as part of its structure. For example, a workspace contains a dashboard.
`owns`	The source object is responsible for or has ownership of the destination object.
`hosted in`	The source object runs within or is deployed to the destination object. For example, an application is hosted in a virtual machine.
`hosted by`	The source object is provided, run, or managed by the destination object. For example, a website is hosted by a cloud platform.
`builds`	The source object creates, compiles or produces the destination object as part of a build or deployment process.
`uses`	The source object consumes or makes use of the destination object to perform its function.
`calls`	The source object sends a request to or invokes the destination object, such as an application calling an API or service.
`depends on`	The source object relies on the destination object to operate correctly. A failure or degradation in the destination object may affect the source object.
`monitors`	The source object observes the health, availability or performance of the destination object.

Interacting with the map

The map has two sets of controls: buttons that act on an individual object, and buttons that affect the whole map.

Object buttons

Hovering on an object reveals the object toolbar which has the following buttons.

Icon	Button	Description
	Expand / Collapse	Expands the object relationships to show the connected objects, or collapses the relationships to hide the connected objects. The number of connected objects is shown in parentheses.
	Hide	Click to remove nodes from the map. This will remove any relationship lines, but connected nodes will still display. The following options display, depending on the node context: Hide this object / Hide this group: Removes only the selected object or group from the map. Hide all <object type>: Removes all nodes of the same object type from the map.
	Ungroup	If a group of objects, ungroup a specific object or all objects.
	Drilldown	Navigates to the object drilldown page.

Map buttons

The view toolbar is located in the bottom-left of the map and provides options for the whole map.

Icon	Button	Description
	Fullscreen	Show the view full screen. This option is only available when the view is tiled.
	Zoom in / Zoom out	Adjusts the zoom level of the map. The zoom can also be controlled with the mouse scroll wheel.
	Vertical layout	The default layout of the Map. Shows a top-down view, using the direction of the relationships to position "source" objects at the top, and "destination" objects at the bottom. Select to choose from the other available layouts.
	Horizontal view	Shows a left-to-right view, using the direction of the relationships to position "source" objects to the left, and "destination" objects to the right. Best when relationships are wide rather than deep.
	Network view	Spreads nodes radially around a central object, with connections fanning out in all directions and related branches extending outward. Best for exploring everything linked to a focal point without imposing a top-down hierarchy.
	Collapse all	Collapse every expanded node and hide any unpinned connected nodes. Pinned nodes remain visible.
	Restore hidden types	Displays when you have hidden one or more object type from the map. Click then select the object types you want to restore.

Tips for using the map

The map rewards exploration, so don't be afraid to dig in. A few habits will help:

Start from what you care about, then branch out. However you open the map, it all connects into the same explorable space. Expand a node to reveal what it's linked to, then keep following the threads outward.
Pin the things that matter. Pinned objects always stay on the map. Pin your key objects, then use Collapse all for a clean view of just those.
Cut through the clutter. Group nodes tidy up similar objects, and you can hide anything that's just noise. Show the right things, not everything.
Pick the layout that fits. Use vertical or horizontal for a clean hierarchy, and network to see everything radiating from a single focal point.

Was this article helpful?

Have more questions or facing an issue?

Submit a ticket