> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Service maps

> Visualize service dependencies and request flow with ClickHouse Observability service maps.

[Beta feature](https://clickhouse.com/docs/reference/settings/beta-and-experimental-features.md#beta-features)

Service maps visualize how your services interact. ClickHouse Observability builds the graph by matching client spans (outgoing requests) with server spans (incoming requests) within the same trace, reconstructing the request path between services.

Click **Service Map** in the left navigation panel to open the full graph. Services appear once you're [ingesting trace data](https://clickhouse.com/docs/clickstack/observability/ingesting-data/overview.md) with OpenTelemetry.

![Service map showing service nodes and request flow between them](https://mintcdn.com/private-7c7dfe99/FqnhjwVWZILRZzw7/images/clickstack/observability-service-map-overview.png?fit=max\&auto=format\&n=FqnhjwVWZILRZzw7\&q=85\&s=7acf46a747e629ce7c0609c879ba0bd9)

## Exploring the service map

Each node represents a service, identified by the `service.name` resource attribute. Edges (dashed lines) connect services where a client span in one matches a server span in another. Node size reflects relative traffic volume. In **Error rate** mode, red nodes indicate services with errors in the selected time range. Use the legend in the top-right corner to switch between **Latency**, **Error rate**, and **Throughput**.

The toolbar above the map lets you filter and adjust the view.

**Source selector** — choose the trace source used to build the map, such as **Traces**.

**Sampling slider** — adjust the sampling rate to balance performance and accuracy. Lower rates load faster on high-volume clusters.

**Date range picker** — set the time window for the trace data used to build the map.

Use the **+/-** buttons in the bottom-left corner of the map or scroll to zoom in and out.

## Trace-level service maps

When you inspect an individual trace, select the **Service Map** tab to see how that specific request moved between services. Switch back to the **Trace** tab to return to the waterfall.

![Switching from the trace waterfall to the service map for an individual trace](https://mintcdn.com/private-7c7dfe99/FqnhjwVWZILRZzw7/images/clickstack/observability-trace-service-map.gif?s=5b989434a386e0f1712d207bef863a74)