All Products
Search
Document Center

Enterprise Distributed Application Service:External call monitoring

Last Updated:Mar 11, 2026

You can use external call monitoring to locate slow calls or errors during the external calls of an application. By surfacing latency, error rates, and HTTP status code trends for every outbound dependency, you can pinpoint which external call is responsible and trace the problem back to the internal API that triggered it.

Typical troubleshooting workflow:

  1. An alert fires for increased response time on your application.

  2. Open external call monitoring and sort by response time to find the slowest external dependency.

  3. On the Overview tab, check request count, error count, and HTTP status code trends.

  4. Switch to the Call source tab to identify which internal APIs triggered the problematic external call.

Access external call monitoring

  1. Log on to the EDAS console.

  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 > External Calls.

The left-side pane lists all external calls for the application. Sort by response time, request count, error count, or exception count to prioritize investigation.

View call overview

Click an external call in the left-side pane to open the Overview tab. This tab displays time-series charts for the following metrics:

MetricDescription
Request countTotal number of requests over time
Response timeLatency trends for the selected external call
Error countFailed requests over time
HTTP status codesBreakdown of response status codes
External call overview

Trace call sources

Click an external call in the left-side pane, then select the Call source tab. The charts display request count, response time, and error count broken down by the internal APIs that triggered the external call.

Call sources

Filter and navigate call sources

ActionHow to
Expand or collapse all APIsClick Collapse/Expand All at the top of the tab.
Search for a specific APIEnter an application name or API (span) name in the search box and click the Search icon.
Expand or collapse a single APIClick the collapse panel for the API, or click the up or down arrow at the end of the row, to toggle its performance metrics.

Edition requirements

Enterprise Distributed Application Service (EDAS) provides external call monitoring in Professional Edition and Platinum Edition only. Standard Edition does not support this feature.