When your application's response time spikes or error rates climb, you need to quickly identify which interface is responsible and what is causing the degradation. The Interface Invocation page in Application Real-Time Monitoring Service (ARMS) provides interface-level observability across your application, including call topology, performance metrics, slow query detection, exception and error aggregation, service dependency mapping, and trace-level drill-down.
Open the Interface Invocation page
Log on to the ARMS console.
In the left-side navigation pane, choose Application Monitoring > Applications.
On the Applications page, select a region in the top navigation bar, and then click the name of the application that you want to manage.
The icon in the Language column indicates how the application is connected. A
icon means the application is connected to Application Monitoring. A hyphen (-) means it is connected to Managed Service for OpenTelemetry.In the left-side navigation pane, click Interface Invocation.
Monitor interface performance on the Overview tab
The Overview tab displays the call topology of the selected interface along with time-series charts for four metrics:
| Metric | Description |
|---|---|
| Requests | Total number of requests over time |
| Errors | Number of failed requests over time |
| Response time | Average response time (RT) trend |
| HTTP status codes | Distribution of HTTP status codes over time |
A sudden spike in errors or response time on these charts is a starting point for deeper investigation with the analysis tabs below.
Identify slow SQL and NoSQL queries
SQL Analysis tab
The SQL Analysis tab lists all SQL queries executed within the selected interface's code path. Use this tab to locate slow SQL statements that cause high response times.
To view the full trace that contains a specific SQL statement, click Interface Snapshot in the Actions column.
NoSQL Analysis tab
The NoSql Analysis tab works the same way as the SQL Analysis tab, but targets NoSQL requests initiated within the selected interface. Click Interface Snapshot in the Actions column to view the complete trace for any NoSQL statement.
Analyze exceptions and errors
Exception Analysis tab
The Exception Analysis tab displays Java exceptions thrown from the selected interface's code, helping you identify the most frequent exceptions.
Click Interface Snapshot in the Actions column to view the full trace that includes the exception stack.
Error Analysis tab
The Error Analysis tab aggregates errors and HTTP status codes returned by the application. Use it to spot recurring error patterns across the interface.
Click a value in the TraceId column to open the trace details page for that specific request.
Trace upstream and downstream dependencies
Upstream Services and Downstream Services tabs
The Upstream Services and Downstream Services tabs show the services that call your application (upstream) and the services that your application calls (downstream). Each entry includes three performance metrics:
| Metric | Description |
|---|---|
| Response time | Average RT for calls between the two services |
| Requests | Total number of requests |
| Errors | Number of failed requests |
Use these tabs to determine whether a slow dependency is contributing to performance degradation. For example, if your application's response time is high, check the Downstream Services tab to identify whether a slow downstream service is the root cause.
Upstream Traces and Downstream Traces tabs
The Upstream Traces and Downstream Traces tabs provide a detailed view of interface-level call relationships:
Click Expand/Collapse All to show or hide all interfaces at once.
Search by application name or interface name in the search box.
Click the collapse panel or arrow icon at the end of a row to expand or collapse performance metrics for a specific interface.
Inspect traces on the Interface Snapshot tab
The Interface Snapshot tab provides trace-level visibility into the selected interface. It displays the parameters of the selected interface, two charts, and a trace details table.
Charts
Total Traces -- Shows the total number of interface calls and the number of slow calls. An interface call is classified as slow when its RT exceeds 500 milliseconds. This threshold is configurable in the application settings. Slow call counts exclude local interface calls generated in asynchronous scenarios.
Response time trend -- Shows how the interface RT changes over time. This chart is based on sampled data, so accuracy depends on the sampling rate configured for the application.
Trace details table
The table lists individual traces with metadata. From here:
Click a value in the TraceId column to open the trace details page, where you can inspect the full span breakdown of a request.
Click View Logs in the Actions column to view the business logs associated with a specific interface call.
To use View Logs, you must first associate trace IDs with your application's business logs. This association lets you jump directly from a problematic trace to the relevant log entries for troubleshooting. For setup instructions, see Associate trace IDs with business logs.
Supported frameworks
ARMS automatically detects and monitors interfaces in the following web and Remote Procedure Call (RPC) frameworks.
| Framework | Minimum version |
|---|---|
| Tomcat | 7+ |
| Jetty | 8+ |
| Resin | 3.0+ |
| Undertow | 1.3+ |
| WebLogic | 11.0+ |
| SpringBoot | 1.3.0+ |
| HSF | 2.0+ |
| Dubbo | 2.5+ |