Tag
|
Adding tags to clusters can help you identify and manage your cluster resources. You can customize tags or use tags predefined by Tag Management Service (TMS). For details, see Managing Tags.
diff --git a/docs/css/umn/css_01_0012.html b/docs/css/umn/css_01_0012.html
index 5207fdb9..17b3ee3d 100644
--- a/docs/css/umn/css_01_0012.html
+++ b/docs/css/umn/css_01_0012.html
@@ -20,7 +20,7 @@
 In the preceding command, the private network address and port number of only one node in the cluster are used. If the node fails, the command will fail to be executed. If the cluster contains multiple nodes, you can replace the private network address and port number of the faulty node with those of any available node in the cluster. If the cluster contains only one node, restore the node and execute the command again.
If encryption has not been enabled for the communication with the cluster, the command output is similar to that shown in the following figure.
-Figure 1 Command output
+Figure 1 Command output
Accessing a Cluster Using Java API in Non-security ModeFor clusters in the non-security mode, you are advised to use use RestHighLevelClient.
diff --git a/docs/css/umn/css_01_0024.html b/docs/css/umn/css_01_0024.html
index c5f5087b..18ef0de2 100644
--- a/docs/css/umn/css_01_0024.html
+++ b/docs/css/umn/css_01_0024.html
@@ -49,7 +49,7 @@
{"index":{}}
{"productName":"Latest art shirts for women in 2017 autumn","size":"L"}
The command output is similar to that shown in Figure 1. If the value of the errors field in the result is false, the data is successfully imported.
- Figure 1 Response message
+ Figure 1 Response message
Modifying Specifications
-You can scale-in/out your cluster nodes to improve resource utilization and reduce O&M costs.
- Scaling out Clusters- Log in to the CSS management console.
- Choose Clusters. Locate the row containing the target cluster and click Modify in the Operation column.
- On the displayed Modify Configuration page, specify New Nodes and Node Storage Capacity.
If none of the master nodes, client nodes, and cold data nodes are enabled in your cluster, you can modify the number of nodes or the node storage capacity. You can add 1 to 32 nodes.
-If your cluster has a master node, client node, or cold data node enabled, you can modify the number of master nodes, client nodes, cold data nodes, or the node storage capacity. You can add 1 to 200 nodes, including a maximum of nine master nodes and 32 client nodes.
- - If you only expand the node quantity, the Node Specifications and Node Storage Capacity settings of newly added nodes will be the same as the settings you specified during cluster creation.
- If none of the master nodes, client nodes, and cold data nodes are enabled in your cluster, and you increase both the node quantity and the storage capacity, the Node Specifications settings of newly added nodes will be the same as the settings you specified during cluster creation, whereas the Node Storage Capacity settings of all nodes will be changed to the new storage capacity.
- If master nodes, client nodes, or cold data nodes are enabled in your cluster, you can increase the quantity and storage capacity of a certain type of nodes, for example, master nodes.
- If none of the master nodes, client nodes, and cold data nodes are enabled in your cluster, and you only change the Node Storage Capacity, the storage capacity of all the nodes in the cluster will be changed.
- If master nodes, client nodes, or cold data nodes are enabled in your cluster, you can increase the storage capacity of a certain type of nodes, for example, master nodes.
- You can expand the storage capacity six times at most.
- Services will not be interrupted during the cluster scale-out process.
-
-Figure 1 Modifying specifications
- - Click Next.
- On the displayed Details page, confirm the specifications and click Submit.
- Click Back to Cluster List to switch to the Clusters page. If Scaling out is displayed in the Task Status column, the cluster specifications are being modified. If Available is displayed in the Cluster Status column, the modification is successful.
-
- Scaling in Clusters- Log in to the CSS management console.
- Click Clusters. Locate the row containing the target cluster and click Modify in the Operation column.
- On the displayed Modify Configuration page, specify New Nodes.
- For a cluster without master nodes, the number of remaining data nodes (including cold data nodes and other types of nodes) after scale-in must be greater than half of the original node number, and greater than the maximum number of index replicas.
- Ensure each AZ under each node type has at least one node after the scale-in.
- For a cluster with master nodes, after scale-in, there has to be an odd number of master nodes, and there has to be at least three of them.
- Ensure that the disk usage after scale-in is less than 80%.
- Services will not be interrupted during the cluster scale-in process.
- During scale-in, data on the node to be brought offline must be migrated to other nodes within 5 hours. Otherwise, the scale-in fails. If the data volume of a cluster is large, you are advised to perform the scale-in for multiple times.
-
- - Click Next.
- On the displayed Details page, confirm the specifications and click Submit.
- Click Back to Cluster List to switch to the Clusters page. If Scaling in is displayed in the Task Status column, the cluster specifications are being modified. If Available is displayed in the Cluster Status column, the scale-in is successful.
-
- Suggestions on Using Elasticsearch
-Elasticsearch is an open-source search engine. This section provides some suggestions on using Elasticsearch to help you better use CSS.
- Improving Indexing Efficiency- Sending data to Elasticsearch through multiple processes or threads
A single thread that sends bulk requests is unlikely to max out the indexing capability of a cluster. However, to maximize utilization of cluster resources and improve data processing efficiency, send data through multiple threads or processes.
-By testing, you can determine the optimal number of threads for bulk requests of the same size. You can progressively increase the number of threads until the CPU is saturated in the cluster. You are advised to use the nodes stats API to view the CPU status of a node. View the os.cpu.percent, os.cpu.load_average.1m, os.cpu.load_average.5m, and os.cpu.load_average.15m parameter settings for more details. For information on how to use the nodes stats API and parameter descriptions, see https://www.elastic.co/guide/en/elasticsearch/reference/6.2/cluster-nodes-stats.html#os-stats.
-For example, check whether the CPU is saturated if two threads are used during execution of bulk requests. If it is not saturated, increase the number of threads. If the load or CPU is saturated when the number of threads reaches N, you are advised to use N threads (the optimal number according to your testing) to execute bulk requests and improve indexing efficiency.
- - Increasing the refresh interval
By default, each shard is automatically refreshed once per second. However, the refresh frequency is not applicable to all scenarios. If you use Elasticsearch to index a large number of log files and want to increase the indexing speed instead of obtaining near-real-time search performance, you can reduce the refresh frequency of each index.
-PUT /my_logs
-{
- "settings": {
- "refresh_interval": "30s"
- }
-}
- - Disabling refresh and replicas for initial loads
If you need to import a large amount of data at a time, it is recommended that you disable refresh and replicas by setting refresh_interval to -1 and number_of_replicas to 0. After you import the data, set refresh_interval and number_of_replicas to the original values.
-
-
- Selecting Appropriate Number of Shards and ReplicasWhen you create index data, you are advised to specify the number of shards and replicas. Otherwise, default settings (five shards and one replica) will be used.
- The shard quantity is strongly relevant to the indexing speed. Too many or too few shards will lead to slow indexing. If you specify too many shards, numerous files will be opened during retrieval, slowing down the communication between servers. If you specify too few shards, the index size of a single shard may be too large, slowing down the indexing speed.
- Specify the shard quantity based on the node quantity, disk quantity, and index size. It is recommended that the size of a single shard not exceed 30 GB. The shard size is calculated using the following formula: Size of a shard = Total amount of data/Shard quantity
- PUT /my_index
-{
- "settings": {
- "number_of_shards": 1,
- "number_of_replicas": 0
- }
-}
-
- Storing Data in Different IndicesElasticsearch relies on Lucene to index and store data and it suits dense data, which means that all documents have the same field.
- - Avoiding putting unrelated data in the same index
Do not put documents that have different data structures into the same index. You can consider creating some smaller indices and use fewer shards to store the documents into the indices.
- - Avoiding putting different types in the same index
It may save time and efforts to put different types of documents into an index. However, be aware that Elasticsearch does not store documents based on type. Therefore, putting different types into one index will slow down indexing. If your document types do not have similar mappings, put them in the same index.
- - Avoiding field conflicts between different document types in an index
Avoid two different types that have fields of the same name but different mappings.
-
-
- Creating Indices by Time RangeYou are advised to create indices to store time-related data, such as log data, by time range, instead of storing all data in a super large index.
- For example, you can store data in an index named by year (example: logs_2014) or by month (example: logs_2014-10). When the volume of data becomes very large, you can store data in an index named by day (example: logs_2014-10-24).
- Creating indices by time range has the following advantages:
- - Specifying a suitable number of shards and replicas based on the current volume of data
You can flexibly set the number of shards and replicas for each index created by time range so that there is no need to set a large shard at the beginning. After the cluster capacity is expanded, the time range can be set to adapt to the cluster scale.
- - Deleting old data by deleting old indices
DELETE /logs_2014-09
- - Switching between indices using the alias mechanism
The following example illustrates how to delete index logs_2014-09 from alias mechanism logs_current and add index logs_2014-10. POST /_aliases
-{
- "actions": [
- { "add": { "alias": "logs_current", "index": "logs_2014-10" }},
- { "remove": { "alias": "logs_current", "index": "logs_2014-09" }}
- ]
-}
- - Optimizing the indices that are no longer updated, such as indices generated last week or month, to increase query efficiency
Combine multiple segments in the logs_2014-09-30 index into a shard, improving the query efficiency.
-Versions earlier than 7. xPUT /logs_2014-09-30/_settings
-{ "number_of_replicas": 0 }
-
-POST /logs_2014-09-30/_forcemerge?max_num_segments=1
-
-PUT /logs_2014-09-30/_settings
-{ "number_of_replicas": 1 }
- Versions later than 7.x
-PUT /logs_2014-09-30/_settings
-{ "number_of_replicas": 0 }
-
-POST /logs_2014-09-30/_forcemerge
-{
- "max_num_segments":1
-}
-
-PUT /logs_2014-09-30/_settings
-{ "number_of_replicas": 1 }
-
-
- Optimizing Index Configurations- Distinguishing between texts and keywords
In Elasticsearch, the string field is divided into two new data types: text used for full-text search and keyword used for keyword search.
-You are advised to configure exact-value fields without word segmentation, such as tags or enumerated values, as the keyword type.
-Versions earlier than 7.x
-PUT my_index1
-{
- "mappings": {
- "my_type": {
- "properties": {
- "tags": {
- "type": "keyword"
- },
- "full_name": {
- "type": "text"
- }
- }
- }
- }
-}
-Versions later than 7.x
-PUT my_index1
-{
- "mappings": {
- "properties": {
- "tags": {
- "type": "keyword"
- },
- "full_name": {
- "type": "text"
- }
- }
- }
- }
- - Aggregated statistics based on the text field
Aggregated statistics based on the text field is not a common requirement. In Elasticsearch, to use aggregated statistics based on the text field, you need to enable fielddata (disabled by default). However, enabling fielddata will consume significant memory.
-You are advised to conduct multifield mapping on the sub-word string to a text field for full-text search and a keyword field for aggregated statistics.
-Versions earlier than 7.x
-PUT my_index2
-{
- "mappings": {
- "my_type": {
- "properties": {
- "full_name": {
- "type": "text",
- "fields": {
- "raw": {
- "type": "keyword"
- }
- }
- }
- }
- }
- }
-}
-Versions later than 7.x
-PUT my_index2
-{
- "mappings": {
- "properties": {
- "full_name": {
- "type": "text",
- "fields": {
- "raw": {
- "type": "keyword"
- }
- }
- }
- }
- }
- }
-
-
- Using Index TemplatesElasticsearch allows you to use index templates to control settings and mappings of certain created indices, for example, controlling the shard quantity to 1 and disabling the _all field. You can use the index template to control the settings you want to apply to the created indices.
- - In the index template, you can use the template field to specify a wildcard.
- If there are multiple index templates, you can use order to specify the overwriting sequence. The greater the value, the higher the priority.
- In the following example, the index matching logstash-* uses the my_logs template, and the priority value of the my_logs template is 1.
- Versions earlier than 7.x
- PUT /_template/my_logs
-{
- "template": "logstash-*",
- "order": 1,
- "settings": {
- "number_of_shards": 1
- },
- "mappings": {
- "_default_": {
- "_all": {
- "enabled": false
- }
- }
- },
- "aliases": {
- "last_3_months": {}
- }
-}
-
- Versions later than 7.x
- PUT /_template/my_logsa
-{
- "index_patterns": ["logstasaah-*"],
- "order": 1,
- "settings": {
- "number_of_shards": 1
- },
- "mappings": {
- "properties": {
- "_all": {
- "enabled": false
- }
- }
- },
- "aliases": {
- "last_3_months": {}
- }
-}
- Data Backup and RestorationElasticsearch replicas provide high availability during runtime, which ensures service continuity even when sporadic data loss occurs.
- However, replicas do not protect against failures. In case of a failure, you need a backup of your cluster so that you can restore data.
- To back up cluster data, create snapshots and save them in OBS buckets. This backup process is "smart". You are advised to use your first snapshot to store a copy of your data. All subsequent snapshots will save the differences between the existing snapshots and the new data. As the number of snapshots increases, backups are added or deleted accordingly. This means that subsequent backups will take a shorter time because only a small volume of data needs to be transferred.
-
- Improving Query Efficiency by FilteringFilters are important because they are fast. They do not calculate relevance (skipping the entire scoring phase) and are easily cached.
- Usually, when you look for an exact value, you will not want to score the query. You would want to include/exclude documents, so you will use a constant_score query to execute the term query in a non-scoring mode and apply a uniform score of one.
- GET /my_store/products/_search
-{
- "query" : {
- "constant_score" : {
- "filter" : {
- "term" : {
- "city" : "London"
- }
- }
- }
- }
-}
-
-
- Retrieving Large Amount of Data Through Scroll APIIn the scenario where a large amount of data is returned, the query-then-fetch process supports pagination with the from and size parameters, but within limits. Results are sorted on each shard before being returned. However, with larger from values, the sorting process can become very heavy, using vast amounts of CPU, memory, and bandwidth. For this reason, deep pagination is not recommended.
- You can use a scroll query to retrieve large numbers of documents from Elasticsearch efficiently, without affecting system performance. Scrolling allows you to do an initial search and to keep pulling batches of results from Elasticsearch until there are no more results left.
-
- Differences Between Query and FilterIn general, a filter will outperform a scoring query.
- When used in filtering context, the query is said to be a non-scoring or filtering query. That is, the query simply asks the question: Does this document match? The answer is always a simple, binary yes|no.
- Typical filtering cases are listed as follows:
- - Is the created time in the range from 2013 to 2014?
- Does the status field contain the term "published"?
- Is the lat_lon field within 10 km of a specified point?
- When used in a querying context, the query becomes a "scoring" query. Similar to the non-scoring query, this query also determines if a document matches and how well the document matches. A typical use for a scoring query is to find documents:
- - Matching the words "full text search"
- Containing the word "run", but also matching "runs", "running", "jog", or "sprint"
- Containing the words "quick", "brown", and "fox" – the closer together they are, the more relevant the document
- Tagged with lucene, search, or java – the more tags, the more relevant the document
-
- Checking Whether a Query Is ValidQueries can become quite complex. Especially, when they are combined with different analyzers and field mappings, they can become a little difficult to follow. You can use the validate-query API to check whether a query is valid.
- For example, on the Kibana Console page, run the following command to check whether the query is valid. In this example, the validate request tells you that the query is invalid.
- Versions earlier than 7.x
- GET /gb/tweet/_validate/query
-{
- "query": {
- "tweet" : {
- "match" : "really powerful"
- }
-}
-}
- Versions later than 7.x
- GET /gb/tweet/_validate/query
-{
-"query": {
- "productName" : {
- "match" : "really powerful"
- }
- }
- }
- The response to the preceding validate request tells us that the query is invalid. To find out why it is invalid, add the explain parameter to the query string and execute the following command.
- Versions earlier than 7.x
- GET /gb/tweet/_validate/query?explain
-{
-"query": {
- "tweet" : {
- "match" : "really powerful"
- }
- }
- }
- Versions later than 7.x
- GET /gb/tweet/_validate/query?explain
-{
- "query": {
- "productName" : {
- "match" : "really powerful"
- }
-}
-}
- According to the command output shown in the following, the type of query (match) is mixed up with the name of the field (tweet).
- {
- "valid": false,
- "error": "org.elasticsearch.common.ParsingException: no [query] registered for [tweet]"
-}
- Using the explain parameter has the added advantage of returning a human-readable description of the (valid) query, which helps in understanding exactly how CSS interprets your query.
-
- PrerequisitesTo use the function of creating or restoring snapshots, the account or IAM user that logs in to the CSS management console must have both of the following permissions:
- Tenant Administrator for project OBS in region Global service
- CSS Administrator in the current region
Managing Automatic Snapshot Creation- In the left navigation pane of the CSS management console, click Clusters.
- On the Clusters page that is displayed, click the name of the target cluster. On the displayed page, click Cluster Snapshots.
- On the displayed Cluster Snapshots page, click the icon to the right of Cluster Snapshot to enable the cluster snapshot function.
- (Optional) After the cluster snapshot function is enabled, CSS automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click
 to the right of Basic Configuration. To ensure the security of snapshot data, you can select a key to encrypt the snapshot.In the displayed Edit Basic Configuration dialog box, you can either select an existing OBS bucket and IAM agency or create an OBS bucket and IAM agency. To create an OBS bucket, click Create Bucket. To create an IAM agency, click Create IAM Agency. For details, see Creating a Bucket and Creating an Agency. To encrypt the snapshot, select Snapshot Encryption and select a key.
