Listen to Cloud server: domestic PHP, JSP,. NET performance monitoring Scenarios

Recently built a more private blog, because it is a foreign VPS, so want to test the visit time around.
Turn around and find this: Listen to the Cloud CDN.
Of course, not to listen to the Cloud CDN, but began to try to listen to the cloud server.

What does listening to the cloud do?

Listen to the Cloud app: monitor crashes, connection timeouts, memory leaks, and more during mobile app usage.

Listen to Cloud server: monitor the efficiency and performance bottlenecks of the server application.

Listen to Cloud CDN: Monitor CDN Accelerated content.

Listen to the cloud SYS: monitoring server, free users can monitor 5 units.

Resources

This time, the more formal reference materials are put forward:
PHP APM Comparison Evaluation: OneAPM, New Relic, listen to the cloud
Phper should be concerned about the service-side performance issues? Listen to Cloud server trial notes
Listen to the official cloud help document
Official demo

Configuration

According to the official configuration, there is nothing to say.

There are a few points to note:

1. Listen to the cloud server in the form of Daemon +php extension boot, instead of the original PHP link library, executable file replacement, so in stability can be more comfortable, that is, PHP-FPM case, After you've finished listening to the cloud plugin, just restart PHP-FPM.

The 2.license key is only used to differentiate between users, not to mark Server Application,server application is used under the Nbs.app_name option.

3. Listen to the cloud server configuration file is the PHP Networkbench.ini file in the configuration file directory, with a variety of configuration options: For example, a machine configuration of multiple server application, including the corresponding Chinese description.

4. Generally listen to cloud server new application for about 20 minutes to receive data, monitoring data and actual access to data about 5 minutes of time difference.

5. Other questions refer to the manual for creating an Application interface: Listen to the cloud PHP monitoring manual

There are two pits:
1. Installing the Listen Cloud Server package in Ubuntu Server 14.04 (nginx,php-fpm,mysql) in vmplayer , restarting php-fpm may cause mysqld to be shut down and need to start mysqld manually. not testing the Ubuntu system on the actual server
2. The default name of the first PHP application is called PHP application, if you delete PHP application, and then go to create a second application name, also known as PHP application, in this case, you can not receive the data of the second application. This is when asked to listen to the cloud customer service only then know: if PHP application is deleted, then the server is no longer going to receive data from PHP application.

Not to tell you this is why my app is called PHP application 2.

Application

It's not very easy to use words to show what the cloud is doing, but the illustrations are intuitive:
A Typecho Blog monitoring data:

As you can see, the routing distribution on the home page consumes most of the response time:

Additional monitoring data:

