Service¶
Service, as a centralized observability entry point, presents performance metrics, call topology, and full observability data (including traces, logs, and infrastructure) of distributed systems from a global perspective, providing integrated analysis capabilities from a global status overview to deep diagnosis of a single service. Service assets are uniformly managed in the Unified Catalog.
Performance Metrics¶
The performance metrics list provides a core dataset for measuring service health. It centrally displays, in a list format, the performance data of services within the currently selected Workspace, including key metrics such as request count, error rate, and response time. By default, the current workspace is queried. You can also select multiple workspaces on the same site within the authorized scope; services with the same name in different workspaces are displayed separately.
The list supports switching between the Service and Endpoint perspectives. Endpoints are aggregated by the combination of service and HTTP route, and support route-based search and service-based filtering. For statistics conditions, see Performance Metrics.
This allows you to quickly evaluate the running status of each service from a global perspective and, through functional components such as filtering, search, and the Time Widget, quickly locate target services that exhibit anomalies (such as a sudden spike in error rate or prolonged response time), providing a clear starting point for subsequent analysis.
Service Map¶
The Service Map presents the call relationships and overall dependency structure among services in the form of a topology graph. It aggregates the originally scattered trace information into an understandable "map", allowing you to intuitively see which upstream services a service depends on and which downstream services call it.
This global dependency view is critical for understanding the system architecture, assessing the impact scope of changes, and quickly locating the problem propagation chain when failures occur.
Service Assets¶
Service assets have been migrated to and managed in Unified Catalog > Service. You can view, add, or edit services in the Unified Catalog and maintain related business attributes.
Through the Unified Catalog, you can associate technical entities (services) with the daily work context of development and operations, making it convenient to quickly view related information from service assets.
Service Details¶
Click any service to enter its Service Details page, which presents a comprehensive analysis interface aggregating all observability data of that service. Through the tabs at the top, the page seamlessly integrates different observability perspectives, including the Analysis Dashboard, Resource Calls, Infrastructure Dependencies, Traces, and Logs.
As a result, in-depth analysis around a single service can be completed within the same interface without switching between different functional modules. For example, you can start from the macro-level performance charts (Analysis Dashboard), then view the most time-consuming API endpoints (Resource Calls), trace their complete call chains (Traces), and finally check the resource status of the hosts or containers supporting the service (Infrastructure Dependencies).
