Organization Maps for Full-Stack Observability

See every application, service, host, and network device, and how they depend on each other, on one live map.

Spot the failing device behind a red application
Trace top-down or bottom-up, whichever way the alert starts.
Give network, server, and application teams one shared map.

Full-stack dependency mapping with Organization maps

When an application slows down or loses connectivity, you shouldn’t have to piece the answer together from separate tools. OpManager automatically lays out your applications, services, hosts, and network devices in connected layers. When something turns red, you see which applications are affected and which device underneath is the likely cause. Start at either end, and the map leads the way.

Trace faults to the root cause across every layer

Use organization maps to trace faults across your full-stack topology

Your application slows down: is it a service, the server, or a switch three hops away? OpManager's application dependency mapping shows the chain on one map, so you switch tools less and fix the problem sooner.

Get your full-stack topology in one view, showing how every device, server, service, and application connects.
Trace top-down: Start with a slow application and follow its upstream dependencies to pinpoint the underlying service or server issue.
Trace bottom-up: Pick a faulty switch and expand its downstream dependencies to see which servers, services, and applications rely on it.

One dependency map, layered view for every team

During an incident, the server team and the network team rarely need the same view. OpManager gives each layer its own map, so every team works on what it owns while the full hierarchy stays one click away.

Use the built-in filters to switch between network, host, service, and application maps, and focus on just the layer you’re investigating.
See hosts, VMs, and datastores alongside your physical devices, so a problem on a virtual server doesn’t go unnoticed.

Understand network device relationships with Layer 2 topology maps

A bottom-up trace is only as good as the network map under it. OpManager builds a Layer 2 foundation from your seed routers, so a failed link points to the right hosts and applications.

See which device sits on which switch port, with MAC address and port details, using the Switch Port Mapper add-on on your monitored switches.
Define uplink dependencies once, and OpManager draws the dependency chains for you, so an outage’s impact is visible without manual tracing.
Move across hundreds of devices and spot the branch a problem sits on.

View key metrics without leaving the map

An alert tells you something’s wrong, not how bad it is or where to look. OpManager puts each node’s status and key metrics one hover away, so you can size up an incident before opening anything else.

Health colors on every application show which ones need attention first.
See the key performance metrics for any node, from device availability to database and server health, without opening another page.
Open the device snapshot page only to trigger automated L1 troubleshooting workflows or take any remedial action, right from there.

Four layers, one chain of dependencies

Every monitored entity sits in its own layer, with a count of how many need attention, so you can read your organization’s health from top to bottom.

Layer	What it contains	Availability
Application	Business applications and APM-monitored web apps, the services your users actually experience.	Applications Manager plugin
Service	Databases, web servers, and runtimes such as Tomcat, PostgreSQL, MySQL, Oracle, and Java, grouped by type.	Applications Manager plugin
Host	The physical and virtual servers those services run on, each linked to the services it hosts.	Default in OpManager
Network	Switches, routers, firewalls, and other devices that connect the hosts, the foundation everything else depends on.	Default in OpManager

Go beyond mapping: Connect it to how your team works

Enterprise-wide visibility

With OpManager Enterprise Edition, merge organization maps from remote sites (probes) into one central map for a single view of your distributed infrastructure.

Severity-based alerts

Devices showing severity-based color codes for Attention, Trouble, and Critical states in the organization maps help you filter critical devices, and prioritize them.

Device-level insights

View live device status and metrics like availability, packet loss, response time, CPU, and memory. Open the snapshot page from the map to investigate and remediate.

ServiceDesk Plus Integration

Sync devices, IP addresses, categories, and relationships to ServiceDesk Plus (On-premise and Cloud) to isolate faults from your ITSM platform.

Why teams choose OpManager

To trace faults across the full stack, faster

Two-way tracing

Start from the application or the network. The same map takes you to the root cause either way.

Faster RCA

Spot faults, trace dependencies across layers, and start remediation from the device snapshot.

Automated topology map

The map is built from discovered data and refreshes every six hours. You can also rebuild it manually.

FAQs about Organization maps

An organization map is a visual, layer-by-layer representation of your IT environment. In OpManager, it maps dependencies across applications, services, infrastructure, and network devices in a tree view, so you can trace issues across layers.

A Layer 2 map shows how network devices are directly connected at the data link layer. An organization map goes further. It uses Layer 2 topology as its network foundation and adds infrastructure, services, and applications above it.

Upstream dependencies are the components an entity relies on, such as the services, servers, and switches behind an application. Downstream dependencies are the components that rely on it, such as the applications affected when a switch fails. In OpManager, you can expand either direction from any node on the map. (51 words)

The application and services layers. The network and infrastructure layer maps are available by default in OpManager.

The map is first built an hour after OpManager’s initial installation, and it refreshes every six hours after that. You can also refresh it manually.

With OpManager Enterprise Edition, each remote site’s Layer 2 map is merged into one central organization map on the central server, giving you a full view of all locations.

Hover over a device to see the metrics it monitors, such as availability, packet loss, response time, and CPU and memory usage. Click the device to open its snapshot page, where you can see device-specific details and take remedial action, including automating workflows to start L1 troubleshooting.

Devices are color-coded by severity (Attention, Trouble, Critical), so you can prioritize the most serious alarms first. The thresholds are set in Severity Settings.Answer goes here.

Yes. OpManager syncs devices and their relationships to ServiceDesk Plus On-premise and Cloud, so teams can isolate faults through relationship mapping in the ITSM platform.

An application dependency map shows the services, servers, and network devices an application relies on. In OpManager’s organization map, these dependencies are shown across layers, so you can see what an application depends on and what depends on a given device.