Skip to content

Service Map

On the "Service Map" page, you can visually view the invocation relationships between services through a topology diagram.

Space Scope

Entering the Service Map page, the system defaults to displaying only the service nodes and invocation relationships within the current workspace. When cross-space authorization is not configured, service nodes, invocation edges, and metric data from other workspaces are invisible.

If the current workspace has been authorized to access data from other spaces, you can switch the viewing dimension through the space scope selector at the top of the page:

  • Current Space: Displays only the service topology of the current workspace (default option).
  • All Spaces: Displays the service topology of the current space and all accessible spaces.
  • Authorized Spaces: Multi-select specific authorized workspaces to view the service topology of the corresponding spaces.

The search, filtering, service count statistics, node colors, and topology metrics on the page are all calculated in real-time based on the currently selected space scope. If the current workspace has no cross-space authorization, the page will not display other space options.

Attention

The current service topology data has a default delay of 5 minutes. It supports adjustment via the max_delay parameter within a range of 1 to 5 minutes (minute granularity) (❗️Only available for Deployment Plan users). You can flexibly set it based on your business real-time requirements.

  • For SaaS Commercial Plan, the data visibility scope is configured through cross-space authorization. Only workspace owners, administrators, or roles with cross-space authorization management permissions can configure it. After authorization takes effect, the authorized workspace can view the corresponding data in ServiceMap. Once authorization is revoked, the corresponding workspace will immediately lose access to view the source space's ServiceMap data.

  • For Deployment Plan, the data visibility scope is configured based on the site dimension.

Single Service

Hovering over a single service node will highlight the corresponding service, while other unrelated services and connection lines turn gray. You can view key metrics for this service, including request count, error rate, average response time, P99/P95 response time, and maximum response time.

View Service Details

On the default page, in addition to visually displaying the invocation relationships between services within the currently selected space scope, clicking any service node will slide out the details of that service. It mainly includes the following elements:

  1. Service name, and its corresponding team, contact information, alert count, etc..
  2. Basic metrics of the current service: request count, error rate, average response time, P99/P95 response time, and maximum response time.
  3. Click to view the upstream and downstream of the current service, service overview, and associated logs and traces.
  4. Anomaly trend charts for metrics (service request response time, error request distribution) and logs (error log count).

Manage Topology

  • Zoom in, zoom out, or fully display the current service topology.

  • Supports selecting different performance metrics to match service node colors, including request count, P50/P75/P95/P99 response time, maximum response time, and error rate.

  • Custom Colors: Set the color range intervals for service nodes based on the selected "fill metric".

  • Custom Intervals: Customize the color range intervals for service nodes for the selected fill metric. The system will automatically divide the values into 5 intervals based on the maximum and minimum values of the selected metric in the topology, each interval corresponding to a color.

    • Node Size: There are 3 node sizes. The maximum (Max) and minimum (Min) of service requests per second are divided into three equal parts, resulting in three intervals corresponding to 3 graphic sizes.
Attention

When the requests per second is less than 0.01, the displayed value will be uniformly marked as < 0.01. However, note that the node size calculation is still based on the actual value.

  • Topology Configuration:

    • Differentiate Environment and Version: Draw the trace topology based on two dimensions: service (service) and service environment version (service+env+version). After enabling, the system will draw the service topology according to different environment versions.
    • Whether to calculate node size based on "request count".
    • Select the hover highlight range: Directly related nodes (upstream/downstream) / Full-chain related nodes (multi-level upstream/downstream).
    • Only display services matching filter criteria: After enabling, the service topology will filter service nodes based on the current filter criteria, retaining only the service nodes that meet the conditions themselves, and hiding nodes that do not meet the conditions.

Cross-Space Query

Prerequisites

All Commercial Plan workspaces belong to the same organization ID, i.e., the same organization.

If the same Trace data is split and distributed to different workspaces, the complete trace data cannot be viewed in the same workspace. However, cross-workspace Service Map queries can ensure data query continuity. By clicking the button directly in the current workspace, you can view the upstream and downstream invocation topology of the current service.

Data Source Definition and DQL Query

For more details, refer to Service Map Data Source Definition.