After a Microservices Engine (MSE) Nacos engine is created, you can view various runtime parameters and performance metrics on the Monitoring Center page to quickly identify potential issues and performance constraints. This helps you take effective optimization measures at the earliest opportunity, improves engine stability and reliability, and minimizes the risks of system interruptions and failures. This topic describes how to view the monitoring data of an MSE Nacos engine.
Prerequisites
A Nacos engine is created and the engine version is 2.0.4 or later.
Enable the Grafana dashboard
Basic Edition
If your engine uses Basic Edition, the Grafana dashboard is automatically enabled after you upgrade the engine to Professional Edition. For more information about how to upgrade the engine version, see Upgrade a Nacos version.
Professional Edition
If your engine uses Professional Edition and the engine version is 2.0.3 or earlier, you need to click Upgrade Monitoring Dashboard on the Observation Analysis page in the MSE console, and follow the instructions in the dialog box that appears to enable the Grafana dashboard.
Use the Grafana dashboard
If you enable the Grafana dashboard, you can view various performance metrics on the dashboard.
Log on to the MSE console, and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Instances.
On the Instances page, click the name of the instance.
In the left-side navigation pane, click Monitoring Center.
NoteThe default monitoring cycle is 15 minutes before the current time. You can click the time range drop-down list in the upper-right corner to select another time range or configure a custom time range as the monitoring cycle.
When you move the pointer over a specific position in a data chart, the metric data of nodes at the specified point in time is displayed. The time is accurate to minutes.
Click the
icon in the upper-right corner to refresh the current monitoring data.
On the Overview tab, you can view the following information:
In the Overview section, view Number of nodes, Number of configurations, Number of Service Providers, Queries per second, Operations per second, and Number of connections.
In the Usage level section, view Configuration number using water level, Service Provider Water Level, and Connection using water level.
NoteIf you use the Eureka client, the number of connections on the Overview tab cannot be reported to the Eureka client. This is because the Eureka client supports only short-lived connections.
Click the Registry Monitoring tab to view Number of Services, Number of Service Providers, Number of service subscribers, Registration Center TPS, Registration Center QPS, Registration Center Write RT, and Registration Center Read RT.
NoteBy default, Nacos 2.0.4 and later provide four services for address discovery of the Diamond protocol supported by Application Configuration Management. The number of services and number of service providers displayed on the Registry Monitoring tab are the actual numbers plus 4. This is a normal symptom.
If you use the Eureka client, the number of service subscribers cannot be reported to the Eureka client. This is because the Eureka client does not support service subscription and uses polling queries.
Click the Configuration center monitoring tab to view Number of configurations, Configure the number of listeners, Configuration Center TPS, Configuration Center QPS, Configuration Center Write RT, and Configuration Center Read RT.
Click the Push monitoring tab to view Service Push Success Rate, Time-consuming service push, Service Push TPS, and Service Empty Proportion.
NoteIf you use the Eureka client, it does not trigger the push feature of Nacos because the Eureka client uses polling queries. As a result, data of relevant metrics cannot be reported to the Eureka client.
Click the Number of connections monitoring tab to view Number of client versions and Number of Long Links.
NoteIf you use the Eureka client, the metric data displayed on the Number of connections monitoring tab cannot be reported to the Eureka client. This is because the Eureka client supports only short-lived connections.
Click the jvm Monitoring tab to view Young GC Time, Young GC Times, Full GC time, Full GC Times, and Heap Memory Usage.
Click the Resource Monitoring tab to view Inlet flow, Outlet flow, Memory Usage, CPU Usage, Number of nodes, and Load Indicator.
Click the Top N Monitoring tab to view the following information:
In the Service TopN Dashboard section, you can view Number of service providers TopN, Number of service subscribers TopN, and IP Push Failure Times TopN.
In the Configure TopN Dashboard section, you can view Number of Configuration Changes TopN and Configure the number of listeners TopN.
Optional. If you require more advanced observability capabilities, click Using Grafana Expert Edition in the upper-right corner to access the Grafana service console and use multi-tenant Grafana dashboard capabilities.
Optional. If you need to embed the engine monitoring page, click Open in New Window XX (XX represents the specific monitoring name) in the upper-right corner to obtain the URL of the new page.
For example, click the Registry Monitoring tab, and then click Open in New Window Registry Monitoring in the upper-right corner to open the Registry Monitoring tab in a new page.
Use the old dashboard
If you do not enable the Grafana dashboard, you can still use the old dashboard provided by MSE. To view data of more metrics, we recommend that you upgrade the monitoring dashboard to the Grafana dashboard. For more information, see Enable the Grafana dashboard.
Log on to the MSE console, and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Instances.
On the Instances page, click the name of the instance.
In the left-side navigation pane, click Observation Analysis.
On the Observation Analysis page, click the Monitoring tab to view the number of services, number of service providers, and average response time (RT) of the service write interface (ms).
NoteThe default monitoring cycle is 30 minutes before the current time. You can select another time range, such as Last 30 minutes, Last 1 hour, Last 6 hours, and Last 24 hours. You can also configure a custom time range.
The monitoring data of three nodes in the engine is displayed in different colors on the page. You can click the name of a node in the lower part of a chart to display or hide the data of the node. You must make sure that data of at least one node is displayed.
When you move the pointer over a specific position in a chart, metric data of three nodes at the specified point in time is displayed. The time is accurate to minutes.
Click the
icon in the upper-right corner to refresh the current monitoring data.