+Managing Automatic Snapshot Creation- In the left navigation pane of the CSS management console, click Clusters.
- On the Clusters page that is displayed, click the name of the target cluster. On the displayed page, click Cluster Snapshots.
- On the displayed Cluster Snapshots page, click the icon to the right of Cluster Snapshot to enable the cluster snapshot function.
- (Optional) After the cluster snapshot function is enabled, CSS automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click
 to the right of Basic Configuration. To ensure the security of snapshot data, you can select a key to encrypt the snapshot.In the displayed Edit Basic Configuration dialog box, you can either select an existing OBS bucket and IAM agency or create an OBS bucket and IAM agency. To create an OBS bucket, click Create Bucket. To create an IAM agency, click Create IAM Agency. For details, see Creating a Bucket and Creating an Agency. To encrypt the snapshot, select Snapshot Encryption and select a key.
Table 1 Parameter descriptionParameter
|
@@ -51,23 +51,23 @@
- Click the icon to the right of Automatic Snapshot Creation to enable the automatic snapshot creation function.
- In the displayed Edit Snapshot Policy dialog box, specify parameters as required.
-
Figure 1 Automatic snapshot creation
- - Click OK.
After the policy for automatic snapshot creation is created, the policy information will be displayed on the Cluster Snapshots page. If you need to change the policy due to business changes, click .
-Snapshots that are automatically created according to the snapshot policy are displayed in the snapshot list, along with manually created snapshots. You can distinguish them by the Snapshot Type setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click  to sort snapshots based on related parameter settings.
-Figure 2 Automatic snapshot creation
+Figure 1 Automatic snapshot creation
+ - Click OK.
After the policy for automatic snapshot creation is created, the policy information will be displayed on the Cluster Snapshots page. If you need to change the policy due to business changes, click .
+Snapshots that are automatically created according to the snapshot policy are displayed in the snapshot list, along with manually created snapshots. You can distinguish them by the Snapshot Type setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click  to sort snapshots based on related parameter settings.
+Figure 2 Automatic snapshot creation
- (Optional) Disable the automatic snapshot creation function.
After you disable the automatic snapshot creation function, the system stops automatic creation of snapshots. If the system is creating a snapshot based on the automatic snapshot creation policy and the snapshot is not yet displayed in the snapshot list, you cannot disable the automatic snapshot creation function. In this case, if you click the button next to Automatic Snapshot Creation, a message is displayed, indicating that you cannot disable the function. You are advised to disable the function after the system completes automatic creation of the snapshot, and the created snapshot is displayed in the snapshot list.
When disabling the automatic snapshot creation function, you can choose whether to delete the snapshots that have been automatically created by selecting Delete automated snapshots in the displayed dialog box. By default, automatically created snapshots are not deleted.
- If you do not select Delete automated snapshots, automatically created snapshots are not deleted when you disable the automatic snapshot creation function. You can manually delete them later. For details, see Deleting a Snapshot. If you do not manually delete the automatically created snapshots and enable the automatic snapshot creation function again, then all snapshots with Snapshot Type set to Automated in the snapshot list of the cluster can only be automatically deleted by the system. Specifically, the system automatically deletes snapshots based on the snapshot policy configured when you enable the automatic snapshot creation function again. For example, if you set Retention Period (days) to 10, the system will automatically delete the snapshots that have been retained for more than 10 days.
- If you select Delete automated snapshots, all snapshots with Snapshot Type set to Automated in the snapshot list will be deleted when you disable the automatic snapshot creation function.
Manually Creating a Snapshot- In the left navigation pane of the CSS management console, click Clusters.
- On the Clusters page that is displayed, click the name of the target cluster. On the displayed page, click Cluster Snapshots.
Alternatively, on the Clusters page, locate the row that contains the target cluster and click More > Back Up and Restore in the Operation column to switch to the Cluster Snapshots page.
- - On the displayed Cluster Snapshots page, click the icon to the right of Cluster Snapshot to enable the cluster snapshot function.
 indicates that the cluster snapshot function is disabled.
