For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Understanding the service map
  • Accessing the service map
  • Using the service map
Observability

Service map

Was this page helpful?
Previous

Vega for auto-remediation

Next
Built with

Overview

This topic explains how to use the service map in LaunchDarkly Observability.

The service map is an interactive visualization that shows the dependency relationships between your services. It derives this topology from your distributed traces. Parent-child span relationships are analyzed to determine which services call each other. Services appear as nodes in the graph, and directional edges represent call relationships between services. When two services call each other, the edge between them is bidirectional.

Understanding the service map

The service map is powered by distributed tracing data. To populate the map, your services must be instrumented to capture and send traces to LaunchDarkly. To learn more about setting up tracing instrumentation, read Traces.

The service map respects the time range selector on the dashboard. If you adjust the time range, the map updates to reflect service interactions within the new window.

No data displayed

If the service map appears empty, confirm that tracing instrumentation is configured for your services and that the selected time range includes trace data. Try expanding the time range if you expect data to be present.

Accessing the service map

To access the service map:

  1. In the LaunchDarkly UI, navigate to Observability > Dashboards.
  2. Select Service Map from the list of dashboards.

The service map visualization appears, showing your instrumented services and their dependencies.

Using the service map

The service map supports two viewing modes:

  • Overview mode: Displays the full dependency graph for all instrumented services in the selected time range. Use this to get a high-level picture of how your services are connected.
  • Focused mode: Zooms into a single service to highlight its direct connections and associated metrics. Use this to investigate a specific service’s dependencies.

You can switch between these modes using the interactive controls in the visualization. The specific interactions for toggling between modes may change as the feature evolves.