forked from docs/doc-exports
css umn 25.6.0 version
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: zhengxiu <zhengxiu@huawei.com> Co-committed-by: zhengxiu <zhengxiu@huawei.com>
This commit is contained in:
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -15,11 +15,13 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_04_0047.html">Differences Between Elasticsearch Cluster Versions</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_04_0042.html">Differences Between Elasticsearch and OpenSearch</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_04_0014.html">Permissions Management</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_04_0005.html">Constraints</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0000001950350846.html">Performance Metrics</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_04_0008.html">Performance Metrics</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_04_0004.html">Related Services</a></strong><br>
|
||||
</li>
|
||||
@ -5,9 +5,9 @@
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0000002098813645.html">Using Elasticsearch for Data Search</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="index.html">Using Elasticsearch for Data Search</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="en-us_topic_0000002098695185.html">Using OpenSearch for Data Search</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_08_0003.html">Using OpenSearch for Data Search</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
166
docs/css/umn/css_01_0001.html
Normal file
166
docs/css/umn/css_01_0001.html
Normal file
File diff suppressed because it is too large
Load Diff
133
docs/css/umn/css_01_0002.html
Normal file
133
docs/css/umn/css_01_0002.html
Normal file
File diff suppressed because it is too large
Load Diff
23
docs/css/umn/css_01_0004.html
Normal file
23
docs/css/umn/css_01_0004.html
Normal file
@ -0,0 +1,23 @@
|
||||
<a name="EN-US_TOPIC_0000001965496965"></a><a name="EN-US_TOPIC_0000001965496965"></a>
|
||||
|
||||
<h1 class="topictitle1">Importing Data to an Elasticsearch Cluster</h1>
|
||||
<div id="body1504584479327"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0005.html">Different Ways to Ingest Data into an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0048.html">Using In-house Built Logstash to Import Data to Elasticsearch</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0024.html">Using Open Source Elasticsearch APIs to Import Data to Elasticsearch</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0046.html">Using CDM to Import Data to Elasticsearch</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0228.html">Enhancing the Data Ingestion Performance of Elasticsearch Clusters</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0207.html">Using Elasticsearch for Data Search</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
53
docs/css/umn/css_01_0005.html
Normal file
53
docs/css/umn/css_01_0005.html
Normal file
@ -0,0 +1,53 @@
|
||||
<a name="EN-US_TOPIC_0000001945265112"></a><a name="EN-US_TOPIC_0000001945265112"></a>
|
||||
|
||||
<h1 class="topictitle1">Different Ways to Ingest Data into an Elasticsearch Cluster</h1>
|
||||
<div id="body0000001945265112"><div class="section" id="EN-US_TOPIC_0000001945265112__section1218985910454"><h4 class="sectiontitle">Introduction</h4><p id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_p5636738181213">Elasticsearch clusters support multiple data ingestion methods, as listed in <a href="#EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_table114913297713">Table 1</a>. Select one that fits your needs the best. Before starting to ingest data, determine whether to enhance the data ingestion performance of Elasticsearch clusters first. For details, see <a href="css_01_0228.html">Enhancing the Data Ingestion Performance of Elasticsearch Clusters</a>.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_table114913297713"></a><a name="en-us_topic_0000001961259049_table114913297713"></a><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_table114913297713" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Different ways to ingest data into an Elasticsearch cluster</caption><thead align="left"><tr id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_row914911291275"><th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.1.3.2.5.1.1"><p id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_p10149152919711">Data Ingestion Method</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.1.3.2.5.1.2"><p id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_p41497296713">Scenario</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="22%" id="mcps1.3.1.3.2.5.1.3"><p id="EN-US_TOPIC_0000001945265112__p10123334115516">Supported Data Formats/Sources</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.1.3.2.5.1.4"><p id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_p181496292716">Details</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_row214982915714"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001945265112__p11792181416384">Open-source Logstash</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.1.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001945265112__p1194151715616">Open-source Logstash offers a server-side, real-time data processing pipeline, which supports data ingestion from multiple sources. It can be used to ingest various types of data, such as logs, monitoring data, and metrics.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.1.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001945265112__p12123334205518">JSON, CSV, and text</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.1.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001945265112__p6138135455019"><a href="css_01_0048.html">Using In-house Built Logstash to Import Data to Elasticsearch</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_row123514502113"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001945265112__p1378911419381">Open-source Elasticsearch API</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.1.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001945265112__p26761016183811">Open-source Elasticsearch APIs can be used to ingest data. This method is flexible, as you can write your own application code.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.1.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001945265112__p3123934165511">JSON</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.1.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001945265112__p513811544509"><a href="css_01_0024.html">Using Open Source Elasticsearch APIs to Import Data to Elasticsearch</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001945265112__en-us_topic_0000001961259049_row814919291979"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.1.3.2.5.1.1 "><p id="EN-US_TOPIC_0000001945265112__p1478961411380">Cloud Data Migration (CDM)</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.1.3.2.5.1.2 "><p id="EN-US_TOPIC_0000001945265112__p1678831418380">You can use CDM for batch data migration. For example, if data is stored in OBS or an Oracle database, CDM is recommended.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.1.3.2.5.1.3 "><p id="EN-US_TOPIC_0000001945265112__p81232034205515">JSON</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.1.3.2.5.1.4 "><p id="EN-US_TOPIC_0000001945265112__p3137754165015"><a href="css_01_0046.html">Using CDM to Import Data to Elasticsearch</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0004.html">Importing Data to an Elasticsearch Cluster</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -1,14 +1,14 @@
|
||||
<a name="css_01_0398"></a><a name="css_01_0398"></a>
|
||||
<a name="EN-US_TOPIC_0000001972511757"></a><a name="EN-US_TOPIC_0000001972511757"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Searching Data in an Elasticsearch Cluster</h1>
|
||||
|
||||
<div id="body0000001972511757"><p id="css_01_0398__p8060118"></p>
|
||||
<div id="body0000001972511757"><p id="EN-US_TOPIC_0000001972511757__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0399.html">Using DSL to Search for Data in Elasticsearch</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0007.html">Using DSL to Search for Data in Elasticsearch</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0061.html">Using SQL to Search for Data in Elasticsearch</a></strong><br>
|
||||
</li>
|
||||
79
docs/css/umn/css_01_0007.html
Normal file
79
docs/css/umn/css_01_0007.html
Normal file
@ -0,0 +1,79 @@
|
||||
<a name="EN-US_TOPIC_0000001945472646"></a><a name="EN-US_TOPIC_0000001945472646"></a>
|
||||
|
||||
<h1 class="topictitle1">Using DSL to Search for Data in Elasticsearch</h1>
|
||||
<div id="body0000001945472646"><p id="EN-US_TOPIC_0000001945472646__p17394111161812">DSL is the specified query language for Elasticsearch. It is the best language for interaction between Elasticsearch clusters and clients. Elasticsearch DSL is a JSON-based language. Other languages, such as SQL, are translated into Elasticsearch DSL before they can be used for interacting with Elasticsearch clusters.</p>
|
||||
<p id="EN-US_TOPIC_0000001945472646__p196561415590">This topic lists some of the most commonly used Elasticsearch DSL query statements. For more, see <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.10/query-dsl.html" target="_blank" rel="noopener noreferrer">Query DSL</a>.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001945472646__section383919455212"><h4 class="sectiontitle">DSL Usage Example</h4><p id="EN-US_TOPIC_0000001945472646__p1059184122211">Compile the request content in JSON format on the Dev Tools page of Kibana and execute the search request.</p>
|
||||
<p id="EN-US_TOPIC_0000001945472646__p1663415301464">For example, run the following command to retrieve all documents in the <strong id="EN-US_TOPIC_0000001945472646__b241613581863">test</strong> index:</p>
|
||||
<div class="codecoloring" codetype="Json" id="EN-US_TOPIC_0000001945472646__en-us_topic_0000001268594557_screen158809477411"><div class="highlight"><table class="highlighttable"><tr><td class="linenos"><div class="linenodiv"><pre><span class="normal">1</span>
|
||||
<span class="normal">2</span>
|
||||
<span class="normal">3</span>
|
||||
<span class="normal">4</span>
|
||||
<span class="normal">5</span>
|
||||
<span class="normal">6</span></pre></div></td><td class="code"><div><pre><span></span><span class="err">GET</span><span class="w"> </span><span class="err">/</span><span class="kc">test</span><span class="err">/_search</span>
|
||||
<span class="p">{</span>
|
||||
<span class="w"> </span><span class="nt">"query"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span>
|
||||
<span class="w"> </span><span class="nt">"match_all"</span><span class="p">:</span><span class="w"> </span><span class="p">{}</span>
|
||||
<span class="w"> </span><span class="p">}</span>
|
||||
<span class="p">}</span>
|
||||
</pre></div></td></tr></table></div>
|
||||
</div>
|
||||
<p id="EN-US_TOPIC_0000001945472646__p1678182553119">The search result is also in JSON format.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001945472646__section4944125615312"><h4 class="sectiontitle">Common DSL Query Statements</h4><ul id="EN-US_TOPIC_0000001945472646__ul186240196385"><li id="EN-US_TOPIC_0000001945472646__li946616485469">Sets the query filters, which is equivalent to <strong id="EN-US_TOPIC_0000001945472646__b12501514493">where</strong> in the SQL language.<p id="EN-US_TOPIC_0000001945472646__p1152724914464">In the command below, there is no index filter in front of <span class="parmvalue" id="EN-US_TOPIC_0000001945472646__parmvalue6305154474618"><b>_search</b></span>, so all indexes are queried. A bool query allows you to combine multiple search queries with boolean conditions. <strong id="EN-US_TOPIC_0000001945472646__b140175018129">filter</strong> forcibly filters documents whose <span class="parmname" id="EN-US_TOPIC_0000001945472646__parmname1430574474617"><b>status</b></span> field is <span class="parmvalue" id="EN-US_TOPIC_0000001945472646__parmvalue830594412464"><b>published</b></span> and <span class="parmname" id="EN-US_TOPIC_0000001945472646__parmname43050446465"><b>publish_date</b></span> is later than <span class="parmvalue" id="EN-US_TOPIC_0000001945472646__parmvalue630510447466"><b>2015-01-01</b></span>. <strong id="EN-US_TOPIC_0000001945472646__b1356974913149">must</strong> specifies that both <span class="parmname" id="EN-US_TOPIC_0000001945472646__parmname1930534412469"><b>title</b></span> and <span class="parmname" id="EN-US_TOPIC_0000001945472646__parmname17306744104611"><b>content</b></span> must include <span class="parmvalue" id="EN-US_TOPIC_0000001945472646__parmvalue2306194410468"><b>Search</b></span>.</p>
|
||||
<div class="note" id="EN-US_TOPIC_0000001945472646__note196387513488"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001945472646__p107541385475">The difference between <strong id="EN-US_TOPIC_0000001945472646__b859423171615">must</strong> and <strong id="EN-US_TOPIC_0000001945472646__b26001369161">filter</strong> is that <strong id="EN-US_TOPIC_0000001945472646__b01054175163">filter</strong> is equivalent to <strong id="EN-US_TOPIC_0000001945472646__b4121203013164">where</strong> in SQL but its results are not used for scoring. The <strong id="EN-US_TOPIC_0000001945472646__b17395121471810">must</strong> field is also a mandatory filter criteria, but the matching documents are scored based on relevance. The most relevant documents are displayed at the top.</p>
|
||||
</div></div>
|
||||
<pre class="screen" id="EN-US_TOPIC_0000001945472646__screen12896143643812">GET /_search
|
||||
{
|
||||
"query": {
|
||||
"bool": {
|
||||
"must": [
|
||||
{
|
||||
"match": {
|
||||
"title": "Search"
|
||||
}
|
||||
},
|
||||
{
|
||||
"match": {
|
||||
"content": "search"
|
||||
}
|
||||
}
|
||||
],
|
||||
"filter": [
|
||||
{
|
||||
"term": {
|
||||
"status": "published"
|
||||
}
|
||||
},
|
||||
{
|
||||
"range": {
|
||||
"publish_date": {
|
||||
"gte": "2015-01-01"
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
}</pre>
|
||||
</li><li id="EN-US_TOPIC_0000001945472646__li169821932163813"><strong id="EN-US_TOPIC_0000001945472646__b2820579225">Aggregations</strong> are similar to <strong id="EN-US_TOPIC_0000001945472646__b176144422220">Group by</strong> in SQL.<p id="EN-US_TOPIC_0000001945472646__p1318110279496">An aggregation summarizes your data as metrics, statistics, or other analytics. In the example below, the results are aggregated based on the title field in the <strong id="EN-US_TOPIC_0000001945472646__b08541525102416">test</strong> index. If <strong id="EN-US_TOPIC_0000001945472646__b3520942162416">title</strong> is of the text (including keyword) type, use <span class="parmvalue" id="EN-US_TOPIC_0000001945472646__parmvalue9835747105018"><b>title.keyword</b></span> for aggregation. By default, a cluster cannot directly aggregate data of the text type. <strong id="EN-US_TOPIC_0000001945472646__b814692272516">titles</strong> is only an example name of the aggregation. You can name the aggregation <strong id="EN-US_TOPIC_0000001945472646__b8330101772618">titleaggs</strong> instead.</p>
|
||||
<pre class="screen" id="EN-US_TOPIC_0000001945472646__screen437744944813">GET /test/_search
|
||||
{
|
||||
"aggs": {
|
||||
"titles": {
|
||||
"terms": {
|
||||
"field": "title.keyword"
|
||||
}
|
||||
}
|
||||
}
|
||||
}</pre>
|
||||
<p id="EN-US_TOPIC_0000001945472646__p51815276497">The example above for query aggregation includes all documents in the <strong id="EN-US_TOPIC_0000001945472646__b9137259152610">test</strong> index. That is, <strong id="EN-US_TOPIC_0000001945472646__b162584202276">match_all</strong> is used. You can set search criteria to narrow the scope of the aggregation to specific documents.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0006.html">Searching Data in an Elasticsearch Cluster</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
195
docs/css/umn/css_01_0008.html
Normal file
195
docs/css/umn/css_01_0008.html
Normal file
File diff suppressed because it is too large
Load Diff
@ -1,22 +1,22 @@
|
||||
<a name="css_01_0009"></a><a name="css_01_0009"></a>
|
||||
<a name="EN-US_TOPIC_0000001965416761"></a><a name="EN-US_TOPIC_0000001965416761"></a>
|
||||
|
||||
<h1 class="topictitle1">Managing Elasticsearch Clusters</h1>
|
||||
<div id="body1503460464688"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0415.html">Viewing Elasticsearch Cluster Information</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0185.html">Viewing Elasticsearch Cluster Information</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0417.html">Creating Users for an Elasticsearch Cluster and Granting Cluster Access</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0109.html">Creating Users for an Elasticsearch Cluster and Granting Cluster Access</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0075.html">Setting Tags for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0080.html">Configuring Default Parameters in the .yml Configuration File of an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0058.html">Binding an Elasticsearch Cluster to an Enterprise Project</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0058.html">Associating an Elasticsearch Cluster with an Enterprise Project</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0418.html">Changing the Node Specifications of an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0245.html">Changing the Node Specifications and Storage Type of an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0156.html">Replacing Specified Nodes for an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0156.html">Replacing a Specified Node for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0158.html">Changing the Security Mode of an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
|
||||
@ -1,18 +1,20 @@
|
||||
<a name="css_01_0411"></a><a name="css_01_0411"></a>
|
||||
<a name="EN-US_TOPIC_0000001972543281"></a><a name="EN-US_TOPIC_0000001972543281"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Configuring Networking for an Elasticsearch Cluster</h1>
|
||||
|
||||
<div id="body0000001972543281"><p id="css_01_0411__p8060118"></p>
|
||||
<div id="body0000001972543281"><p id="EN-US_TOPIC_0000001972543281__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0279.html">Configuring Routes for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0076.html">Configuring Public Network Access for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0412.html">Configuring VPC Endpoint Service for an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0082.html">Configuring VPC Endpoints for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0413.html">Configuring a Dedicated Load Balancer for an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0181.html">Configuring a Dedicated Load Balancer for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
<a name="css_01_0414"></a><a name="css_01_0414"></a>
|
||||
<a name="EN-US_TOPIC_0000001945362244"></a><a name="EN-US_TOPIC_0000001945362244"></a>
|
||||
|
||||
<h1 class="topictitle1">Scaling an Elasticsearch Cluster</h1>
|
||||
<div id="body0000001945362244"><p id="css_01_0414__p8060118"></p>
|
||||
<div id="body0000001945362244"><p id="EN-US_TOPIC_0000001945362244__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0151.html">Scaling Out an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0151.html">Scaling Out/Up an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0153.html">Scaling In an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0153.html">Scaling In/Down an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
112
docs/css/umn/css_01_0013.html
Normal file
112
docs/css/umn/css_01_0013.html
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,10 +1,10 @@
|
||||
<a name="css_01_0015"></a><a name="css_01_0015"></a>
|
||||
<a name="EN-US_TOPIC_0000001938377864"></a><a name="EN-US_TOPIC_0000001938377864"></a>
|
||||
|
||||
<h1 class="topictitle1">Deleting an Elasticsearch Cluster</h1>
|
||||
<div id="body1503460464688"><p id="css_01_0015__en-us_topic_0000001268594553_p1219762501">You can delete clusters that you no longer need.</p>
|
||||
<div class="section" id="css_01_0015__section6834143742917"><h4 class="sectiontitle">Constraints</h4><ul id="css_01_0015__en-us_topic_0000001268594553_ul3613184185219"><li id="css_01_0015__en-us_topic_0000001268594553_li1461319413523">Deleting a cluster will clear all its data. Exercise caution.</li><li id="css_01_0015__en-us_topic_0000001268594553_li1980118281592">A cluster that has no snapshots created for it cannot be restored once it is deleted. The snapshots of the cluster stored in OBS, if any, will not be deleted with the cluster. You can restore a deleted cluster using its snapshots stored in the OBS bucket.</li><li id="css_01_0015__li9728758142317">For a cluster for which the VPCEP service has been enabled, deleting the cluster may not delete the VPC endpoint associated with the cluster if the current account does not have the necessary VPCEP permissions. For details about the VPCEP permissions, see section "Permissions" in <em id="css_01_0015__i64101029124318">VPC Endpoint User Guide</em>.</li></ul>
|
||||
<div id="body1503460464688"><p id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_p1219762501">You can delete clusters that you no longer need.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001938377864__section6834143742917"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_ul3613184185219"><li id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_li1461319413523">Deleting a cluster will delete all its data. Any data that has not been backed up will be permanently lost. Exercise caution.</li><li id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_li1980118281592">A cluster that has no snapshots created for it cannot be restored once it is deleted. The snapshots of the cluster stored in OBS, if any, will not be deleted with the cluster. You can restore a deleted cluster using its snapshots stored in the OBS bucket.</li><li id="EN-US_TOPIC_0000001938377864__li9728758142317">For a cluster for which the VPCEP service has been enabled, deleting the cluster may not delete the VPC endpoint associated with the cluster if the current account does not have the necessary VPCEP permissions. For details about the VPCEP permissions, see section "Permissions" in <em id="EN-US_TOPIC_0000001938377864__i205357402242">VPC Endpoint User Guide</em>.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="css_01_0015__en-us_topic_0000001268594553_section175418313575"><h4 class="sectiontitle">Deleting a Cluster</h4><ol id="css_01_0015__en-us_topic_0000001268594553_ol20161122142614"><li id="css_01_0015__en-us_topic_0000001268594553_li11622242616">Log in to the <span id="css_01_0015__text68166500111614">CSS</span> management console.</li><li id="css_01_0015__en-us_topic_0000001268594553_li1180413314595">In the navigation tree on the left, select a cluster type. The cluster list page is displayed.</li><li id="css_01_0015__en-us_topic_0000001268594553_li9160224260">Locate the target cluster and click <strong id="css_01_0015__en-us_topic_0000001268594553_b3863134022819">More</strong> > <strong id="css_01_0015__en-us_topic_0000001268594553_b4464114252818">Delete</strong> in the <strong id="css_01_0015__en-us_topic_0000001268594553_b1698111072819">Operation</strong> column.</li><li id="css_01_0015__en-us_topic_0000001268594553_li21622222619">In the displayed dialog box, manually type in <strong id="css_01_0015__b12173151714287">DELETE</strong>, and click <span class="uicontrol" id="css_01_0015__uicontrol3955167898125"><b>OK</b></span>.</li></ol>
|
||||
<div class="section" id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_section175418313575"><h4 class="sectiontitle">Deleting a Cluster</h4><ol id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_ol20161122142614"><li id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_li11622242616"><span id="EN-US_TOPIC_0000001938377864__ph4222205142920">Log in to the CSS management console.</span></li><li id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001938377912_li448417016810">In the navigation pane on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001938377864__uicontrol100417808485143"><b>Clusters > Elasticsearch</b></span>.</li><li id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001938377912_en-us_topic_0000001223594400_li163277114258">In the cluster list, find the target cluster, and choose <span class="uicontrol" id="EN-US_TOPIC_0000001938377864__uicontrol197882174115"><b>More > Delete</b></span> in the <strong id="EN-US_TOPIC_0000001938377864__b378861124114">Operation</strong> column.</li><li id="EN-US_TOPIC_0000001938377864__en-us_topic_0000001268594553_li21622222619">In the displayed dialog box, manually type in <strong id="EN-US_TOPIC_0000001938377864__b12173151714287">DELETE</strong>, and click <span class="uicontrol" id="EN-US_TOPIC_0000001938377864__uicontrol3955167898125"><b>OK</b></span>.</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -1,22 +1,22 @@
|
||||
<a name="css_01_0422"></a><a name="css_01_0422"></a>
|
||||
<a name="EN-US_TOPIC_0000001945364736"></a><a name="EN-US_TOPIC_0000001945364736"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Elasticsearch Cluster Monitoring and Log Management</h1>
|
||||
|
||||
<div id="body0000001945364736"><p id="css_01_0422__p8060118"></p>
|
||||
<div id="body0000001945364736"><p id="EN-US_TOPIC_0000001945364736__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0423.html">Elasticsearch Cluster Monitoring Metrics</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0025.html">Elasticsearch Cluster Monitoring Metrics</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0426.html">Configuring Elasticsearch Cluster Monitoring</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0026.html">Configuring Elasticsearch Cluster Monitoring</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0223.html">Setting Alarm Alerting via SMN for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0429.html">Synchronizing Elasticsearch Alerts to Prometheus</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0219.html">Synchronizing Elasticsearch Alerts to Prometheus</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0077.html">Querying and Managing Elasticsearch Cluster Logs</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0077.html">Managing Elasticsearch Cluster Logs</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
165
docs/css/umn/css_01_0017.html
Normal file
165
docs/css/umn/css_01_0017.html
Normal file
File diff suppressed because it is too large
Load Diff
55
docs/css/umn/css_01_0019.html
Normal file
55
docs/css/umn/css_01_0019.html
Normal file
@ -0,0 +1,55 @@
|
||||
<a name="EN-US_TOPIC_0000002333390490"></a><a name="EN-US_TOPIC_0000002333390490"></a>
|
||||
|
||||
<h1 class="topictitle1">Importing Vector Data</h1>
|
||||
<div id="body0000002333390490"><p id="EN-US_TOPIC_0000002333390490__p015512713407">Importing vector data is the process of ingesting data to the CSS vector database. When writing vector data to a vector index, you need to specify the vector field (for example, <strong id="EN-US_TOPIC_0000002333390490__b788950244113121">my_vector</strong>) and the corresponding data format. The CSS vector database supports two common formats: floating-point arrays and Base64.</p>
|
||||
<ul id="EN-US_TOPIC_0000002333390490__ul12570134934217"><li id="EN-US_TOPIC_0000002333390490__li1857084917423">Floating-point arrays: transmitting readable arrays directly.</li><li id="EN-US_TOPIC_0000002333390490__li11570124910425">Base64: encoding vectors (little-endian byte order) into character strings to reduce network transmission overhead and improve efficiency in handling high-dimensional/binary vectors.</li></ul>
|
||||
<p id="EN-US_TOPIC_0000002333390490__p77872510388">Choose a format based on the characteristics of your data. Also, choose an appropriate data importing method.</p>
|
||||
<ul id="EN-US_TOPIC_0000002333390490__ul11613101718129"><li id="EN-US_TOPIC_0000002333390490__li136131817181217">Importing a single record: Use for small-scale applications or testing.</li><li id="EN-US_TOPIC_0000002333390490__li15613191771215">Bulk import: Use for large-scale applications, where write requests are merged to reduce network overhead.</li></ul>
|
||||
<div class="section" id="EN-US_TOPIC_0000002333390490__section6903614172518"><h4 class="sectiontitle">Constraints</h4><ul id="EN-US_TOPIC_0000002333390490__ul187041447152514"><li id="EN-US_TOPIC_0000002333390490__li107049478251">Ensure that the vector field names and vector dimensions are consistent with those defined for the index.</li><li id="EN-US_TOPIC_0000002333390490__li8704164792512">Base64 encoding must use the little-endian byte order. Otherwise, parsing errors may occur.</li><li id="EN-US_TOPIC_0000002333390490__li17043472253">In the case of bulk imports, you are advised to submit 100 to 1000 records per request. This balances throughput and memory overhead.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000002333390490__section112382921217"><h4 class="sectiontitle">Importing a Single Record</h4><ul id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_ul1447115404176"><li id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_li154711140131720">Floating-point array<pre class="screen" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_screen187218394184">POST <i><span class="varname" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_varname122034371812">my_index</span></i>/_doc
|
||||
{
|
||||
"my_vector": [1.0, 2.0]
|
||||
}</pre>
|
||||
</li><li id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_li1747144071720">Base64<pre class="screen" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_screen5659104710189">POST <i><span class="varname" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_varname1197011507187">my_index</span></i>/_doc
|
||||
{
|
||||
"my_vector": "AACAPwAAAEA="
|
||||
}</pre>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000002333390490__section1759833513124"><h4 class="sectiontitle">Bulk Import</h4><ul id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_ul11956134511195"><li id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_li169561945101915">Floating-point array<pre class="screen" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_screen1786216364208">POST <i><span class="varname" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_varname119601143172014">my_index</span></i>/_bulk
|
||||
{"index": {}}
|
||||
{"my_vector": [1.0, 2.0], "my_label": "red"}
|
||||
{"index": {}}
|
||||
{"my_vector": [2.0, 2.0], "my_label": "green"}
|
||||
{"index": {}}
|
||||
{"my_vector": [2.0, 3.0], "my_label": "red"}</pre>
|
||||
</li><li id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_li6956134511920">Base64<pre class="screen" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_screen6310134384817">POST <i><span class="varname" id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_varname632816518231">my_index</span></i>/_bulk
|
||||
{"index":{}}
|
||||
{"my_vector":"AACAPwAAAEA=", "my_label": "red"}
|
||||
{"index":{}}
|
||||
{"my_vector":"AAAAQAAAAEA=", "my_label": "green"}
|
||||
{"index":{}}
|
||||
{"my_vector":"AAAAQAAAQEA=", "my_label": "red"}</pre>
|
||||
</li></ul>
|
||||
<p id="EN-US_TOPIC_0000002333390490__en-us_topic_0000002353678449_p73291054143716">For details about how to use the Bulk API, see <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/docs-bulk.html" target="_blank" rel="noopener noreferrer">Bulk API</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000002333390490__section164656265118"><a name="EN-US_TOPIC_0000002333390490__section164656265118"></a><a name="section164656265118"></a><h4 class="sectiontitle">(Optional) Post-processing after Data Ingestion: Offline Index Building</h4><div class="warning" id="EN-US_TOPIC_0000002333390490__note9426454103716"><span class="warningtitle"><img src="public_sys-resources/warning_3.0-en-us.png"> </span><div class="warningbody"><ul id="EN-US_TOPIC_0000002333390490__ul1286142123818"><li id="EN-US_TOPIC_0000002333390490__li8286725386">Use offline index creation via an API only when real-time data is not required or crucial and the cluster version is OpenSearch 2.19.0.</li><li id="EN-US_TOPIC_0000002333390490__li1075867174411">If lazy_indexing is enabled, offline index building must be performed after data ingestion. Otherwise, the system will return error code 500 for standard vector query, with the error message "Load native index failed exception." To solve this problem, perform offline index building before vectors queries.</li></ul>
|
||||
</div></div>
|
||||
<p id="EN-US_TOPIC_0000002333390490__p1529111251215">OpenSearch uses an LSM (Log-Structured Merge) tree-like model to accelerate write operations. As data is continuously written in and updated, numerous small index segments are generated and later merged via a backend task to enhance query performance. As vector indexing is computationally intensive, frequent index merging while vector data is being written in consumes significant CPU resources. Therefore, where real-time data is not crucial, it is advisable to set <strong id="EN-US_TOPIC_0000002333390490__b114183182411171">lazy_indexing</strong> to <strong id="EN-US_TOPIC_0000002333390490__b174512243911171">true</strong> for vector fields. This allows a final vector index to be created via a non-real time API after all data has been written in. This approach significantly reduces index merges, thereby improving overall write and index merging performance.</p>
|
||||
<p id="EN-US_TOPIC_0000002333390490__p031561711139">Offline index building consists of two steps:</p>
|
||||
<ol id="EN-US_TOPIC_0000002333390490__ol478183191311"><li id="EN-US_TOPIC_0000002333390490__li87811731131318">Merge index segments.</li><li id="EN-US_TOPIC_0000002333390490__li478115315135">Create the final vector index based on the final index segments.</li></ol>
|
||||
<p id="EN-US_TOPIC_0000002333390490__p1367412481662">The API used for offline index building is as follows:</p>
|
||||
<pre class="screen" id="EN-US_TOPIC_0000002333390490__screen1367414483612">POST _vector/indexing/{index_name}
|
||||
{
|
||||
"field": "{field_name}"
|
||||
}</pre>
|
||||
<p id="EN-US_TOPIC_0000002333390490__p96742481061">where, {index_name} indicates the name of the index to create. {field_name} indicates the name of the vector field for which <strong id="EN-US_TOPIC_0000002333390490__b192479830911171">lazy_indexing</strong> has been set to <strong id="EN-US_TOPIC_0000002333390490__b212160817111171">true</strong>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0101.html">Configuring Vector Search for OpenSearch Clusters</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
185
docs/css/umn/css_01_0021.html
Normal file
185
docs/css/umn/css_01_0021.html
Normal file
File diff suppressed because it is too large
Load Diff
130
docs/css/umn/css_01_0022.html
Normal file
130
docs/css/umn/css_01_0022.html
Normal file
File diff suppressed because it is too large
Load Diff
51
docs/css/umn/css_01_0023.html
Normal file
51
docs/css/umn/css_01_0023.html
Normal file
@ -0,0 +1,51 @@
|
||||
<a name="EN-US_TOPIC_0000001987223073"></a><a name="EN-US_TOPIC_0000001987223073"></a>
|
||||
|
||||
<h1 class="topictitle1">Elasticsearch Cluster Monitoring Metrics Supported by the Kernel</h1>
|
||||
<div id="body0000001987223073">
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001987223073__table9434132712317" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Elasticsearch cluster monitoring metrics supported by the kernel</caption><thead align="left"><tr id="EN-US_TOPIC_0000001987223073__row4434527102316"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.1.2.5.1.1"><p id="EN-US_TOPIC_0000001987223073__p11434172716231">Metric</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="40%" id="mcps1.3.1.2.5.1.2"><p id="EN-US_TOPIC_0000001987223073__p29081437172318">Description</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.1.2.5.1.3"><p id="EN-US_TOPIC_0000001987223073__p10434182720238">Supported Cluster Version</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.1.2.5.1.4"><p id="EN-US_TOPIC_0000001987223073__p2434927122310">Details</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001987223073__row1943412715235"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.1 "><p id="EN-US_TOPIC_0000001987223073__p10434122752316">P99 latency for search requests</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.1.2.5.1.2 "><p id="EN-US_TOPIC_0000001987223073__en-us_topic_0000001938377876_p17345101319367">Open-source Elasticsearch provides only the average latency metric when monitoring responses to search requests. This may not accurately reflect the actual search performance of a cluster. To improve on this, the P99 latency metric is added in CSS to monitor the 99th percentile latency of each cluster.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.3 "><p id="EN-US_TOPIC_0000001987223073__p143531918718">Elasticsearch 7.6.2, Elasticsearch 7.10.2</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.4 "><p id="EN-US_TOPIC_0000001987223073__p1434192702317"><a href="css_01_0177.html#EN-US_TOPIC_0000001938377876__section7236204762019">Monitoring P99 Latency</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001987223073__row12434132792314"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.1 "><p id="EN-US_TOPIC_0000001987223073__p1743482710239">HTTP status codes for the cluster</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.1.2.5.1.2 "><p id="EN-US_TOPIC_0000001987223073__en-us_topic_0000001938377876_p5549314412">When you access Elasticsearch through HTTP, you receive HTTP status codes in response to your requests. The native open-source Elasticsearch does not collect statistics on these status codes. To improve on this, HTTP status code monitoring is added in CSS, allowing you to monitor HTTP status codes and get a sense of how the service is running.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.3 "><p id="EN-US_TOPIC_0000001987223073__p1576663611254">Elasticsearch 7.6.2, Elasticsearch 7.10.2</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.4 "><p id="EN-US_TOPIC_0000001987223073__p843422782312"><a href="css_01_0177.html#EN-US_TOPIC_0000001938377876__section1367052018215">Monitoring HTTP Status Codes</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001987223073__row16761121311719"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.1 "><p id="EN-US_TOPIC_0000001987223073__p177625131179">Cluster indexes</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.1.2.5.1.2 "><p id="EN-US_TOPIC_0000001987223073__p19667195121518">Index monitoring helps to monitor the index usage and trends of a cluster, allowing users to handle potential risks in a timely manner to ensure cluster reliability. Index usage statistics are collected and stored in the cluster's monitoring index (index name: <span class="parmvalue" id="EN-US_TOPIC_0000001987223073__en-us_topic_0000001938218528_parmvalue1432511499153"><b>monitoring-eye-css-[yyyy-mm-dd]</b></span>. By default, these monitoring indexes are retained for one week before being permanently deleted upon expiration.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.3 "><p id="EN-US_TOPIC_0000001987223073__p1356383611710">Elasticsearch 7.6.2, Elasticsearch 7.10.2</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.1.2.5.1.4 "><p id="EN-US_TOPIC_0000001987223073__p576261311176"><a href="css_01_0135.html">Configuring Index Monitoring for an Elasticsearch Cluster</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0025.html">Elasticsearch Cluster Monitoring Metrics</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,21 +1,21 @@
|
||||
<a name="css_01_0423"></a><a name="css_01_0423"></a>
|
||||
<a name="EN-US_TOPIC_0000001953303642"></a><a name="EN-US_TOPIC_0000001953303642"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Elasticsearch Cluster Monitoring Metrics</h1>
|
||||
|
||||
<div id="body0000001953303642"><p id="css_01_0423__p8060118"></p>
|
||||
<div id="body0000001953303642"><p id="EN-US_TOPIC_0000001953303642__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0424.html">Monitoring Metrics for Elasticsearch Clusters in Cloud Eye</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0042.html">Monitoring Metrics for Elasticsearch Clusters in Cloud Eye</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0425.html">Elasticsearch Cluster Monitoring Metrics Supported by the Kernel</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0023.html">Elasticsearch Cluster Monitoring Metrics Supported by the Kernel</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0422.html">Elasticsearch Cluster Monitoring and Log Management</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0016.html">Elasticsearch Cluster Monitoring and Log Management</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -1,20 +1,20 @@
|
||||
<a name="css_01_0426"></a><a name="css_01_0426"></a>
|
||||
<a name="EN-US_TOPIC_0000001987382921"></a><a name="EN-US_TOPIC_0000001987382921"></a>
|
||||
|
||||
<h1 class="topictitle1">Configuring Elasticsearch Cluster Monitoring</h1>
|
||||
<div id="body0000001987382921"><p id="css_01_0426__p8060118"></p>
|
||||
<div id="body0000001987382921"><p id="EN-US_TOPIC_0000001987382921__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0155.html">Using Cloud Eye to Monitor Elasticsearch Clusters</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0427.html">Configuring Kernel Monitoring for an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0177.html">Configuring Kernel Monitoring for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0428.html">Configuring Index Monitoring for an Elasticsearch Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0135.html">Configuring Index Monitoring for an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0422.html">Elasticsearch Cluster Monitoring and Log Management</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0016.html">Elasticsearch Cluster Monitoring and Log Management</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
128
docs/css/umn/css_01_0027.html
Normal file
128
docs/css/umn/css_01_0027.html
Normal file
File diff suppressed because it is too large
Load Diff
19
docs/css/umn/css_01_0028.html
Normal file
19
docs/css/umn/css_01_0028.html
Normal file
@ -0,0 +1,19 @@
|
||||
<a name="EN-US_TOPIC_0000001991840137"></a><a name="EN-US_TOPIC_0000001991840137"></a>
|
||||
|
||||
<h1 class="topictitle1">OpenSearch Cluster Planning Suggestions</h1>
|
||||
<div id="body0000001991840137"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0088.html">Planning Cluster AZs and HA</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0092.html">Planning the Cluster Version and Security Mode</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0094.html">Planning Node Types and Specifications</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0273.html">Using OpenSearch for Data Search</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
21
docs/css/umn/css_01_0029.html
Normal file
21
docs/css/umn/css_01_0029.html
Normal file
@ -0,0 +1,21 @@
|
||||
<a name="EN-US_TOPIC_0000001992205769"></a><a name="EN-US_TOPIC_0000001992205769"></a>
|
||||
|
||||
<h1 class="topictitle1">Logging In to an OpenSearch Cluster Through Cerebro</h1>
|
||||
<div id="body0000001992205769"><p id="EN-US_TOPIC_0000001992205769__p8827747104514">Cerebro is an open-source Elasticsearch web admin tool, designed for real-time monitoring and efficient cluster operations. Cerebro works for OpenSearch just as well. In CSS, Cerebro is pre-built for each OpenSearch cluster. You can start Cerebro with one click, without installing anything. Cerebro allows you to quickly check a cluster's health status, node distribution, and index details. For routine O&M tasks, including shard adjustment, index management, and performance monitoring, we recommend using Cerebro. Its intuitive cluster topology views and comprehensive management features streamline O&M workflows, reducing complexity while improving efficiency. Cerebro is suitable for different roles, including developers, O&M teams, and data analysts.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_section138869481791"><h4 class="sectiontitle">Accessing a Cluster Through Cerebro on the CSS Console</h4><p id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_p1611313396388">The OpenSearch clusters created in CSS provide a built-in Cerebro component, using which you can quickly access these clusters.</p>
|
||||
<ol id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_ol8123172192918"><li id="EN-US_TOPIC_0000001992205769__li111185453113"><span id="EN-US_TOPIC_0000001992205769__ph134648105316">Log in to the CSS management console.</span></li><li id="EN-US_TOPIC_0000001992205769__li1711804571114">In the navigation pane on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001992205769__uicontrol63874463576"><b>Clusters > OpenSearch</b></span>.</li><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_li7655153392911">Find the target cluster, and choose <strong id="EN-US_TOPIC_0000001992205769__b163315221443">More</strong> > <strong id="EN-US_TOPIC_0000001992205769__b733152210420">Cerebro</strong> in the <strong id="EN-US_TOPIC_0000001992205769__b173312222416">Operation</strong> column. The Cerebro login page is displayed.<ul id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_ul75232028195712"><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_li20523122816570">Non-security cluster: Click the cluster name on the Cerebro login page to go to the Cerebro console.</li><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_li134787055820">Security cluster: Click the cluster name on the Cerebro login page, enter the username and password, and click <span class="uicontrol" id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_uicontrol15959165212110"><b>Authenticate</b></span> to go to the Cerebro console. The default username is <strong id="EN-US_TOPIC_0000001992205769__b7118503411">admin</strong> and the password is the one specified during cluster creation.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_en-us_topic_0000001961178825_en-us_topic_0000001528379305_en-us_topic_0000001428595166_li0655183310296">After the login is successful, you can access clusters through Cerebro.</li></ol>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_section1335265473715"><h4 class="sectiontitle">Accessing a Cluster Using an In-House Built Cerebro</h4><div class="caution" id="EN-US_TOPIC_0000001992205769__note168981240141319"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><p id="EN-US_TOPIC_0000001992205769__p7590154189">When using in-house built Cerebro to access a cluster, make sure the network between them is connected.</p>
|
||||
</div></div>
|
||||
<ol id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_ol038919424422"><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_li4389174219428">Obtain the cluster access address. For details about how to obtain the cluster access address for different network configurations, see <a href="css_01_0289.html#EN-US_TOPIC_0000001992165561__en-us_topic_0000001975823337_section855085010198">Network Configuration</a>.</li><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_li1031865316452">Start Cerebro, and enter the cluster access address.<ul id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_ul61032508382"><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_li1910365016383">For a cluster in security mode, enter https://<em id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_i2761648184412">access address</em>:9200.<p id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_p55091117194818">To log in to a cluster in security mode, you need to provide a username and password.</p>
|
||||
</li><li id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_li410411505384">For a cluster in non-security mode, enter http://<em id="EN-US_TOPIC_0000001992205769__en-us_topic_0000001972416121_i13480434467">access address</em>:9200.</li></ul>
|
||||
</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0288.html">Accessing an OpenSearch Cluster</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
79
docs/css/umn/css_01_0030.html
Normal file
79
docs/css/umn/css_01_0030.html
Normal file
@ -0,0 +1,79 @@
|
||||
<a name="EN-US_TOPIC_0000001992165565"></a><a name="EN-US_TOPIC_0000001992165565"></a>
|
||||
|
||||
<h1 class="topictitle1">Accessing an OpenSearch Cluster Using cURL Commands</h1>
|
||||
<div id="body0000001992165565"><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_p128983357017">Open-source OpenSearch provides a series of RESTful APIs. You can run cURL commands to access these APIs using tools such as OpenSearch Dashboards and Postman. This topic describes how to run cURL commands to access an OpenSearch cluster.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_section346464820183"><h4 class="sectiontitle">Prerequisites</h4><ul id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_ul10447145616424"><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li1044745604219">The target CSS OpenSearch cluster is available.</li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li1344713562420">An ECS has been created, and it is in the same VPC and security group as the CSS cluster.<ul id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_ul612451510168"><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_li4839213171619">If they are not in the same security group, modify the ECS security group, or configure its inbound and outbound rules to allow all access from the cluster. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/ecs/en-us_topic_0030878383.html" target="_blank" rel="noopener noreferrer">Configuring Security Group Rules</a>.</li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_li158392130165">For details about how to use an ECS, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/ecs/en-us_topic_0092494193.html" target="_blank" rel="noopener noreferrer">Creating and Logging In to a Linux ECS</a>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_section14909125211516"><h4 class="sectiontitle">Accessing a Cluster</h4><ol id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_ol1651417167525"><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li11618134413130">Obtain the private network address of the cluster. It is used to access the cluster.<p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_p152184916443"><a name="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li11618134413130"></a><a name="en-us_topic_0000001945217682_en-us_topic_0000001961178833_li11618134413130"></a>This topic uses a private IP address as an example to describe how to access a cluster. The cluster access address varies depending on the network configurations used. For details, see <a href="css_01_0190.html#EN-US_TOPIC_0000001975823337__section855085010198">Network Configuration</a>.</p>
|
||||
<ol type="a" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_ol1742819417471"><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_li1515612820249"><span id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_ph115718818245">Log in to the CSS management console.</span></li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_li215708162415">In the navigation pane on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_uicontrol722453846"><b>Clusters > OpenSearch</b></span>.</li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_li815717822419">In the cluster list, obtain the target cluster's private IP address from the <strong id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_b11512044152320">Private IP Address</strong> column. Generally, the IP address format is <em id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_i815104492319"><host></em>:<em id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_i6151344152317"><port></em> or <em id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_i1115144452317"><host></em>:<em id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_i14151144412237"><port></em>,<em id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_i12151194432312"><host></em>:<em id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_i16151444142315"><port></em>.<p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_p615720817246">If the cluster has only one node, the IP address and port number of this single node are displayed, for example, <span class="parmvalue" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_parmvalue1950910310013"><b>10.62.179.32:9200</b></span>. If the cluster has multiple nodes and all of them are data nodes, the IP addresses and port numbers of all these nodes are displayed; if some of them are client nodes, only the IP addresses and port numbers of these client nodes are displayed; for example, <span class="parmvalue" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000002338102386_parmvalue250963305"><b>10.62.179.32:9200,10.62.179.33:9200</b></span>.</p>
|
||||
</li></ol>
|
||||
</li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li13876151991418">Run one of the following commands on the ECS to access the cluster. The access command varies depending on the security mode of the cluster.<ul id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_ul48942022152318"><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li789411220236">For a cluster with the security mode disabled:<pre class="screen" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_screen12262625142419">curl "http://<host>:<port>"</pre>
|
||||
</li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li10172522142412">For a security-mode cluster that uses HTTP:<pre class="screen" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_screen921113585271">curl -u <user>:<password> "http://<host>:<port>"</pre>
|
||||
</li><li id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_li1984395519251">For a security-mode cluster that uses HTTPS:<pre class="screen" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_screen7365674284">curl -u <user>:<password> -k "https://<host>:<port>"</pre>
|
||||
</li></ul>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_table111741414338" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Variables</caption><thead align="left"><tr id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_row91731411337"><th align="left" class="cellrowborder" valign="top" width="23.7%" id="mcps1.3.3.2.2.2.2.3.1.1"><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p14171714153311">Variable</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="76.3%" id="mcps1.3.3.2.2.2.2.3.1.2"><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p417131412333">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_row192601805113"><td class="cellrowborder" valign="top" width="23.7%" headers="mcps1.3.3.2.2.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p19261218155110"><host></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.3%" headers="mcps1.3.3.2.2.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p42611819514">IP address of each node in the cluster. If the cluster contains multiple nodes, there will be multiple IP addresses. You can use any of them.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_row73721818175113"><td class="cellrowborder" valign="top" width="23.7%" headers="mcps1.3.3.2.2.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p133723186514"><port></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.3%" headers="mcps1.3.3.2.2.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p16372318165118">Port number for accessing a cluster node. Generally, the port number is 9200.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_row131711473319"><td class="cellrowborder" valign="top" width="23.7%" headers="mcps1.3.3.2.2.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p4171147336"><user></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.3%" headers="mcps1.3.3.2.2.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p111791417336">Username for accessing the cluster.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_row161711420338"><td class="cellrowborder" valign="top" width="23.7%" headers="mcps1.3.3.2.2.2.2.3.1.1 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p17171149336"><password></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.3%" headers="mcps1.3.3.2.2.2.2.3.1.2 "><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p11713147339">Password of the user.</p>
|
||||
<p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p12911206191917">If the password contains special characters, enclose the username and password in single quotation marks, for example, <span class="parmvalue" id="EN-US_TOPIC_0000001992165565__parmvalue8171551613"><b>curl -u "user:password!" "http://<host>:<port>"</b></span>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p851194212514">Example command:</p>
|
||||
<pre class="screen" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_screen136219151262">curl "http://10.62.176.32:9200"</pre>
|
||||
<p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p10778131918610">Example response:</p>
|
||||
<pre class="screen" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_screen15227210104616">HTTP/1.1 200 OK
|
||||
content-type: application/json; charset=UTF-8
|
||||
content-length: 513
|
||||
|
||||
{
|
||||
"name" : "css-xxx-ess-esn-3-1",
|
||||
"cluster_name" : "css-xxx",
|
||||
"cluster_uuid" : "xxx_uuid",
|
||||
"version" : {
|
||||
"number" : "7.10.2",
|
||||
"build_type" : "tar",
|
||||
"build_hash" : "unknown",
|
||||
"build_date" : "unknown",
|
||||
"build_snapshot" : true,
|
||||
"lucene_version" : "9.12.1",
|
||||
"minimum_wire_compatibility_version" : "7.10.0",
|
||||
"minimum_index_compatibility_version" : "7.0.0"
|
||||
},
|
||||
"tagline" : "The OpenSearch Project: https://opensearch.org/"
|
||||
}</pre>
|
||||
<div class="note" id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_note117071415813"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000001992165565__en-us_topic_0000001945217682_en-us_topic_0000001961178833_p47161416815">For more commands, see the <a href="https://docs.opensearch.org/latest/" target="_blank" rel="noopener noreferrer">OpenSearch documentation</a>.</p>
|
||||
</div></div>
|
||||
</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0288.html">Accessing an OpenSearch Cluster</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
18
docs/css/umn/css_01_0031.html
Normal file
18
docs/css/umn/css_01_0031.html
Normal file
@ -0,0 +1,18 @@
|
||||
<a name="EN-US_TOPIC_0000001955726462"></a><a name="EN-US_TOPIC_0000001955726462"></a>
|
||||
|
||||
<h1 class="topictitle1">Accessing an OpenSearch Cluster Using Java</h1>
|
||||
<div id="body0000001955726462"><p id="EN-US_TOPIC_0000001955726462__en-us_topic_0000001945377006_en-us_topic_0000001961178857_p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0032.html">Accessing an OpenSearch Cluster Using the High Level REST Client</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0037.html">Accessing an OpenSearch Cluster Using the Low Level REST Client</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0288.html">Accessing an OpenSearch Cluster</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
1080
docs/css/umn/css_01_0032.html
Normal file
1080
docs/css/umn/css_01_0032.html
Normal file
File diff suppressed because it is too large
Load Diff
19
docs/css/umn/css_01_0033.html
Normal file
19
docs/css/umn/css_01_0033.html
Normal file
@ -0,0 +1,19 @@
|
||||
<a name="EN-US_TOPIC_0000001965496785"></a><a name="EN-US_TOPIC_0000001965496785"></a>
|
||||
|
||||
<h1 class="topictitle1">Backing up and Restoring the Data of an Elasticsearch Cluster</h1>
|
||||
<div id="body0000001633221741"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0267.html">Creating Snapshots to Back Up the Data of an Elasticsearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0266.html">Restoring the Data of an Elasticsearch Cluster Using a Snapshot</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0271.html">Deleting an Elasticsearch Cluster Snapshot</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0207.html">Using Elasticsearch for Data Search</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
3584
docs/css/umn/css_01_0037.html
Normal file
3584
docs/css/umn/css_01_0037.html
Normal file
File diff suppressed because it is too large
Load Diff
3968
docs/css/umn/css_01_0042.html
Normal file
3968
docs/css/umn/css_01_0042.html
Normal file
File diff suppressed because it is too large
Load Diff
435
docs/css/umn/css_01_0043.html
Normal file
435
docs/css/umn/css_01_0043.html
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
141
docs/css/umn/css_01_0046.html
Normal file
141
docs/css/umn/css_01_0046.html
Normal file
File diff suppressed because it is too large
Load Diff
150
docs/css/umn/css_01_0047.html
Normal file
150
docs/css/umn/css_01_0047.html
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
416
docs/css/umn/css_01_0049.html
Normal file
416
docs/css/umn/css_01_0049.html
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
546
docs/css/umn/css_01_0051.html
Normal file
546
docs/css/umn/css_01_0051.html
Normal file
File diff suppressed because it is too large
Load Diff
270
docs/css/umn/css_01_0053.html
Normal file
270
docs/css/umn/css_01_0053.html
Normal file
File diff suppressed because it is too large
Load Diff
@ -8,18 +8,24 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001972160305__row1529013164812"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p1729183113489">2025-04-11</p>
|
||||
<tbody><tr id="EN-US_TOPIC_0000001972160305__row195851951155318"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p1058565175315">2025-11-15</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0000001972160305__p1958555113530">Added:</p>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul1039311590545"><li id="EN-US_TOPIC_0000001972160305__li14393559135411">OpenSearch 2.19 is supported.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001972160305__row1529013164812"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p1729183113489">2025-04-11</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0000001972160305__p1920814012509">Modified:</p>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul12550355175118"><li id="EN-US_TOPIC_0000001972160305__li2550125505110">Added the ability to skip rollover during index lifecycle management: <a href="css_01_0420.html">Automating Index Rollover in an Elasticsearch Cluster Through Index Lifecycle Management</a> and <a href="css_01_0502.html">Automating Index Rollover in an OpenSearch Cluster Through Index Lifecycle Management</a>.</li><li id="EN-US_TOPIC_0000001972160305__li135501755125117">Deleted the >16 GB memory capacity limit: <a href="css_01_0118.html">About Vector Search</a> and <a href="css_01_0465.html">About Vector Search</a>.</li><li id="EN-US_TOPIC_0000001972160305__li255015553511">Added disk encryption: <a href="css_01_0380.html">Creating an Elasticsearch Cluster</a> and <a href="css_01_0275.html">Creating an OpenSearch Cluster</a>.</li><li id="EN-US_TOPIC_0000001972160305__li12550115518517">Added support for the GRAPH_SQ4 and GRAPH_SQ8 indexing algorithms: <a href="css_01_0121.html">Creating Vector Indexes in an Elasticsearch Cluster</a>.</li><li id="EN-US_TOPIC_0000001972160305__li18550125515510">Optimized the frontend procedures for restarting clusters: <a href="css_01_0014.html">Restarting an Elasticsearch Cluster</a> and <a href="css_01_0499.html">Restarting an OpenSearch Cluster</a>.</li></ul>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul12550355175118"><li id="EN-US_TOPIC_0000001972160305__li2550125505110">Added the ability to skip rollover during index lifecycle management: <a href="css_01_0021.html">Automating Index Rollover in an Elasticsearch Cluster Through Index Lifecycle Management</a> and <a href="css_01_0209.html">Automating Index Rollover in an OpenSearch Cluster Through Index Lifecycle Management</a>.</li><li id="EN-US_TOPIC_0000001972160305__li135501755125117">Deleted the >16 GB memory capacity limit: <a href="css_01_0118.html">About CSS Vector Search</a> and <a href="css_01_0103.html">About CSS Vector Search</a>.</li><li id="EN-US_TOPIC_0000001972160305__li255015553511">Added disk encryption: <a href="css_01_0270.html">Creating an Elasticsearch Cluster</a> and <a href="css_01_0269.html">Creating an OpenSearch Cluster</a>.</li><li id="EN-US_TOPIC_0000001972160305__li12550115518517">Added support for the GRAPH_SQ4 and GRAPH_SQ8 indexing algorithms: Creating Vector Indexes in an Elasticsearch Cluster.</li><li id="EN-US_TOPIC_0000001972160305__li18550125515510">Optimized the frontend procedures for restarting clusters: <a href="css_01_0014.html">Restarting an Elasticsearch Cluster</a> and <a href="css_01_0286.html">Restarting an OpenSearch Cluster</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001972160305__row1699711510197"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p89981851121918">2024-11-04</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0000001972160305__p1998751151914">Added:</p>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul13437202043012"><li id="EN-US_TOPIC_0000001972160305__li12747177102612"><a href="css_01_0393.html">Accessing an Elasticsearch Cluster Using LDAP</a>, <a href="css_01_0452.html">Accessing an OpenSearch Cluster Using LDAP</a></li></ul>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul13437202043012"><li id="EN-US_TOPIC_0000001972160305__li12747177102612"><a href="css_01_0017.html">Accessing an Elasticsearch Cluster Using LDAP</a>, <a href="css_01_0248.html">Accessing an OpenSearch Cluster Using LDAP</a></li></ul>
|
||||
<p id="EN-US_TOPIC_0000001972160305__p189961393017">Modified:</p>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul1328213218301"><li id="EN-US_TOPIC_0000001972160305__li128215326308"><a href="css_01_0155.html">Using Cloud Eye to Monitor Elasticsearch Clusters</a>, <a href="css_01_0506.html">Using Cloud Eye to Monitor OpenSearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li11134151123514"><a href="css_01_0379.html">Elasticsearch Cluster Planning Suggestions</a>, <a href="css_01_0380.html">Creating an Elasticsearch Cluster</a>, <a href="css_01_0439.html">OpenSearch Cluster Planning Suggestions</a>, <a href="css_01_0275.html">Creating an OpenSearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li117995268379"><a href="css_01_0075.html">Setting Tags for an Elasticsearch Cluster</a>, <a href="css_01_0488.html">Setting Tags for an OpenSearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li4486115815237"><a href="css_01_0424.html">Monitoring Metrics for Elasticsearch Clusters in Cloud Eye</a>, <a href="css_01_0505.html">Monitoring Metrics for OpenSearch Clusters in Cloud Eye</a></li><li id="EN-US_TOPIC_0000001972160305__li1435344019470"><a href="css_01_0151.html">Scaling Out an Elasticsearch Cluster</a>, <a href="css_01_0418.html">Changing the Node Specifications of an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li1135314012472"><a href="css_01_0544.html">CSS Resource Monitoring</a></li></ul>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul1328213218301"><li id="EN-US_TOPIC_0000001972160305__li128215326308"><a href="css_01_0155.html">Using Cloud Eye to Monitor Elasticsearch Clusters</a>, <a href="css_01_0214.html">Using Cloud Eye to Monitor OpenSearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li11134151123514"><a href="css_01_0188.html">Elasticsearch Cluster Planning Suggestions</a>, <a href="css_01_0270.html">Creating an Elasticsearch Cluster</a>, <a href="css_01_0028.html">OpenSearch Cluster Planning Suggestions</a>, <a href="css_01_0269.html">Creating an OpenSearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li117995268379"><a href="css_01_0075.html">Setting Tags for an Elasticsearch Cluster</a>, <a href="css_01_0277.html">Setting Tags for an OpenSearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li4486115815237"><a href="css_01_0042.html">Monitoring Metrics for Elasticsearch Clusters in Cloud Eye</a>, <a href="css_01_0213.html">Monitoring Metrics for OpenSearch Clusters in Cloud Eye</a></li><li id="EN-US_TOPIC_0000001972160305__li1435344019470"><a href="css_01_0151.html">Scaling Out an Elasticsearch Cluster</a>, <a href="css_01_0245.html">Changing the Node Specifications of an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li1135314012472"><a href="css_01_0250.html">CSS Resource Monitoring</a></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001972160305__row621771214596"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p8217712195917">2024-05-17</p>
|
||||
@ -45,14 +51,14 @@
|
||||
<tr id="EN-US_TOPIC_0000001972160305__row16274132412711"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p1727517247713">2023-09-25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.1.1.3.1.2 "><p id="EN-US_TOPIC_0000001972160305__p1634711571272">Added:</p>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul116511171476"><li id="EN-US_TOPIC_0000001972160305__li36815252713"><a href="css_01_0413.html">Configuring a Dedicated Load Balancer for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li148817457915"><a href="css_01_0156.html">Replacing Specified Nodes for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li347163415910">Adding master/client nodes</li><li id="EN-US_TOPIC_0000001972160305__li768252510713"><a href="css_01_0158.html">Changing the Security Mode of an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li1068216257714"><a href="css_01_0201.html">Switching AZs for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li106821525376"><a href="css_01_0186.html">Upgrading the Version of an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li1682112518717"><a href="css_01_0061.html">Using SQL to Search for Data in Elasticsearch</a></li><li id="EN-US_TOPIC_0000001972160305__li1940957192718">Using the Open Distro Alarm Plugin</li><li id="EN-US_TOPIC_0000001972160305__li792891214284">(Optional) Service Authorization</li><li id="EN-US_TOPIC_0000001972160305__li1968318258711">Monitoring Metrics</li><li id="EN-US_TOPIC_0000001972160305__li17495169086">Logstash</li><li id="EN-US_TOPIC_0000001972160305__li114562135107"><a href="css_01_0397.html">Enhancing the Data Import Performance of Elasticsearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li2997165621010"><a href="css_01_0409.html">Configuring Enhanced Aggregation for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li5119223161116"><a href="css_01_0410.html">Configuring Read/Write Splitting Between Two Elasticsearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li0406193661116">Intelligent O&M</li></ul>
|
||||
<ul id="EN-US_TOPIC_0000001972160305__ul116511171476"><li id="EN-US_TOPIC_0000001972160305__li36815252713"><a href="css_01_0181.html">Configuring a Dedicated Load Balancer for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li148817457915"><a href="css_01_0156.html">Replacing a Specified Node for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li347163415910">Adding master/client nodes</li><li id="EN-US_TOPIC_0000001972160305__li768252510713"><a href="css_01_0158.html">Changing the Security Mode of an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li1068216257714"><a href="css_01_0201.html">Switching AZs for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li106821525376"><a href="css_01_0186.html">Upgrading the Version of an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li1682112518717"><a href="css_01_0061.html">Using SQL to Search for Data in Elasticsearch</a></li><li id="EN-US_TOPIC_0000001972160305__li1940957192718">Using the Open Distro Alarm Plugin</li><li id="EN-US_TOPIC_0000001972160305__li792891214284">(Optional) Service Authorization</li><li id="EN-US_TOPIC_0000001972160305__li1968318258711">Monitoring Metrics</li><li id="EN-US_TOPIC_0000001972160305__li17495169086">Logstash</li><li id="EN-US_TOPIC_0000001972160305__li114562135107"><a href="css_01_0228.html">Enhancing the Data Ingestion Performance of Elasticsearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li2997165621010"><a href="css_01_0173.html">Configuring Enhanced Aggregation for an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li5119223161116"><a href="css_01_0162.html">Configuring Read/Write Splitting Between Two Elasticsearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li0406193661116">Intelligent O&M</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EN-US_TOPIC_0000001972160305__row1296665215214"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.1.1.3.1.1 "><p id="EN-US_TOPIC_0000001972160305__p2967175275215">2023-03-28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.1.1.3.1.2 "><ul id="EN-US_TOPIC_0000001972160305__ul196098186522"><li id="EN-US_TOPIC_0000001972160305__li132265210494">Optimized the content structure of the following sections:<ul id="EN-US_TOPIC_0000001972160305__ul81831921175012"><li id="EN-US_TOPIC_0000001972160305__li21831121175010">What Is Cloud Search Service?</li><li id="EN-US_TOPIC_0000001972160305__li74423445113">Related Services</li><li id="EN-US_TOPIC_0000001972160305__li7638194315210">Clusters in Security Mode</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001972160305__li15686408437">Updated the procedure description in the following sections:<ul id="EN-US_TOPIC_0000001972160305__ul106431260430"><li id="EN-US_TOPIC_0000001972160305__li424414521111">Getting Started with Elasticsearch</li><li id="EN-US_TOPIC_0000001972160305__li112056201891">Changing Specifications</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001972160305__li1828852714526">Added:<ul id="EN-US_TOPIC_0000001972160305__ul2040763065220"><li id="EN-US_TOPIC_0000001972160305__li43052012125314">Advantages</li><li id="EN-US_TOPIC_0000001972160305__li7261521115316">Product Components</li><li id="EN-US_TOPIC_0000001972160305__li4827193835217">Permission Management</li><li id="EN-US_TOPIC_0000001972160305__li1890894112102"><a href="css_01_0072.html">Creating IAM Users and Granting Them Permissions to Use CSS</a></li><li id="EN-US_TOPIC_0000001972160305__li843115583101">CSS Custom Policies</li><li id="EN-US_TOPIC_0000001972160305__li11253104051118"><a href="css_01_0382.html">Logging In to an Elasticsearch Cluster Using Kibana</a></li><li id="EN-US_TOPIC_0000001972160305__li1696953975911"><a href="css_01_0415.html">Viewing Elasticsearch Cluster Information</a></li><li id="EN-US_TOPIC_0000001972160305__li48321354123"><a href="css_01_0151.html">Scaling Out an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li115721054161218"><a href="css_01_0153.html">Scaling In an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li187842012171316">Removing Specified Nodes</li><li id="EN-US_TOPIC_0000001972160305__li3111134115718"><a href="css_01_0058.html">Binding an Elasticsearch Cluster to an Enterprise Project</a></li><li id="EN-US_TOPIC_0000001972160305__li9350114516577">Kibana Platform</li><li id="EN-US_TOPIC_0000001972160305__li4769949191417"><a href="css_01_0155.html">Using Cloud Eye to Monitor Elasticsearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li67718713313">Optimized the directory structure based on the question types.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001972160305__li1828852714526">Added:<ul id="EN-US_TOPIC_0000001972160305__ul2040763065220"><li id="EN-US_TOPIC_0000001972160305__li43052012125314">Advantages</li><li id="EN-US_TOPIC_0000001972160305__li7261521115316">Product Components</li><li id="EN-US_TOPIC_0000001972160305__li4827193835217">Permission Management</li><li id="EN-US_TOPIC_0000001972160305__li1890894112102"><a href="css_01_0070.html">Creating IAM Users and Granting Them Permissions to Use CSS</a></li><li id="EN-US_TOPIC_0000001972160305__li843115583101">CSS Custom Policies</li><li id="EN-US_TOPIC_0000001972160305__li11253104051118"><a href="css_01_0108.html">Logging In to an Elasticsearch Cluster Using Kibana</a></li><li id="EN-US_TOPIC_0000001972160305__li1696953975911"><a href="css_01_0185.html">Viewing Elasticsearch Cluster Information</a></li><li id="EN-US_TOPIC_0000001972160305__li48321354123"><a href="css_01_0151.html">Scaling Out/Up an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li115721054161218"><a href="css_01_0153.html">Scaling In/Down an Elasticsearch Cluster</a></li><li id="EN-US_TOPIC_0000001972160305__li187842012171316">Removing Specified Nodes</li><li id="EN-US_TOPIC_0000001972160305__li3111134115718"><a href="css_01_0058.html">Associating an Elasticsearch Cluster with an Enterprise Project</a></li><li id="EN-US_TOPIC_0000001972160305__li9350114516577">Kibana Platform</li><li id="EN-US_TOPIC_0000001972160305__li4769949191417"><a href="css_01_0155.html">Using Cloud Eye to Monitor Elasticsearch Clusters</a></li><li id="EN-US_TOPIC_0000001972160305__li67718713313">Optimized the directory structure based on the question types.</li></ul>
|
||||
</li><li id="EN-US_TOPIC_0000001972160305__li19853143114182">Deleted the following sections:<ul id="EN-US_TOPIC_0000001972160305__ul74347406187"><li id="EN-US_TOPIC_0000001972160305__li312913565318">What Is Kibana?</li><li id="EN-US_TOPIC_0000001972160305__li68888795412">What is Cerebro?</li><li id="EN-US_TOPIC_0000001972160305__li843411409188">Suggestions on Using Elasticsearch</li><li id="EN-US_TOPIC_0000001972160305__li1646124517187">Viewing Monitoring Metrics</li><li id="EN-US_TOPIC_0000001972160305__li16754226175413">Creating Alarm Rules</li></ul>
|
||||
</li></ul>
|
||||
</td>
|
||||
615
docs/css/umn/css_01_0056.html
Normal file
615
docs/css/umn/css_01_0056.html
Normal file
File diff suppressed because it is too large
Load Diff
@ -1,13 +1,11 @@
|
||||
<a name="css_01_0058"></a><a name="css_01_0058"></a>
|
||||
<a name="EN-US_TOPIC_0000001938218348"></a><a name="EN-US_TOPIC_0000001938218348"></a>
|
||||
|
||||
<h1 class="topictitle1">Binding an Elasticsearch Cluster to an Enterprise Project</h1>
|
||||
<div id="body1547448423138"><p id="css_01_0058__en-us_topic_0000001268594561_p17448200144115">You can create enterprise projects based on your organizational structure. Then you can manage resources across different regions by enterprise project, add users and user groups to enterprise projects, and grant different permissions to the users and user groups. This section describes how to bind a CSS cluster to an enterprise project and how to modify an enterprise project.</p>
|
||||
<div class="section" id="css_01_0058__en-us_topic_0000001268594561_section149801923192910"><h4 class="sectiontitle">Prerequisites</h4><p id="css_01_0058__en-us_topic_0000001268594561_p166501928172918">Before binding an enterprise project, you have created an enterprise project.</p>
|
||||
<h1 class="topictitle1">Associating an Elasticsearch Cluster with an Enterprise Project</h1>
|
||||
<div id="body1547448423138"><p id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_p17448200144115">In CSS, you can associate your Elasticsearch cluster with an enterprise project. You can create enterprise projects based on your organizational structure. Then you can manage resources across different regions by enterprise project, add users and user groups to enterprise projects, and grant different permissions to the users and user groups.</p>
|
||||
<p id="EN-US_TOPIC_0000001938218348__p10876258174410">You can associate your cluster with an enterprise project either when creating the cluster or afterward.</p>
|
||||
<div class="section" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_section149801923192910"><h4 class="sectiontitle">Prerequisites</h4><p id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_p166501928172918">You have created an enterprise project.</p>
|
||||
</div>
|
||||
<div class="section" id="css_01_0058__en-us_topic_0000001268594561_section57873201918"><h4 class="sectiontitle">Binding an Enterprise Project</h4><p id="css_01_0058__en-us_topic_0000001268594561_p2210251391">When creating a cluster, you can bind an existing enterprise project to the cluster, or click <strong id="css_01_0058__b359216131512">View Enterprise Project</strong> to go to the enterprise project management console and create a new project or view existing projects.</p>
|
||||
</div>
|
||||
<div class="section" id="css_01_0058__en-us_topic_0000001268594561_section2120201511011"><h4 class="sectiontitle">Modifying an Enterprise Project</h4><p id="css_01_0058__en-us_topic_0000001268594561_p7438234131011">For a cluster that has been created, you can modify its enterprise project based on the site requirements.</p>
|
||||
<ol id="css_01_0058__en-us_topic_0000001268594561_ol1947141411194"><li id="css_01_0058__en-us_topic_0000001268594561_li8101103316318">Log in to the CSS management console.</li><li id="css_01_0058__en-us_topic_0000001268594561_li6302956053">In the navigation pane on the left, select a cluster type. The cluster management page is displayed.</li><li id="css_01_0058__en-us_topic_0000001268594561_li8302155619516">In the cluster list on the displayed page, click the target cluster name to switch to the <strong id="css_01_0058__en-us_topic_0000001268594561_b655595516369">Cluster Information</strong> page.</li><li id="css_01_0058__en-us_topic_0000001268594561_li4230112181920">On the <span class="uicontrol" id="css_01_0058__en-us_topic_0000001268594561_uicontrol1144519117472"><b>Cluster Information</b></span> page, click the enterprise project name on the right of <span class="uicontrol" id="css_01_0058__en-us_topic_0000001268594561_uicontrol12693632149"><b>Enterprise Project</b></span>. The project management page is displayed.</li><li id="css_01_0058__en-us_topic_0000001268594561_li1669213196206">On the <span class="uicontrol" id="css_01_0058__en-us_topic_0000001268594561_uicontrol4510247182817"><b>Resources</b></span> tab page, select the region of the current cluster, and select <strong id="css_01_0058__b988412014713">CSS</strong> for <strong id="css_01_0058__b75453276475">Service</strong>. In this case, the corresponding CSS cluster is displayed in the resource list.</li><li id="css_01_0058__en-us_topic_0000001268594561_li78671469217">Select the cluster whose enterprise project you want to modify and click <span class="uicontrol" id="css_01_0058__en-us_topic_0000001268594561_uicontrol5366101511813"><b>Remove</b></span>.</li><li id="css_01_0058__en-us_topic_0000001268594561_li19166117162317">On the <span class="wintitle" id="css_01_0058__en-us_topic_0000001268594561_wintitle1516933271819"><b>Remove Resource</b></span> page, specify <span class="parmname" id="css_01_0058__en-us_topic_0000001268594561_parmname1674851311229"><b>Mode</b></span> and select <span class="parmname" id="css_01_0058__en-us_topic_0000001268594561_parmname1365814264018"><b>Destination Enterprise Project</b></span>, and click <span class="uicontrol" id="css_01_0058__en-us_topic_0000001268594561_uicontrol199034303020"><b>OK</b></span>.</li><li id="css_01_0058__en-us_topic_0000001268594561_li599664183618">After the resource is removed, you can view the modified enterprise project information on the <strong id="css_01_0058__en-us_topic_0000001268594561_b119217384210">Clusters</strong> page.</li></ol>
|
||||
<div class="section" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_section2120201511011"><h4 class="sectiontitle">Managing Enterprise Projects</h4><ol id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_ol1947141411194"><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li8101103316318"><span id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001938377572_ph152259618315">Log in to the CSS management console.</span></li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li6302956053">In the navigation pane on the left, choose <span class="uicontrol" id="EN-US_TOPIC_0000001938218348__uicontrol8971553085138"><b>Clusters > Elasticsearch</b></span>.</li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li8302155619516">In the cluster list, click the name of the target cluster. The cluster information page is displayed.</li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li4230112181920">On the <strong id="EN-US_TOPIC_0000001938218348__b129327231372116">Overview</strong> tab, find <strong id="EN-US_TOPIC_0000001938218348__b96555628572116">Enterprise Project</strong> in the <strong id="EN-US_TOPIC_0000001938218348__b176435351872116">Configuration</strong> area, and click the enterprise project name next to it. The <strong id="EN-US_TOPIC_0000001938218348__b42356816272116">Project Management</strong> page is displayed.</li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li1669213196206">On the <strong id="EN-US_TOPIC_0000001938218348__b110175838372116">Resources</strong> tab, select the region of the current cluster, and select <strong id="EN-US_TOPIC_0000001938218348__b14608793972116">CloudSearchService</strong> as <strong id="EN-US_TOPIC_0000001938218348__b108298616872116">Service</strong>. Then click <strong id="EN-US_TOPIC_0000001938218348__b1040073018235">Search</strong>. The CSS clusters are displayed in the resource list below.</li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li78671469217">Select the cluster whose enterprise project you want to modify and click <span class="uicontrol" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_uicontrol5366101511813"><b>Remove</b></span>.</li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li19166117162317">On the <span class="wintitle" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_wintitle1516933271819"><b>Remove Resource</b></span> page, specify <span class="parmname" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_parmname1674851311229"><b>Mode</b></span> and select <span class="parmname" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_parmname1365814264018"><b>Destination Enterprise Project</b></span>, and click <span class="uicontrol" id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_uicontrol199034303020"><b>OK</b></span>.</li><li id="EN-US_TOPIC_0000001938218348__en-us_topic_0000001268594561_li599664183618">After the change is complete, return to the Elasticsearch cluster list on the CSS console and check the cluster's new enterprise project.</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
26
docs/css/umn/css_01_0059.html
Normal file
26
docs/css/umn/css_01_0059.html
Normal file
@ -0,0 +1,26 @@
|
||||
<a name="EN-US_TOPIC_0000001955726474"></a><a name="EN-US_TOPIC_0000001955726474"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Importing Data to an OpenSearch Cluster</h1>
|
||||
|
||||
<div id="body0000001955726474"></div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="css_01_0084.html">Different Ways to Ingest Data into an OpenSearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0085.html">Using In-house Built Logstash to Ingest Data into an OpenSearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0087.html">Using Open Source OpenSearch APIs to Import Data to an OpenSearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0089.html">Using CDM to Import Data to an OpenSearch Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="css_01_0090.html">Enhancing the Data Ingestion Performance of OpenSearch Clusters</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0273.html">Using OpenSearch for Data Search</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user