- indicates that the cluster snapshot function is enabled.
- - (Optional) After the cluster snapshot function is enabled, CSS automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click to the right of Basic Configuration. For details about how to configure parameters involved in the basic configuration, see 4.
- After basic configurations are completed, click Create.
- Name indicates the name of the manually created snapshot, which can contain 4 to 64 characters and must start with a lowercase letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed. For snapshots you create manually, you can specify the snapshot name. The system will not automatically add the time information to the snapshot name.
- Index: Enter the name of an index. The manually created snapshot can back up data of certain indices in the cluster. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?) are not allowed. Multiple index names are separated by commas (,). If you do not specify this parameter, data of all indices in the cluster is backed up by default. You can use the asterisk (*) to back up data of certain indices. For example, if you enter 2018-06*, then data of indices with the name prefix of 2018-06 will be backed up.
Run the GET /_cat/indices command in Kibana to query all index names in the cluster.
+ - On the displayed Cluster Snapshots page, click the icon to the right of Cluster Snapshot to enable the cluster snapshot function.
 indicates that the cluster snapshot function is disabled.
+ indicates that the cluster snapshot function is enabled.
+ - (Optional) After the cluster snapshot function is enabled, CSS automatically creates the OBS bucket and IAM agency for you to store snapshots. The automatically created OBS bucket and IAM agency are displayed on the page. If you want to change the OBS bucket and IAM agency, click to the right of Basic Configuration. For details about how to configure parameters involved in the basic configuration, see 4.
- After basic configurations are completed, click Create.
- Name indicates the name of the manually created snapshot, which can contain 4 to 64 characters and must start with a lowercase letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed. For snapshots you create manually, you can specify the snapshot name. The system will not automatically add the time information to the snapshot name.
- Index: Enter the name of an index. The manually created snapshot can back up data of certain indices in the cluster. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?) are not allowed. Multiple index names are separated by commas (,). If you do not specify this parameter, data of all indices in the cluster is backed up by default. You can use the asterisk (*) to back up data of certain indices. For example, if you enter 2018-06*, then data of indices with the name prefix of 2018-06 will be backed up.
Run the GET /_cat/indices command in Kibana to query all index names in the cluster.
- Description: indicates the description of the created snapshot. The value contains 0 to 256 characters, and certain special characters (<>) are not allowed.
-Figure 3 Creating a snapshot
- - Click OK.
After the snapshot is created, it will be displayed in the snapshot list. The status Available indicates that the snapshot is created successfully. All automatically and manually created snapshots are displayed in the snapshot list. You can distinguish them by the Snapshot Type setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click to sort snapshots based on related parameter settings.
+Figure 3 Creating a snapshot
+ - Click OK.
After the snapshot is created, it will be displayed in the snapshot list. The status Available indicates that the snapshot is created successfully. All automatically and manually created snapshots are displayed in the snapshot list. You can distinguish them by the Snapshot Type setting. In the upper right corner of the snapshot list, enter the keyword of the snapshot name or snapshot ID to search for the desired snapshots. You can also click to sort snapshots based on related parameter settings.
Restoring DataYou can use snapshots whose Snapshot Status is Available to restore cluster data. The stored snapshot data can be restored to other clusters.
@@ -76,9 +76,9 @@
Rename Pattern: Enter a regular expression. Indices that match the regular expression are restored. The default value index_(.+) indicates restoring data of all indices. The value contains 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?,) are not allowed.
Rename Replacement: Enter the index renaming rule. The default value restored_index_$1 indicates that restored_ is added in front of the names of all restored indices. The value can contain 0 to 1,024 characters. Uppercase letters, spaces, and certain special characters (including "\<|>/?,) are not allowed. You can set Rename Replacement only if you have specified Rename Pattern.
Cluster: Select the cluster that you want to restore. You can select the current cluster or others. However, you can only restore the snapshot to clusters whose status is Available. If the status of the current cluster is Unavailable, you cannot restore the snapshot to the current cluster. If you select another cluster and two or more indices in the cluster have the same name, data of all indices with the same name as the name you specify will be overwritten. Therefore, exercise caution when you set the parameters.
- Figure 4 Restoring a snapshot
+ Figure 4 Restoring a snapshot
- - Click OK. If restoration succeeds, Task Status of the snapshot in the snapshot list will change to Restoration succeeded, and the index data is generated again according to the snapshot information.
Figure 5 Successful restoration
+ - Click OK. If restoration succeeds, Task Status of the snapshot in the snapshot list will change to Restoration succeeded, and the index data is generated again according to the snapshot information.
Figure 5 Successful restoration
Deleting a SnapshotIf you no longer need a snapshot, delete it to release storage resources. If the automatic snapshot creation function is enabled, snapshots that are automatically created cannot be deleted manually, and the system automatically deletes these snapshots on the half hour after the time specified by Retention Period (days). If you disable the automatic snapshot creation function while retaining the automated snapshots, then you can manually delete them later. If you do not manually delete the automatically created snapshots and enable the automatic snapshot creation function again, then all snapshots with Snapshot Type set to Automated in the snapshot list of the cluster can only be automatically deleted by the system.
diff --git a/docs/css/umn/css_01_0043.html b/docs/css/umn/css_01_0043.html
deleted file mode 100644
index aa08659e..00000000
--- a/docs/css/umn/css_01_0043.html
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
- Creating Alarm Rules
- You can create the alarm rules for cluster metrics on the Cloud Eye management console. If the monitored metrics meet the specified alarm rule, alarms are reported. In this case, you can learn about cluster exceptions in time and take proper measures.
- Procedure- Log in to the Cloud Eye console.
- In the left navigation pane, choose Alarm Management > Alarm Rules.
- Click Create Alarm Rule in the upper right corner.
- In the displayed Create Alarm Rule page, set parameters as required.
You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batches for multiple cloud service instances. In this example, assume that you use the alarm template to create the alarm rule for the CSS cluster.
-- Configure the name and description of an alarm rule.
-
Table 1 Parameter descriptionParameter
- |
-Description
- |
-Example Value
- |
-
|---|
-
-Name
- |
-Name of the alarm rule. The system automatically generates a name, which you can change if required.
- |
-alarm-p8v9
- |
-
-Description
- |
-Alarm rule description. This parameter is optional.
- |
--
- |
-
-
-
- - Select a monitored object and set alarm content parameters.
-
Table 2 Parameters for configuring alarmsParameter
- |
-Description
- |
-Example Value
- |
-
|---|
-
-Resource Type
- |
-Name of the service for which the alarm rule is configured
- |
-Cloud Search Service
- |
-
-Dimension
- |
-Metric dimension of the alarm rule. Currently, the following dimensions are supported:
-- CSS Clusters: Alarm rules are specified by cluster.
- CSS Clusters - CSS Instances: Alarm rules are specified by node in a cluster.
- |
-CSS clusters
- |
-
-Monitoring Scope
- |
-Resource range to which the alarm rule applies. You can select Resource groups or Specific resources.
-Note:
-- If you select Resource groups and any resource in the group meets the alarm policy, an alarm is triggered.
- If you select Specific resources, select one or more monitored objects and click
 to synchronize the monitored object or objects to the dialog box on the right.
- |
-Specific resources
- |
-
-
-
- - Specify Method, Template, and Alarm Notification.
-
Table 3 Parameter descriptionParameter
- |
-Description
- |
-Example Value
- |
-
|---|
-
-Method
- |
-Select Use template or Create manually.
-If you set Monitoring Scope to Specific resources, you can set Method to Use template.
- |
-Create manually
- |
-
-Template
- |
-Template you want to import
- |
--
- |
-
-Alarm Notification
- |
-If you enable this function, specify Validity Period, Notification Object, and Trigger Condition.
- |
--
- |
-
-
-
- - Click Create.
After the alarm rule is successfully created, it will be displayed in the alarm rule list
-
-
-
-
-
-
diff --git a/docs/css/umn/css_01_0044.html b/docs/css/umn/css_01_0044.html
deleted file mode 100644
index 7b1d5a5b..00000000
--- a/docs/css/umn/css_01_0044.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
- Viewing Metrics
- Cloud Eye performs daily monitoring on core cluster metrics for CSS. You can log in to the Cloud Eye management console to view cluster metrics.
- Cloud Eye only monitors clusters that have been successfully created in real time.
- Prerequisites- The cluster status is Available or Processing.
You cannot view the metrics for deleted clusters or the metrics for the clusters those whose Status is Abnormal or Creating on the Cloud Eye management console. If the status of a cluster changes from Abnormal or Creating to Available, you can view its metrics in real time after approximately 10 minutes.
-
- - The cluster has been running for about 10 minutes.
- You have created alarm rules.
-
- Procedure- Log in to the CSS management console.
- Choose Clusters. Select a cluster. In the Operation column, choose More > View Metric.
- Click the tab for the time range you want to view.
- View the monitoring data.
-
-
-
-
diff --git a/docs/css/umn/css_01_0048.html b/docs/css/umn/css_01_0048.html
index 849d0630..5a7fb74c 100644
--- a/docs/css/umn/css_01_0048.html
+++ b/docs/css/umn/css_01_0048.html
@@ -10,7 +10,7 @@
- After installing Logstash, perform the following steps to import data. For details about how to install Logstash, visit the following website: https://www.elastic.co/guide/en/logstash/current/installing-logstash.html
- The JDK must be installed before Logstash is installed. In Linux OS, you can run the yum -y install java-1.8.0 command to install JDK 1.8.0. In Windows OS, you can download the required JDK version from the official website of JDK, and install it by following the installation guide.
- In the Importing Data When Logstash Is Deployed on an ECS scenario, ensure that the ECS and the Elasticsearch cluster to which data is imported reside in the same VPC.
Importing Data When Logstash Is Deployed on the External NetworkFigure 1 illustrates how data is imported when Logstash is deployed on an external network.
- Figure 1 Importing data when Logstash is deployed on an external network
+ Figure 1 Importing data when Logstash is deployed on an external network
- Create a jump host and configure it as follows:
- The jump host is an ECS running the Linux OS and has been bound with an EIP.
- The jump host resides in the same VPC as the CSS cluster.
- SSH local port forwarding is configured for the jump host to forward requests from a chosen local port to port 9200 on one node of the CSS cluster.
- Refer to SSH documentation for the local port forwarding configuration.
- Use PuTTY to log in to the created jump host with the EIP.
- Run the following command to perform port mapping and transfer the request sent to the port on the jump host to the target cluster:
ssh -g -L <Local port of the jump host:Private network address and port number of a node> -N -f root@<Private IP address of the jump host>
@@ -69,7 +69,7 @@ output {
If a license error is reported, set ilm_enabled to false.
If the cluster has the security mode enabled, you need to download a certificate first.
-- Download a certificate on the Basic Information page of the cluster.
Figure 2 Downloading a certificate
+- Download a certificate on the Basic Information page of the cluster.
Figure 2 Downloading a certificate
- Store the certificate to the server where Logstash is deployed.
- Modify the logstash-simple.conf configuration file.
Consider the data files in the /tmp/access_log/ path mentioned in 4 as an example. Assume that data import starts from data in the first row of the data file, the filtering condition is left unspecified (indicating no data processing operations are performed), and the public IP address and port number of the jump host are 192.168.0.227 and 9200, respectively. The name of the index for importing data is myindex, and the certificate is stored in /logstash/logstash6.8/config/CloudSearchService.cer. Edit the configuration file as follows, and enter :wq to save the configuration file and exit. input{
file {
path => "/tmp/access_log/*"
@@ -94,13 +94,13 @@ output{
- Run the following command to import the data collected by Logstash to the cluster:
./bin/logstash -f logstash-simple.conf
This command must be executed in the directory where the logstash-simple.conf file is stored. For example, if the logstash-simple.conf file is stored in /root/logstash-7.1.1/, go to the directory before running the command.
- - Log in to the CSS management console.
- In the left navigation pane, click Clusters to switch to the Clusters page.
- From the cluster list, locate the row that contains the cluster to which you want to import data and click Access Kibana in the Operation column.
- In the left navigation pane of the displayed Kibana window, click Dev Tools.
Figure 3 Logging in to Dev Tools
+ - Log in to the CSS management console.
- In the left navigation pane, click Clusters to switch to the Clusters page.
- From the cluster list, locate the row that contains the cluster to which you want to import data and click Access Kibana in the Operation column.
- In the left navigation pane of the displayed Kibana window, click Dev Tools.
Figure 3 Logging in to Dev Tools
- On the Console page of Kibana, search for the imported data.
On the Console page of Kibana, enter the following command to search for data. View the search results. If the searched data is consistent with the imported data, the data has been imported successfully.
GET myindex/_search
Importing Data When Logstash Is Deployed on an ECSFigure 4 illustrates how data is imported when Logstash is deployed on an ECS that resides in the same VPC as the cluster to which data is to be imported.
- Figure 4 Importing data when Logstash is deployed on an ECS
+ Figure 4 Importing data when Logstash is deployed on an ECS
- Ensure that the ECS where Logstash is deployed and the cluster to which data is to be imported reside in the same VPC, port 9200 of the ECS security group has been assigned external network access permissions, and an EIP has been bound to the ECS.
- If there are multiple servers in a VPC, you do not need to associate EIPs to other servers as long as one server is associated with an EIP. Switch to the node where Logstash is deployed from the node with which the EIP is associated.
- If a private line or VPN is available, you do not need to associate an EIP.
- Use PuTTY to log in to the ECS.
For example, data file access_20181029_log is stored in the /tmp/access_log/ path of the ECS, and the data file includes the following data: | All | Heap used for segments | | 18.6403 | MB |
@@ -153,7 +153,7 @@ output {
}
}
If the cluster has the security mode enabled, you need to download a certificate first.
- - Download a certificate on the Basic Information page of the cluster.
Figure 5 Downloading a certificate
+- Download a certificate on the Basic Information page of the cluster.
Figure 5 Downloading a certificate
- Store the certificate to the server where Logstash is deployed.
- Modify the logstash-simple.conf configuration file.
Consider the data files in the /tmp/access_log/ path mentioned in 2 as an example. Assume that data import starts from data in the first row of the data file, the filtering condition is left unspecified (indicating no data processing operations are performed), the public IP address and port number of the jump host are 192.168.0.227 and 9200, respectively. The name of the index for importing data is myindex, and the certificate is stored in /logstash/logstash6.8/config/CloudSearchService.cer. Edit the configuration file as follows, and enter :wq to save the configuration file and exit. input{
file {
path => "/tmp/access_log/*"
@@ -177,7 +177,7 @@ output{
- Run the following command to import the ECS data collected by Logstash to the cluster:
./bin/logstash -f logstash-simple.conf
- - Log in to the CSS management console.
- In the left navigation pane, click Clusters to switch to the Clusters page.
- From the cluster list, locate the row that contains the cluster to which you want to import data and click Access Kibana in the Operation column.
- In the left navigation pane of the displayed Kibana window, click Dev Tools.
Figure 6 Choosing Dev Tools
+ - Log in to the CSS management console.
- In the left navigation pane, click Clusters to switch to the Clusters page.
- From the cluster list, locate the row that contains the cluster to which you want to import data and click Access Kibana in the Operation column.
- In the left navigation pane of the displayed Kibana window, click Dev Tools.
Figure 6 Choosing Dev Tools
- On the Console page of Kibana, search for the imported data.
On the Console page of Kibana, enter the following command to search for data. View the search results. If the searched data is consistent with the imported data, the data has been imported successfully.
GET myindex/_search
diff --git a/docs/css/umn/css_01_0051.html b/docs/css/umn/css_01_0051.html
index 92b24de2..2bf4e19b 100644
--- a/docs/css/umn/css_01_0051.html
+++ b/docs/css/umn/css_01_0051.html
@@ -2,12 +2,12 @@
Viewing Audit Logs
After you enable CTS, it starts recording operations related to CSS. The CTS management console stores the last seven days of operation records. This section describes how to query the last seven days of operation records on the CTS management console.
- Procedure- Log in to the CTS management console.
- Click
 in the upper left corner and select a region. - In the left navigation pane, click Trace List.
- You can use filters to query traces. The following four filter criteria are available:
diff --git a/docs/css/umn/css_01_0056.html b/docs/css/umn/css_01_0056.html
index de86c699..30f5bb44 100644
--- a/docs/css/umn/css_01_0056.html
+++ b/docs/css/umn/css_01_0056.html
@@ -2,8 +2,8 @@
Introduction to the Cluster List
The cluster list displays all CSS clusters. If there are a large number of clusters, these clusters will be displayed on multiple pages. You can view clusters of all statuses from the cluster list.
- Clusters are listed in chronological order by default in the cluster list, with the most recent cluster displayed at the top. You can click  next to the related parameter in the table heading to modify cluster sorting. Table 1 describes the parameters involved in the cluster list.
- In the upper right corner of the cluster list, you can enter the name or ID of a cluster and click  to search for a cluster. You can also click  in the upper right corner to refresh the cluster list.
+ Clusters are listed in chronological order by default in the cluster list, with the most recent cluster displayed at the top. You can click  next to the related parameter in the table heading to modify cluster sorting. Table 1 describes the parameters involved in the cluster list.
+ In the upper right corner of the cluster list, you can enter the name or ID of a cluster and click  to search for a cluster. You can also click  in the upper right corner to refresh the cluster list.
Table 1 Cluster list parameter descriptionParameter
|
diff --git a/docs/css/umn/css_01_0058.html b/docs/css/umn/css_01_0058.html
index fffdc8a8..1ba09579 100644
--- a/docs/css/umn/css_01_0058.html
+++ b/docs/css/umn/css_01_0058.html
@@ -2,7 +2,7 @@
Binding an Enterprise Project
You must configure an enterprise project for each cluster. If you do not need to distinguish enterprise projects for clusters, you can bind clusters to the default project. For clusters created before the binding an enterprise project feature was released, their enterprise projects were bound to the default project. You can modify the enterprise project based on the site requirements.
- Binding an Enterprise ProjectWhen creating a cluster, you can bind it to an enterprise project by specifying the Enterprise Project parameter. For details, see .
+
Modifying an Enterprise ProjectFor a cluster that has been created, you can modify its enterprise project based on the site requirements.
- On the CSS management console, click Clusters.
- In the cluster list on the displayed page, click the target cluster name to switch to the Basic Information page.
- On the displayed page, click the parameter value on the right of Enterprise Project. The Project Management page of the Resource Management is displayed.
- On the Resources tab page, select the corresponding Region and select Cloud Search Service from Service. In this case, the corresponding CSS cluster is displayed in the resource list.
- Select the cluster whose enterprise project you want to modify and click Remove.
- On the Remove Resource page, specify Mode and select Destination Enterprise Project, and click OK.
- After you complete the preceding steps, you can view the enterprise project bound to the cluster in either of the following ways:
- Switch to the CSS cluster list, where the value of Enterprise Project for the cluster is changed to the new enterprise project.
- On the Resource Management page, click Project Management in the navigation pane on the left. On the displayed page, click View Migration Event to obtain the cluster information.
diff --git a/docs/css/umn/css_01_0060.html b/docs/css/umn/css_01_0060.html
index a42de352..7f23824b 100644
--- a/docs/css/umn/css_01_0060.html
+++ b/docs/css/umn/css_01_0060.html
@@ -6,7 +6,7 @@
Deleting a Failed TaskYou can delete one or all failed tasks at a time.
- To delete a failed task, perform the following operations: Locate the row that contains the target task and click Delete in the Operation column. In the displayed dialog box, confirm the task you want to delete and click Yes.
- To delete all failed tasks, perform the following operations: In the Failed Tasks dialog box, click Delete All. In the displayed dialog box, confirm the information about all failed tasks and click Yes.
- Figure 1 Deleting a failed task
+ Figure 1 Deleting a failed task
Error Code
Table 1 Failure causesError Code
diff --git a/docs/css/umn/css_01_0072.html b/docs/css/umn/css_01_0072.html
index 110f9e39..8c83810a 100644
--- a/docs/css/umn/css_01_0072.html
+++ b/docs/css/umn/css_01_0072.html
@@ -7,7 +7,7 @@
This section describes the procedure for granting permissions (see Figure 1).
PrerequisitesBefore assigning permissions to user groups, you should learn about the system policies listed in Permissions Management.
Process FlowFigure 1 Process for granting CSS permissions
+ Process FlowFigure 1 Process for granting CSS permissions
- Create a user group and assign permissions
Create a user group on the IAM console, and assign the CSS permission to the group.
- Create a user and add it to a user group
Create a user on the IAM console and add the user to the group created in 1. Create a user group a....
- Log in as an IAM user and verify permissions.
Log in to the CSS console as the created user, and verify that it only has read permissions for CSS.
diff --git a/docs/css/umn/css_01_0077.html b/docs/css/umn/css_01_0077.html
index b0ddbfbf..5b08dd46 100644
--- a/docs/css/umn/css_01_0077.html
+++ b/docs/css/umn/css_01_0077.html
@@ -2,7 +2,7 @@
Managing Logs
CSS provides log backup and search functions to help you locate faults. You can back up cluster logs to OBS buckets and download required log files to analyze and locate faults.
- Enabling Log Management- Log in to the CSS management console.
- On the Clusters page, click the name of the cluster whose logs you want to back up. The Basic Information page is displayed.
- Click the Logs tab and enable Log Management.
 indicates that the log management function is disabled.  indicates that it is enabled.
+Enabling Log Management- Log in to the CSS management console.
- On the Clusters page, click the name of the cluster whose logs you want to back up. The Basic Information page is displayed.
- Click the Logs tab and enable Log Management.
 indicates that the log management function is disabled.  indicates that it is enabled.
- Enable the Log Management function. In the Edit Log Backup Configuration dialog box, set the parameters.
In the displayed dialog box, OBS Bucket, Backup Path, and IAM Agency are automatically created for log backup. You can modify the default value by referring to Table 1.
Table 1 Parameter descriptionParameter
@@ -33,16 +33,16 @@
|
|---|
- (Optional) If the Log Management function has been enabled for the cluster, you can modify the log backup parameters.
Click  on the right of Log Backup Configuration. The Edit Log Backup Configuration dialog box is displayed. You can modify the log backup parameters.
+ - (Optional) If the Log Management function has been enabled for the cluster, you can modify the log backup parameters.
Click  on the right of Log Backup Configuration. The Edit Log Backup Configuration dialog box is displayed. You can modify the log backup parameters.
- Back up logs.
- Automatically backing up logs
Click the icon on the right of Auto Backup to enable the auto backup function.
- indicates that the auto backup function is enabled, and indicates that it is disabled.
-After the automatic backup function is enabled, set the backup start time in the Modify Log Backup Policy dialog box. When the scheduled time arrives, the system will back up logs automatically. Click  on the right of the switch to change Backup Start Time.
+ indicates that the auto backup function is enabled, and indicates that it is disabled.
+After the automatic backup function is enabled, set the backup start time in the Modify Log Backup Policy dialog box. When the scheduled time arrives, the system will back up logs automatically. Click  on the right of the switch to change Backup Start Time.
- Manually backing up logs
On the Log Backup tab page, click Back Up. On the displayed page, click Yes to start backup.
If Task Status in the log backup list is Successful, the backup is successful.
All logs in the cluster are copied to a specified OBS path. You can view or download log files from the path of the OBS bucket.
- - Search for logs.
On the Log Search page, select the desired node, log type, and log level, and click  . The search results are displayed.
+ - Search for logs.
On the Log Search page, select the desired node, log type, and log level, and click  . The search results are displayed.
When you search for logs, the latest 10,000 logs are matched. A maximum of 100 logs are displayed.
The VPC endpoint service allows you to access the cluster through a private domain name. When the VPC endpoint service is enabled, the system creates a VPC endpoint for you by default. To create a VPC endpoint, you must have the required permissions. For details, see .
 The public IP address access and VPC endpoint service share a load balancer. If you have configured a public access whitelist, public and private IP addresses that access the cluster through VPCEP are restricted because the public IP address access shares the load balancer with the VPC endpoint service. In this case, you need to add IP address 198.19.128.0/17 to the public access whitelist to allow traffic through VPCEP.
- Enabling the VPC Endpoint Service- Log in to the CSS management console.
- On the Create Cluster page, set Advanced Settings to Custom. Enable the VPC endpoint service.
|
|---|
- Figure 1 Configuring basic information
- Set host specifications of the cluster.
Table 4 Parameter descriptionParameter
|
@@ -181,7 +180,7 @@
|---|
Figure 2 Configuring node specifications
+Figure 1 Configuring node specifications
- Set network specifications of the cluster.
Table 5 Parameter descriptionParameter
|
@@ -220,7 +219,7 @@
|---|
Figure 3 Configuring network specifications
+Figure 2 Configuring network specifications
- Set the enterprise project of the cluster.
When creating a CSS cluster, you can bind an enterprise project to the cluster if you have enabled enterprise project. You can select an enterprise project created by the current user from the drop-down list or click View Project Project to go to the Enterprise Project Management console and create a new project or view existing projects.
- Configure automatic snapshot creation for the cluster.
By default, the cluster snapshot function is enabled. If you do not need this function, you can disable Cluster Snapshot.
Basic Configuration- OBS Bucket: name of the OBS bucket used for storing snapshots.
- Backup Path: storage path of the snapshot in the OBS bucket.
- IAM Agency: authorized by the current account for CSS to access or maintain data stored in the OBS bucket.
@@ -229,7 +228,7 @@
Automatic Snapshot Creation
You can customize Snapshot Name Prefix, Backup Start Time, and Retention Period (days) as required.
- Snapshot Name Prefix: Enter a maximum of 32 characters starting with a lowercase letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed.. A snapshot name consists of a snapshot name prefix and a timestamp. For example, snapshot-1566921603720.
- Backup Started: indicates the time when the backup starts automatically every day. You can specify this parameter only in hours, for example, 00:00 or 01:00. The value ranges from 00:00 to 23:00. Select a time from the drop-down list box.
- Retention Period (days): indicates the duration when snapshots are retained in the OBS bucket, in days. The value ranges from 1 to 90. You can specify this parameter as required. The system automatically deletes expired snapshots every hour at half past the hour.
- - Configure advanced settings for the cluster.
- Default: The the VPC Endpoint Service, Kibana Public Access, and Tag functions are disabled by default. You can manually enable these functions after the cluster is created.
- Custom: You can enable the VPC Endpoint Service and Tag functions as required.
+ - Configure advanced settings for the cluster.
- Default: The the VPC Endpoint Service, and Tag functions are disabled by default. You can manually enable these functions after the cluster is created.
- Custom: You can enable the VPC Endpoint Service and Tag functions as required.
Table 6 Parameters for advanced settingsParameter
|
@@ -242,11 +241,6 @@
After enabling this function, you can obtain a private domain name for accessing the cluster in the same VPC. For details, see VPC Endpoint Service.
|
|---|
-Kibana Public Access
- |
-Clusters in non-security mode cannot access Kibana through the Internet.
- |
-
Tag
|
Adding tags to clusters can help you identify and manage your cluster resources. You can customize tags or use tags predefined by TMS. For details, see Managing Tags.
diff --git a/docs/css/umn/css_01_0109.html b/docs/css/umn/css_01_0109.html
index b25c8d31..c30b8fa9 100644
--- a/docs/css/umn/css_01_0109.html
+++ b/docs/css/umn/css_01_0109.html
@@ -5,17 +5,17 @@
Procedure This section takes Kibana 7.6.2 as an example to describe the procedure.
- - Log in to the CSS management console.
- Click Access Kibana in the Operation column of a cluster.
Figure 1 Logging in to Kibana (1)
- - Log in to Kibana.
Figure 2 Logging in to Kibana (2)
+- Log in to the CSS management console.
- Click Access Kibana in the Operation column of a cluster.
Figure 1 Logging in to Kibana (1)
+ - Log in to Kibana.
Figure 2 Logging in to Kibana (2)
- Username: admin
- Password: Enter the password set during cluster creation.
- Click the Security icon on the Kibana operation page.
Figure 3 Going to the Security page
- - Create a user.
- Choose Authentication Backends >Internal Users Database.
Figure 4 Adding a user (1)
- - On the Internal Users Database page, choose
 . The page for adding user information is displayed.Figure 5 Adding a user (2)
+ - Click the Security icon on the Kibana operation page.
Figure 3 Going to the Security page
+ - Create a user.
- Choose Authentication Backends >Internal Users Database.
Figure 4 Adding a user (1)
+ - On the Internal Users Database page, choose
 . The page for adding user information is displayed.Figure 5 Adding a user (2)
- On the user creation page, configure Username and Password, and click Submit.
The user will be displayed in the user list.
- - Configure roles and permissions for the user.
- Click Roles.
Figure 6 Adding a role
- - On the Open Distro Security Roles page, click .
- Enter a role name on the Overview page.
Figure 7 Entering a role name
+ - Configure roles and permissions for the user.
- Click Roles.
Figure 6 Adding a role
+ - On the Open Distro Security Roles page, click .
- Enter a role name on the Overview page.
Figure 7 Entering a role name
- Configure CSS cluster permissions on the Cluster Permissions page. You can skip this step.
- Configure index permissions on the Index Permissions page.
Index patterns: Set this parameter to the name of the index whose permission needs to be configured. For example, my_store. Use different names for the index and the user.
@@ -23,8 +23,8 @@
- Retain the default settings on the Tenant Permissions page.
After the configuration is complete, the role will be displayed.
- - Assign a role to the user.
- Click Role Mappings.
Figure 8 Role mapping
- - Click to add the mapping between users and roles.
Figure 9 Users and roles
+ - Assign a role to the user.
- Click Role Mappings.
Figure 8 Role mapping
+ - Click to add the mapping between users and roles.
Figure 9 Users and roles
- Click Submit.
- Verify that the configuration takes effect in Kibana.
| Name
|
User-defined cluster name.
-You can click  on the right to change the cluster name.
+You can click  on the right to change the cluster name.
|
ID
diff --git a/docs/css/umn/css_02_0001.html b/docs/css/umn/css_02_0001.html
index 8f732c5e..0d091a03 100644
--- a/docs/css/umn/css_02_0001.html
+++ b/docs/css/umn/css_02_0001.html
@@ -4,7 +4,7 @@
|
|---|
|---|
|
Figure 1 Console page
next to the cluster name. After the modification is completed, click 
to save the modification. If you want to cancel the modification, click 
.NOTE:
next to the cluster name. After the modification is completed, click 
to save the modification. If you want to cancel the modification, click 
.
