Skip to main content
Version: 3.7.0

Systems

Related Concepts

  • Services are fundamental resource types in ONE, automatically identified by agents based on specific rules. However, services can be numerous and complex for some users. Therefore, we provide System-related functionality to help users manage services from a system-level perspective.
  • A System is a logical concept within ONE, formed by aggregating services. In practice, users need to define systems according to their actual business environment.

Creating a System

  • New users will be guided to create a system upon first visiting the "Systems & Services/Systems" page, which opens the system creation dialog.
  • Existing users can click the 「Create」 button next to the view switcher to open the creation dialog, as shown below.

alt text

You need to define the system name, its parent system (if any), and associate services to complete the creation.

Clarification on Common Confusions:

tip
  • Parent System: Systems have a three-level hierarchy: System, Subsystem, and Service. A system can contain both subsystems and services directly. If you are creating a subsystem, select its parent system here. If the system is not a subsystem, select 'None'.
  • Associate Services: Here, select only the services directly contained by this system. Do not select services belonging to subsystems under this system.

Managing Systems

After creation, you can manage systems from either the Statistical or List view. Actions include: Edit, Delete, and Add Subsystem. (Systems currently support only 2 levels, so subsystems cannot have the "Add Subsystem" function)

  • Edit System: Select the system to edit from the card or list view, then click 「Edit」. You can modify the system name and its directly associated services. The parent system cannot be changed.
  • Delete System: Deleting a system will simultaneously remove all its configured content, including subsystems. As systems are user-defined resources, the impact is generally low. However, this action cannot be undone, so please proceed with caution.

Analyzing Systems

System Overview Views​

Statistical View​

Displays the health status of all systems using cards. If alerts are present, the system card is rendered red. The alert query scope includes all entities associated with the system (configurable via the vertical architecture hierarchy), with the highest severity alert shown in the top-left corner. The card also displays key metrics: Average Response Time, Request Error Rate, and Throughput.

alt text

List View​

Displays the health status of all systems in a list format. If alerts are present, an alert indicator appears next to the system name, colored according to the highest alert severity. The alert query scope is the same as in the Statistical View. The list also shows system tags, service count, and other relevant data.

alt text

Drill-Down Analysis​

Select a system for analysis. Click on the system card in the Statistical view or the system name in the List view to drill down into the System Details page.

Relationships​

Horizontal Call Relationships​

  1. Displays the upstream and downstream call relationships of the current system. You can directly see how many applications and systems call this system, and which systems, databases, and message queues it calls. To focus on a specific type of resource, click its card to view details or perform call analysis.

alt text

  1. Using the diagram above as an example, clicking the 'Database' card reveals information about the 8 databases called by this system.

alt text

  1. Clicking "Call Analysis" in the list allows you to analyze the interaction between the system and a specific database.

alt text

  1. Call Analysis supports drilling down by the services and interfaces within the system to analyze specific call behaviors.

alt text

System Statistics​

  1. Click the current system card in the call relationship graph to view its key statistical metrics.

alt text

  1. If system metrics appear abnormal, you can switch to view data for the contained services or subsystems to help identify the root cause resource.

alt text

Vertical Relationships​

Displays the hierarchical entity resources associated with the current system, e.g., services contained within the system, the containers hosting those services, and the hosts running those containers. Click on Host or Container cards in the system relationship graph to view their details. This section also provides statistics; you can switch statistical dimensions to view the quantity distribution of resources.

alt text

Vertical Architecture​

View the vertical architecture topology of the system for in-depth analysis of associated entities. This view also helps locate anomalous entities by correlating alert data. For more details, see Analyze Core Business Flow.

alt text

Logs​

View logs associated with the services within the current system.

alt text

Traces​

View traces associated with the services within the current system. For specific logic, refer to Traces.

alt text

Call Topology​

View the call topology of the current system to understand system performance, inter-system call performance, and backend call performance.

  • Colored by health score by default.
  • Uses a first-level call depth topology by default.
  • Supports drilling down into systems to view internal call topology.
  • Each node supports individual analysis, allowing you to view its key metrics and any other metric. Flexible correlation between metrics, traces, and events helps you quickly locate performance issues.

alt text

Alerts​

View alerts associated with the services within the current system.

alt text

Custom Views​

Supports adding custom views. For specific logic, refer to Analyze Core Business Flow.

alt text