Instance overview

更新时间:
复制 MD 格式

When an application instance shows degraded performance or unexpected errors, you need a single place to assess its health and trace the root cause. The Overview tab on the Instance Details page provides this diagnostic entry point, showing the application topology, request volume, response time, number of slow calls, error count, and HTTP status code distribution over time.

Open the instance overview

  1. Log on to the .

  2. In the left-side navigation pane, choose Application Management > Applications.

  3. In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace.

  4. From the Cluster Type drop-down list, select Kubernetes Cluster.

  5. Find the target application and click its name in the Application Name column.

  6. In the left-side navigation pane of the application details page, choose Monitor > Instance Details.

  7. In the left-side pane of the Instance Details page, select an instance, then click the Overview tab on the right side of the page.

Application topology

The application topology maps the call relationships between internal services of the application over a specified time period. Use it to identify which upstream or downstream service is causing latency or errors in a request path.

To navigate the topology:

  • Click the plus icon or scroll the mouse wheel up to zoom in.

  • Click the minus icon or scroll the mouse wheel down to zoom out.

  • Click the Refresh icon to reset the topology to its default size.

The application topology is available only in Professional Edition and Platinum Edition. Standard Edition does not support this feature.

Monitoring charts

The Overview tab includes four time series charts that track application health: Requests, Response Time, Errors, and HTTP - Status Code. The tab also displays the number of slow calls. Together, these charts support a diagnostic workflow: start with Requests to confirm traffic patterns, check Response Time for latency degradation, review Errors for failure spikes, and examine HTTP - Status Code for the distribution of 4xx and 5xx responses.

Requests

Displays the number of requests over time. Use this chart to establish a traffic baseline and identify unusual drops or surges in request volume.

Response time

Displays the response time (RT) of the application over time. A gradual increase may indicate resource contention, while a sudden spike often points to a downstream dependency issue. Click a spike in the curve to drill down into the specific time window for deeper analysis.

Errors

Displays the number of errors over time. A sustained increase in errors, especially when correlated with response time spikes, typically signals a service-level issue that requires investigation. Click a spike in the curve to drill down into error details for that time window.

HTTP status codes

Displays HTTP status code distribution over time. Click the legend to show or hide individual status code series. A rise in 5xx codes indicates server-side failures, while increased 4xx codes suggest client-side request issues such as authentication failures or invalid parameters.

Interact with charts

All four monitoring charts share the following interactions:

Action Result
Hover over a data point View detailed statistics at that timestamp
Click and drag to select a time range Zoom into the selected period
Click the chart icon Compare metrics across different dates or view data for a specific historical period