You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md
+6-60Lines changed: 6 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,19 +19,18 @@ products:
19
19
20
20
New or updated versions of the {{stack}} must be prepared to work with {{ece}} and are provided as packs that you can download.
21
21
22
-
::::{important}
23
-
{{es}} 7.8 and later comes with Index Lifecycle Management (ILM) always enabled. Before upgrading to 7.8 or later, to avoid any unpredictable behavior it is important to configure hot-warm clusters on {{ece}} with ILM rather than index curation. Check [migrate to index lifecycle management](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md) for existing clusters, and [configure index management](/manage-data/lifecycle/index-lifecycle-management.md) for new clusters.
24
-
::::
25
-
26
-
27
22
28
23
## Most recent {{stack}} packs [ece_most_recent_elastic_stack_packs]
29
24
30
-
:::{important}
25
+
:::{admonition} {{ece}} 4 removed support for {{stack}} 7.x versions
26
+
{{ece}} 4 no longer supports {{stack}} versions prior to 8.0.0. Upgrade all deployments to 8.0.0 or later before upgrading to {{ece}} 4.x. Refer to the [Product compatibility support matrix -> Compatibility with {{ece}}](https://www.elastic.co/support/matrix#matrix_compatibility) for details.
27
+
:::
28
+
29
+
:::{note}
31
30
Enterprise Search is not available in versions 9.0+.
32
31
:::
33
32
34
-
The following are the most recently released {{stack}} packs for version 9.x, 8.x, 7.x, and 6.x, respectively:
33
+
The following are the most recently released {{stack}} packs for version 9.x, 8.x, and 7.x, respectively:
Copy file name to clipboardExpand all lines: deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md
+15-3Lines changed: 15 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,10 @@ Find answers to your questions about AutoOps for ECE, ECK, and self-managed clus
24
24
*[Can I use macOS to install {{agent}} for this feature?](#macos-install)
25
25
*[Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address)
26
26
27
-
**Questions about collected metrics**
27
+
**Questions about collected metrics and data**
28
28
*[Where are AutoOps metrics stored?](#autoops-metrics-storage)
29
29
*[What information does {{agent}} extract from my cluster?](#extracted-info)
30
+
*[How does AutoOps gather data from my cluster and ensure its security?](#data-gathering)
30
31
31
32
## General questions
32
33
$$$why-autoops$$$**Why should I use AutoOps for my clusters?**
@@ -42,7 +43,7 @@ $$$autoops-metrics-cost$$$ **Is there an added cost for shipping metrics data to
42
43
You can [choose the CSP region where your data is stored](#autoops-metrics-storage).
43
44
44
45
$$$es-versions$$$**Which versions of {{es}} does AutoOps support?**
45
-
: AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol).
46
+
: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above).
46
47
47
48
$$$deployment-types$$$**Which deployment types can be connected to AutoOps?**
48
49
: You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment.
@@ -65,7 +66,7 @@ $$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable t
65
66
66
67
: For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md).
67
68
68
-
## Questions about collected metrics
69
+
## Questions about collected metrics and data
69
70
$$$autoops-metrics-storage$$$**Where are AutoOps metrics stored?**
70
71
: You can choose where to store your metrics from the following AWS regions:
71
72
@@ -88,3 +89,14 @@ $$$extracted-info$$$ **What information does {{agent}} extract from my cluster?*
88
89
| [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format |
89
90
| [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects |
90
91
92
+
$$$data-gathering$$$**How does AutoOps gather data from my cluster and ensure its security?**
93
+
: AutoOps gathers data from your cluster using two protocols:
94
+
* **HTTP request**: Made to our Cloud Connected API to register your cluster with {{ecloud}} and gather registration-related data.
95
+
* **OpenTelemetry Protocol (OTLP)**: Used to gather all other operational data.
96
+
97
+
Each channel is authenticated through an API key or token to ensure your data's security. The following table offers more details:
98
+
99
+
| Protocol | Data extracted | Port | Authentication method |
100
+
| --- | --- | --- | --- |
101
+
| HTTP | Basic cluster information from the `/` endpoint <br><br> License information from the `/_license` endpoint | **443**: standard HTTPS port | Uses an {{ecloud}} API key which is limited for use with Cloud Connect only. |
102
+
| OTLP | Operational information | **4318**: standard OTLP HTTP port <br><br> This service will be exposed on port 443 in the future. | Uses an AutoOps token which is functionally equivalent to an API key. |
Copy file name to clipboardExpand all lines: deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,4 +49,5 @@ The following table shows the errors you might encounter if something goes wrong
49
49
|`LICENSE_EXPIRED`| Elastic license is expired | Contact [sales](https://www.elastic.co/contact#sales) to renew your license. |
50
50
|`LICENSE_USED_BY_ANOTHER_ACCOUNT`| License key connected to another account | A license key can only be connected to one {{ecloud}} organization. Contact [Elastic support](https://support.elastic.co/) for help. |
51
51
|`VERSION_MISMATCH`| {{es}} version is unsupported | Upgrade your cluster to a [supported version](https://www.elastic.co/support/eol). |
52
-
|`UNKNOWN_ERROR`| Installation failed | {{agent}} couldn't be installed due to an unknown issue. Consult the troubleshooting guide or contact [Elastic support](https://support.elastic.co/) for more help. |
52
+
|`UNKNOWN_ERROR`| Installation failed | {{agent}} couldn't be installed due to an unknown issue. Consult the troubleshooting guide or contact [Elastic support](https://support.elastic.co/) for more help. |
53
+
| `` | Failed to register Cloud Connected Mode: cluster license type is not supported | The cluster you are trying to connect doesn't have the required license to connect to AutoOps. For more information, refer to the [prerequisites](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites). |
Copy file name to clipboardExpand all lines: deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ If you have an {{es}} cluster set up for local development or testing, you can c
21
21
22
22
Ensure your system meets the following requirements before proceeding:
23
23
24
-
* Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol).
24
+
* Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol) (7.17.x and above).
25
25
* Your cluster is on an [Enterprise self-managed license](https://www.elastic.co/subscriptions) or an active self-managed [trial](https://cloud.elastic.co/registration).
26
26
* The agent you install for the connection is allowed to send metrics to {{ecloud}}.
27
27
@@ -101,11 +101,13 @@ Select one of the following methods to install {{agent}}:
101
101
Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes.
102
102
:::
103
103
104
+
To learn more about how AutoOps securely gathers data from your cluster, refer to our [FAQ](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md#data-gathering).
105
+
104
106
### Configure agent
105
107
106
108
Depending on your selected installation method, you may have to provide the following information to create the installation command:
107
109
108
-
***{{es}} endpoint URL**: The agent will use this URL to identify which cluster you want to connect to AutoOps.
110
+
***{{es}} endpoint URL**: Enter the URL for the {{es}} cluster you want to monitor by connecting to AutoOps.
109
111
***Preferred authentication method**: Choose one of the following:
110
112
:::::{tab-set}
111
113
:group: api-key-or-basic
@@ -204,7 +206,7 @@ If you manually assign privileges, you won't be able to allow {{agent}} to acces
204
206
205
207
:::::
206
208
***System architecture**: Select the system architecture of the machine running the agent.
207
-
***Metrics storage location**: Select where to store your metrics data from the list of available regions.
209
+
***Metrics storage location**: Select where to store your metrics data from the list of available AWS regions.
208
210
209
211
:::{include} ../_snippets/autoops-cc-regions.md
210
212
:::
@@ -281,10 +283,11 @@ You can use the same installation command to connect multiple clusters, but each
281
283
282
284
Complete the following steps to disconnect your cluster from your Cloud organization. You need the **Organization owner**[role](/deploy-manage/monitor/autoops/cc-manage-users.md#assign-roles) to perform this action.
283
285
286
+
2. Based on your [installation method](#select-installation-method), complete the steps to stop {{agent}} from shipping metrics to {{ecloud}}.
284
287
1. Log in to [{{ecloud}}](https://cloud.elastic.co/home).
285
-
2. In the **Connected clusters** section, locate the cluster you want to disconnect.
286
-
3. From that cluster’s actions menu, select **Disconnect cluster**.
287
-
4. Enter the cluster’s name in the field that appears and then select **Disconnect cluster**.
288
+
3. On the **Connected clusters**page or the **Connected clusters**section of the home page, locate the cluster you want to disconnect.
289
+
4. From that cluster’s actions menu, select **Disconnect cluster**.
290
+
5. Enter the cluster’s name in the field that appears and then select **Disconnect cluster**.
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/alerting-common-issues.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ Configuration options are available to specialize connections to TLS servers, in
60
60
Rules are taking a long time to run and are impacting the overall health of your deployment.
61
61
62
62
::::{important}
63
-
By default, only users with a `superuser` role can query the [preview]{{kib}} event log because it is a system index. To enable additional users to run this query, assign `read` privileges to the `.kibana-event-log*` index.
63
+
By default, only users with a `superuser` role can query the {{kib}} event log because it is a system index. To enable additional users to run this query, assign `read` privileges to the `.kibana-event-log*` index.
0 commit comments