Skip to content

Service Details

In the Service List, click on a single service to enter the associated view page, which mainly includes the following elements:

  • Summary: Displays trend charts of (error) Span count, (error) request count, log count, performance analysis, resource analysis, and anomaly analysis filtered by service, environment, and version.
  • Resource Invocation
  • Infrastructure Dependencies: Displays key metric data of associated hosts and Pods (such as CPU usage, memory usage, etc.).
  • Logs: Displays associated log data.
  • Traces: Displays associated trace data.
  • Error Tracking: Displays associated error counts.
  • Events: Displays associated generated events.

Resource Invocation

Displays resource invocation analysis associated with the service, filtered by environment, version, and K8s cluster dimensions. The left side shows the resource invocation ranking list under the selected conditions. Click on any resource entry, and the right side will dynamically display the detailed view of that resource.

On the left side of the page, the resource invocation ranking associated with the current service is displayed. Click on a single resource, and the right side shows:

  • Core metrics displayed as time series trend charts: invocation count, response time, error rate, response time distribution.
  • Complete trace details related to this resource.

  • Displays the upstream and downstream relationships of this resource in the invocation chain:

    • Colors of all nodes in the current topology are filled based on three dimensions: event status, P99 response time, and request error rate.
    • Hover over a node to directly view key metric data.

    • Click on any resource node in the topology to directly view its "upstream/downstream invocations," "related logs," "user access," and "related events," or create a new monitor based on this node.

      • Use the "View Upstream/Downstream" button to analyze the full path invocation relationship of the current resource layer by layer: the system dynamically displays adjacent layers of associated resources based on the current topology state (e.g., if upstream is already expanded, only downstream nodes are displayed). Unrelated resources are not included, ensuring that only the invocation paths directly related to the current node are always presented.

Feedback

Is this page helpful?