Service map in traces
The service map helps you understand how services interact within a distributed system. It shows which services handle requests, how calls move between them, and how application components work together.
The service map enables you to:
- Understand the request path between services.
- Locate adjacent services that affect the selected component.
- Decide whether to continue the analysis in logs, traces, or connected services.
- Evaluate service load, latency, and percentage of errors.
Here are the possible use cases of a service map:
- Finding the error source to identify which service causes the failure.
- Analyzing latency to identify the service that slows down the call chain.
- Studying the architecture to quickly understand relationships between services.
Service map description
The map shows each service as a node and each service call as a connection between nodes. A service node displays the number of requests per second, response time for the selected percentile, and the percentage of requests with errors. A solid outline means the service has been loaded on the map. A dashed outline means the service was found through connections, but its surrounding context has not yet been loaded.
Working with a service map
-
On the Monium home page, select Services map on the left.
-
At the top, set the data search period on the timeline.
-
Enter the following query in the search bar:
-
project = <project_ID>: Select the project specified inx-monium-projectof the application's telemetry transmission configuration.This may be a cloud (
cloud__<cloud_ID>) or folder (folder__<folder_ID>) project, or another project. -
cluster = <cluster_name>: Select the name of the installation that runs your application. If no cluster is specified,cluster = defaultis used. -
service = <service_name>: Name of your application or service. You can use theOTEL_SERVICE_NAMEenvironment variable to provide it.If you do not see the required labels in the suggestions, you can enter them manually. However, the system most likely has not received data with these labels. See Data delivery troubleshooting for possible solutions.
-
-
Click Execute query.
This will open a service map with the found service and its immediate connections.
-
To explore a service, click its node. This will open a card with metrics and actions:
- Navigate to logs: Open service logs.
- Navigate to traces: Open service traces.
- Explore: Set this service as the focus of the analysis.
- Load connections: Load neighboring services for the selected node.
-
To focus the map on the selected service, click Explore.
This way, you can move step by step from an external service to an internal one and locate where latency or errors start to rise.
-
To display additional service connections, both incoming and outgoing, click Load connections.
Using a service map for analysis
-
Find the service you need using a query.
Start your analysis from the first service that triggered an alert or showed increased latency or percentage of errors.
-
Check its metrics on the map.
-
Load its connections or select Explore.
-
Navigate to logs or traces for detailed analysis.
When working with the map, factor in the following:
- The map is built from tracing data. If your service does not send traces, it will not appear on the map.
- The map content depends on the selected time range and query.
- If you see a dashed node on the map, load its connections to expand the graph.
- For a detailed analysis of a specific request, navigate from the map to searching for traces and spans or viewing and analyzing traces.