If a Trace Query is performed and the query fails to find the invocation trace, the following information is displayed:
- The current application is abnormal or is not in a normal running state.
- The log collector has not been installed or is operating abnormally.
- Port 8182 opened with an error.
- No traffic for the access request.
Click Application management in the left navigation bar of the EDAS console. On the application list page, search for and select the name of the application that does not have an invocation trace or monitoring data.
Click the Deploy information tab on the application details page and check whether the running status of the application instance is Running normally.
- If yes, proceed to the next step.
- If no, troubleshoot the problems with the application instance and proceed to the next step.
Log on to the ECS instance using the root account for application deployment.
Run netstat -antp|grep 8000 in the ESC instance and check whether the connection is normal.
- If yes, the log collector has been installed and its running status is normal.
- If no, the log collector has not been installed. Please Install the log collector.
Log on to the ECS instance using the root account for application deployment, and run netstat -antp|grep 8182 to check the status of port 8182.
- If the connection is normal, port 8182 is open.
- If no connection exists or an error is displayed, see Security group rules to check whether port 8182 is restricted. Open port 8182.
Please check whether traffic for the access request exists based on the actual business of your application. You can also select Log directory on the EDAS console to check whether traffic for the access request exists during the query period.
When you have completed the preceding steps, check on the trace query, basic monitoring, and service monitoring pages whether the invocation trace information and monitoring data are normal.