All Products
Search
Document Center

Microservices Engine:Push tracking

Last Updated:Sep 07, 2023

Microservices Engine (MSE) Nacos instances provide the push tracking feature to track the Nacos service data or configuration data that is pushed from the server to the client. You can use the push tracking feature to query service pushes from a registry and to query configuration change releases and pushes from a configuration center. The push tracking feature helps you observe the execution of pushes from Nacos instances. This way, the troubleshooting efficiency of Nacos instances is improved. This topic describes the push tracking feature and how to query push tracks.

Prerequisites

  • A Nacos Professional Edition instance is created. For more information, see Create a Nacos engine.

  • The Nacos client in 2.0.0 or later is used.

Query push tracks of a registry

You can use the push tracking feature to query the details about service pushes from a registry.

Description

If you encounter issues that are related to service pushes from a registry when you use a Nacos instance, you can use the push tracking feature to help troubleshoot the issues. For example, if the client does not receive service pushes from the registry or an exception occurs on inter-service calls, you can use the push tracking feature to check whether the registry pushes service information to the client as expected.

Procedure

  1. Log on to the MSE console, and select a region in the top navigation bar.

  2. In the left-side navigation pane, choose Microservices Registry > Instances.

  3. On the Instances page, click the name of the instance.

  4. In the left-side navigation pane, choose Service Management > Push track.

  5. In the upper-left corner of the page that appears, select Query Dimension: Service or Query dimension: IP from the query dimension drop-down list. Then, enter the name of the service that you want to query in the Service Name field and enter the name of the group to which the service belongs in the Group Name field. Click Half an hour, 1 hour, or Nearly 1 day as the time range for the query. You can also specify a custom time range in Custom time. Then, click Query.

Note
  • If you select Query dimension: IP from the query dimension drop-down list, all the push information received by the client is queried.

  • If you select Query Dimension: Service from the query dimension drop-down list, the machines to which the service information is pushed and the push status are queried.

The following table describes the parameters.

Parameter

Description

Push Time

The time when the push event occurred.

Push Client IP Address

The IP address of the client to which information was pushed.

Push service name

The name of the service whose information was pushed.

Push Service Group

The name of the group to which the service belongs.

Number of Instances

The number of instance IP addresses that are included in the service push information.

Node name

The name of the Nacos node.

Query push tracks of a configuration center

You can use the push tracking feature to query the details about configuration changes of a configuration center.

Description

If you encounter issues that are related to configuration change releases of a configuration center when you use a Nacos instance, you can use the push tracking feature to query push information. For example, if a configuration release fails or configuration changes do not take effect on a machine, you can use the push tracking feature to query configuration changes and push events of the configuration center.

Procedure

  1. Log on to the MSE console, and select a region in the top navigation bar.

  2. In the left-side navigation pane, choose Microservices Registry > Instances.

  3. On the Instances page, click the name of the instance.

  4. In the left-side navigation pane, choose Configuration Management > Push track. Select Configuration from the query dimension drop-down list, enter the data ID of the configuration that you want to query in the Data ID field, enter the name of the group to which the configuration belongs in the Group field, and then click 搜索图标.

    Note
    • If you select Configuration from the query dimension drop-down list, the machines to which the configuration is pushed and the push status are queried.

    • If you select Query dimension: IP from the query dimension drop-down list, all configurations that are monitored by the machine with the specified IP address are queried.

    • Select Configuration.

      The following table describes the parameters.

      Parameter

      Description

      Change Event

      Displays the configuration change events that occurred in the specified period of time.

      Note

      When you click an event in the Change Event section, you are immediately redirected to the related information that is displayed in the Changes and Push Events section. Then, you can view the MD5 value in the change content of the change event.

      Changes and Push Events

      Displays the configuration changes and push events in the specified period of time. The MD5 value in the change content is displayed for configuration changes. The push time and the IP address of the client to which information is pushed are displayed for push events.

    • Select Query dimension: IP.

      The following table describes the parameters.

      Parameter

      Description

      Changed At

      The time when the configuration change occurred.

      Change Event

      The type of the configuration change event.

      DataId

      The data ID of the configuration.

      Group

      The group to which the configuration associated with this configuration change event belongs.

      Details

      • Click 信息 to view the details of the configuration change event.

      • Click 跳转, select the query dimension, and then query the push events of the configuration at the specified point in time.