Try it free

Explore service topology with service map

  • Latest Dynatrace
  • How-to guide
  • 6-min read
  • Published Jul 14, 2026

The service map brings a single‑screen, interactive topology into Services Services. It automatically discovers runtime connections for your services—upstream and downstream services, database queries, and messaging flows—and overlays live health and performance data so that you can navigate from a high-level view to root cause analysis without switching context. The service map answers two immediate questions when a service behaves unexpectedly: who is calling this service, and what is this service calling?

This service topology is discovered automatically from Smartscape and metrics, so no manual configuration or maintenance is required. The service map is designed for SREs, developers, and platform engineers who need fast, contextual insight into service dependencies and health.

Service map in the Services app, overall viewService map filtered by the Java language and "kafka" in the search fieldService "Map" view for a particular service in the Services app
1 of 3Service map in the Services app, overall view

Key capabilities

The service map offers the following capabilities:

  • Interactive service topology that shows:
    • Horizontal call relationships: Upstream callers (what calls your service) and downstream dependencies (what your service calls), including transitive hops.
    • Database dependencies and messaging flows.
    • Frontend relationships to browser or mobile clients.
  • Zoomable, pannable map for exploring both small and large topologies.
  • Inline search and filters to find and scope services in large environments.
  • Performance and health indicators on each node.
  • Drill-downs from the map into individual analysis views.
  • Distinct node types and icons for services, databases, and queues to make data‑tier dependencies obvious.
  • List/Map toggle so that you can switch between a filtered services list and the topology map while preserving context.
  • Detailed dependency view in the details panel of a specific service.

Prerequisites

  • Access to Services Services in your Dynatrace environment.
  • Services instrumented with OneAgent or OpenTelemetry.

Access and navigate a service map

The service map is available on the Explorer tab in Services Services.

Access a service map

To open a service map for all services

  1. Go to Services Services > Explorer.
  2. Select Map in the view toggle located in the upper-right corner above the service list.

To open a service map for a specific service

  1. Go to Services Services > Explorer.
  2. Find and select the required service from the service list. The service details panel opens.
  3. Go to the Map tab on the service details panel.

Explore a service map

Once you open a service map, you can:

  • Zoom in and out to navigate and explore large topologies.
  • Hover over a node to check the node details.
  • Select a node to focus on the node details and perform additional actions, for example, analyze service performance or drill down to logs or traces.
  • Use the search field in the upper-left corner of the service map as well as the filter field and facets in Services Services to find services by name, ID, tag, namespace, or other common attributes.
  • Pay attention to the node colors, as different colors indicate root causes and nodes affected by a problem.
  • Check the numbers displayed on some nodes, which indicate the number of active health alerts.
  • Download a full or current map view as PNG.

Check node details

On the service map, hover over a node to see the node details. The following metadata is displayed:

  • Node type
  • Node name
  • Metrics for different node types:
    • Service: Failure rate, response time (p50), and throughput (RED metrics)
    • Database: Query count
    • Queue: Publish rate, receive rate, and process rate
    • Frontend: Error rate

    The available metrics depend on how the node was discovered. Smartscape-based nodes provide full performance insights, while metric-based nodes with no corresponding Smartscape entity show limited data.

  • Active health alerts
  • Additional details depending on the node type
Service node details in the service map
Service node details in the service map

Isolate a particular node

To focus the service map on a single node and its immediate dependencies, select the required node and then select Isolate this node. The map zooms in on that node and its dependencies, which is useful for narrowing focus in large or complex topologies.

Isolation view in the service map
Isolation view in the service map

Drill down to traces, logs, and more

The service map integrates with existing drill‑down workflows, so you can navigate from a service map node to Distributed Tracing Distributed Tracing or Logs Logs, while preserving the node context. For example, when you perform an action on a service node, the service is pre-selected in the filter field, while the timeframe remains unchanged.

On the service map, select a node to view node details and actions. The following actions are available:

  • Failure rate > Analyze failures: Open the Failures tab to identify what's causing request failures and compare failure trends over time.

  • Response time (p50) > Analyze response time: Open the Response Time tab to understand latency patterns and spot performance regressions.

  • Distributed Tracing View trace: Open Distributed Tracing Distributed Tracing to investigate individual requests end-to-end.

  • Logs View logs: Open Logs Logs to see log events emitted during service execution.

  • Domain apps: Open relevant apps for non-service nodes, such as Experience Vitals Experience Vitals for frontend nodes or Databases Databases for database entities.

    Opening Databases Databases is only available for database nodes backed by a Smartscape entity. Database nodes derived from metrics without a corresponding Smartscape entity don't support this action.

Drill-downs available for the service node in the service map
Drill-downs available for the service node in the service map

Limitations

The service map has the following known limitations:

  • In large environments, the density of a service map can be high. Use filters and facets to scope the view to relevant services.
  • Some cloud‑managed entity visualizations and advanced database and queue analysis are available in dedicated apps (for example, Databases Databases and Clouds Clouds). The service map provides navigation to those apps but not the full depth of specialized analysis.

Next steps

The service map is one of the features on the Explorer tab in Services Services. For deeper investigation, also explore Failure Analysis and Response Time Analysis on their dedicated tabs in the same app.

Related tags
Application ObservabilityServicesServices