The Change Records page gives you a complete view of all change operations applied to your Elasticsearch cluster—what changed, when it happened, who made the change, and whether it completed successfully. Change operations include configuration changes, cluster restarts, and scaling in or out. Records are available for the previous 30 days.
View change records
-
Log on to the Alibaba Cloud Elasticsearch console.
-
In the left-side navigation pane, click Elasticsearch Clusters.
-
In the top navigation bar, select the resource group and region where your cluster resides. On the Elasticsearch Clusters page, find the cluster and click its ID.
-
In the left-side navigation pane, click Change Records. The page shows change records from the previous 24 hours by default. To adjust the time range, select Previous 7 Days, Previous 30 Days, or specify a custom range. Records older than 30 days are not available.

Change record fields
Each row in the change records table contains the following fields:
-
Change Start Time: The time when the change operation started.
-
Change Type: The type of change, such as cluster creation, cluster restart, or cluster configuration change.
-
Changed By: The ID of the Alibaba Cloud account or RAM user that performed the change.
-
Change Status:
-
In Progress: The change is being performed.
-
Complete: The change finished successfully.
-
Paused: The change is paused. If you did not pause it manually, click View Logs to see the cause.
-
-
Change End Time: Displayed only after the change operation is complete.
-
Actions:
-
Show Details: Opens the Change Details panel, which shows basic information, the type of change, and a before-and-after comparison of the cluster configuration. Parameters in this panel are displayed in the underlying parameter format. For information about modifying YML file parameters, see Configure the YML file.
-
View Logs: Opens the Logs page where you can view the operation log for the change. For more information, see Query logs.
-
What's next
-
If your cluster is abnormal and needs to be recovered at the earliest opportunity, restart the cluster and specify a high concurrency. See Restart a cluster or node.
-
To scale or reconfigure your cluster, see Upgrade the configuration of an Elasticsearch cluster.