By collecting and analyzing tracked logs of the various middleware services in the network calls, you can obtain the call traces of a specific request across systems. This helps sort out application request entrances, service call initiators and dependencies, and helps you to analyze system call bottlenecks, estimate capacity, and quickly locate exceptions.
Log on to the EDAS console.
Click Applications in the left-side navigation pane.
Click the name of the application in the application list.
On the application page, select Application Monitoring > Service Monitoring from the left-side navigation pane.
The service monitoring page contains the following tabs:
- RPC Call Overview: Displays the call records of the RPC service provided by the current application.
- RPC Call Source: Displays the applications that call the RPC service provided by the current application.
- RPC Call Dependency: Displays the applications whose services are called by the current application.
(Optional) Set the monitoring conditions, and click Update to refresh monitor data.
Latest: Displays data at the current time by default. Select a period from the drop-down list.
Sort by: Sorts data by QPS by default. Select an option from the drop-down menu to sort data by the elapsed time or errors/s (average QPS errors per minute).
Results: 10 records are displayed by default. Select the number of results to be displayed from the drop-down menu. Options are 1, 5, 30, 50, 100, and unlimited.
Display: Results are displayed in blocks by default. You can also set the display mode to chart or table.
View monitor data.
For details about the metrics, see Application monitoring overview.
Click a metric of a column in the monitoring graph. The custom query page is displayed.
In the Metrics area, select metrics to view data of different groups.
When monitoring a service, you can monitor the service call trace between the application and other applications. You can also view detailed call traces.
In the monitoring graph, click View Trace next to a calling or called service to go to the Trace Query page.
On the trace query page, you can view the call trace between the application and the calling/called service.
For details about how to query traces, see Trace query.
On the service monitoring page, besides querying call traces related to an application, you can drill down to view monitor data about interdependent applications.
On the RPC Call Overview, RPC Call Source, or RPC Call Dependency tab, click Source Application, Called Service, or Calling Service next to Drill Down at the top of the monitoring graph. The monitoring page of the drilled down application is displayed.
Monitor data of the drilled down application.
The method for monitoring data of a drilled-down application is the same as that for monitoring the current application.