Services¶
Services serve as a centralized management entry point, providing a global perspective to aggregate and connect performance Metrics, call topologies, service lists, and full observability data (including traces, logs, infrastructure, etc.) in distributed systems. This enables integrated analysis capabilities from an overview of the overall state to in-depth diagnosis of individual services.
Performance Metrics¶
The Performance Metrics list provides a core dataset for measuring service health. It centrally displays the performance data of all services in the current workspace in a list format, including key Metrics such as request count, error rate, and response time.
This allows you to quickly assess the operational status of each service from a global perspective, and rapidly locate target services exhibiting anomalies (e.g., sudden spikes in error rates, increased response times) through filtering, searching, and Time Widget, providing a clear starting point for subsequent analysis.
Service Map¶
The Service Map visually presents the calling relationships and overall dependency structure between services in a topological graph format. It aggregates 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 crucial for understanding system architecture, assessing the impact scope of changes, and quickly locating the propagation chain of issues during failures.
Service List¶
The Service List is the configuration and attribute management center for all managed services. Here, you can manually add and edit services, and associate each service with its corresponding business attributes such as code repositories and technical documentation.
This step deeply binds technical entities (services) with the daily work context of development and operations (code, documentation), enabling direct association with specific code locations and existing solutions when service issues arise.
Service Details¶
Click on any service to enter its Service Details page, which presents a comprehensive analysis interface aggregating all observable data for that service. Through tabs at the top, the page seamlessly integrates different observational perspectives such as analysis dashboards, resource calls, infrastructure dependencies, traces, and logs.
Thus, in-depth analysis centered on a single service can be completed within the same interface without switching between different functional modules. For example, you can start from macro performance charts (analysis dashboard), then check the most time-consuming API endpoints (resource calls), trace their complete call chains (traces), and finally inspect the status of the host or container resources supporting the service operation (infrastructure dependencies).
