When a service instance list changes or a configuration is released, Nacos pushes updates from the server to subscribing clients. If a client does not reflect the latest data, you need to determine whether the push was sent and whether it was received. Push tracking records every push event on your Microservices Engine (MSE) Nacos instance, so you can trace delivery end to end.
Push tracking operates in two independent modes, each accessed from a different area of the console:
| Mode | What it tracks | Console path (from instance details) |
|---|---|---|
| Registry push tracking | Service discovery pushes (instance list updates) | Service Management > Push track |
| Configuration push tracking | Configuration change releases and delivery | Configuration Management > Push track |
Prerequisites
Before you begin, make sure that you have:
A Nacos Professional Edition instance. For more information, see Create a Nacos engine
Nacos client version 2.0.0 or later
Query registry push tracks
Registry push tracking verifies whether service discovery updates reached subscribing clients. Use it when:
A client does not receive service updates from the registry.
An exception occurs on inter-service calls and you need to confirm whether the service list was pushed correctly.
Open the registry push tracking page
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, choose Service Management > Push track.
Query by service
Find which clients received a push for a specific service and whether the push succeeded.
Select Query Dimension: Service from the query dimension drop-down list.
Enter the service name in the Service Name field and the group name in the Group Name field.
Select a time range: Half an hour, 1 hour, or Nearly 1 day. To specify a different range, use Custom time.
Click Query.
The results show every push event for the specified service within the selected time range.
| Column | Description |
|---|---|
| Push Time | Timestamp of the push event. |
| Push Client IP Address | IP address of the client that received the push. |
| Push service name | Name of the pushed service. |
| Push Service Group | Group to which the service belongs. |
| Number of Instances | Number of instance IP addresses included in the push payload. |
| Node name | Name of the Nacos node. |
Query by IP
View all service pushes that a specific client received, regardless of service name. This helps build a full picture of what a particular client was notified about.
Select Query dimension: IP from the query dimension drop-down list.
Enter the client IP address, then select a time range and click Query.
The results list all push events received by the specified client IP. The result columns are the same as those described in Query by service.
Query configuration push tracks
Configuration push tracking traces configuration change releases and verifies whether changes reached subscribing clients. Use it when:
A configuration release fails.
Configuration changes do not take effect on a machine.
Open the configuration push tracking page
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, choose Configuration Management > Push track.
Query by configuration
View the full change and push history for a specific configuration item, including when each change occurred, the MD5 checksum of the content, and which clients received the push.
Select Configuration from the query dimension drop-down list.
Enter the data ID in the Data ID field and the group name in the Group field.
Click the search icon
.
The results are split into two sections:
| Section | What it shows |
|---|---|
| Change Event | Configuration change events within the selected time range. Click an event to jump to its details in the Changes and Push Events section, where you can view the MD5 checksum of the changed content. |
| Changes and Push Events | A timeline of configuration changes and push events. For changes, the MD5 checksum of the new content is displayed. For push events, the push time and client IP address are displayed. |
Query by IP
View all configurations monitored by a specific client and the change events associated with them.
Select Query dimension: IP from the query dimension drop-down list.
Enter the client IP address, then click the search icon
.
The results list all configuration change events associated with the specified client.
| Column | Description |
|---|---|
| Changed At | Timestamp of the configuration change. |
| Change Event | The type of the configuration change event. |
| DataId | Data ID of the affected configuration. |
| Group | Group to which the configuration belongs. |
| Details | Click  to view the full change details. Click  to switch query dimensions and trace push events for this configuration at the specified point in time. |