Services¶
As a centralized observability entry point, Services presents performance metrics, call topology, and full observability data (including traces, logs, infrastructure, etc.) in distributed systems from a global perspective, providing integrated analysis capabilities that range from global status overview to deep diagnostics of individual services. Service assets are managed centrally in the Unified Catalog.
Performance Metrics¶
The performance metrics list provides the core data set for measuring service health. It displays performance data for services in the currently selected workspace in a list, including key metrics such as request count, error rate, and response time. By default, the current workspace is queried, but you can also select multiple workspaces on the same site within your authorized scope (see select multiple workspaces on the same site within your authorized scope). Services with the same name in different workspaces are listed separately.
This allows you to quickly assess the operational status of each service at the global level and use functional components such as filters, search, and the Time Widget to locate target services showing anomalies (for example, error rate spikes or prolonged response time), providing a clear starting point for subsequent analysis.
Service Map¶
The Service Map clearly shows the call relationships and overall dependency structure among services in a topology view. It aggregates previously 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 essential for understanding system architecture, assessing the impact scope of changes, and quickly locating failure propagation chains when failures occur.
Service Assets¶
Service assets have been migrated to Unified Catalog > Services for management. 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 teams, making it easy to quickly view relevant information from service assets.
Service Details¶
Click any service to access its Service Details page, which presents an integrated analysis interface aggregating all observability data for the service. The tabs at the top of the page seamlessly integrate different observability perspectives, including analysis dashboards, resource calls, infrastructure dependencies, traces, and logs.
As a result, deep analysis of a single service can be completed in the same interface without switching between different Features. For example, you can start from high-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 status of host or container resources supporting the service (infrastructure dependencies).
