Listener cloud Server: domestic PHP, JSP,. NET performance monitoring program

Listener cloud Server: domestic PHP, JSP,. NET performance monitoring program

Recently, I set up a private blog, because it is a foreign VPS, so I want to test the access time in various regions.
I found this: Listen to Cloud CDN.
Of course, I went to the business again, instead of listening to Cloud CDN, I started to try it out.

What does Tingyun do?

Listener cloud app: monitors problems such as crashes, connection timeout, and memory leakage during use of mobile apps.

Listen to cloud server: monitors server application efficiency and performance bottlenecks.

Listener Cloud CDN: monitors CDN accelerated content.

Listen to cloud sys: monitoring servers. you can monitor 5 servers for free.

References

This time, we put more formal references at the beginning:
Comparison and evaluation of php apm: OneAPM, New Relic, listener cloud
What are the server performance issues that PHPer should be concerned about? Listen to cloud Server trial notes
Listen to the official help document of cloud
Official demo

Configuration

Follow the official configuration.

Pay attention to the following points:

1. listening to cloud Server is started in the form of a daemon + php extension, rather than replacing the original php link library and executable files. Therefore, you can be assured of stability, that is, in the case of php-fpm, you only need to restart php-fpm after installing the Cloud plug-in.

2. the license key is only used to differentiate users, rather than to mark the server application. the server application uses the nbs. app_name option in the following to differentiate.

3. the configuration file of the listener cloud server is networklinks under the php configuration file directory. the INI file has various configuration options: for example, a machine is configured with multiple server applications, which have corresponding Chinese descriptions.

4. generally, applications created by the cloud server can receive data in about 20 minutes. The time difference between monitoring data and actual data access is about 5 minutes.

5. for other issues, refer to the manual for creating an application interface: Listen to the cloud php monitoring manual.

There are two pitfalls:
1.VMPLAYERInstall the listening cloud server package in ubuntu server 14.04 (nginx, php-fpm, mysql). restarting php-fpm may cause mysqld to be disabled. you need to manually start mysqld.The ubuntu system on the actual server is not tested.
2. the default name of the first PHP Application is PHP Application. if you delete the PHP Application and create the second Application name, also called PHP Application, in this case, the data of the second application is not received. This is only known after asking about the cloud customer service: if the PHP Application is deleted, the server will no longer receive data from the PHP Application.

I will not tell you that this is why my Application name is PHP Application 2.

Application

It is not easy to use text to show what the cloud has done, but the illustration is very intuitive:
Monitoring data of a typecho blog:

As you can see, the route distribution on the home page takes most of the response time:

Other monitoring data: