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/monitor/autoops/cc-autoops-as-cloud-connected.md
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,26 @@ products:
12
12
13
13
# AutoOps for self-managed clusters
14
14
15
-
For ECE ({{ece}}), ECK ({{eck}}), and self-managed clusters, AutoOps can be set up in all supported [regions](ec-autoops-regions.md#autoops-for-self-managed-clusters-regions) through [Cloud Connect](/deploy-manage/cloud-connect.md). More regions are coming soon.
15
+
For ECE ({{ece}}), ECK ({{eck}}), and self-managed {{es}} clusters, AutoOps can be set up in all supported [regions](ec-autoops-regions.md#autoops-for-self-managed-clusters-regions) through [Cloud Connect](/deploy-manage/cloud-connect.md). More regions are coming soon.
16
16
17
17
Cloud Connect enables users of ECE, ECK, and self-managed clusters to use {{ecloud}} services. This means you can take advantage of the simplified cluster monitoring, real-time issue detection, and performance recommendations of AutoOps without having to run and manage the underlying infrastructure.
18
18
19
+
## How your self-managed cluster connects to AutoOps
20
+
21
+
To connect your ECE, ECK, or self-managed cluster to AutoOps, you have to use your {{ecloud}} account to install {{agent}}. After that, the process can be broken down into three components:
:alt: Diagram depicting how AutoOps for self-managed clusters works
28
+
:::
29
+
30
+
For instructions on how to get started, refer to [](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md).
31
+
32
+
After this setup is complete, you can start using AutoOps to monitor your cluster. Learn more about what you can do with AutoOps in [views](/deploy-manage/monitor/autoops/views.md) and [events](/deploy-manage/monitor/autoops/ec-autoops-events.md).
33
+
34
+
19
35
## Section overview
20
36
21
37
In this section, you'll find the following information:
@@ -26,4 +42,5 @@ In this section, you'll find the following information:
26
42
* A [troubleshooting guide](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md) to help you with any issues you may encounter
27
43
28
44
:::{tip}
29
-
Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#questions-about-autoops-for-self-managed-clusters) for answers to commonly asked questions about AutoOps for self-managed clusters.
45
+
Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#questions-about-autoops-for-self-managed-clusters) for answers to commonly asked questions about AutoOps for self-managed clusters.
Copy file name to clipboardExpand all lines: deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
+31-33Lines changed: 31 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,42 +44,12 @@ $$$firewall$$$**My organization's firewall may be preventing {{agent}} from coll
44
44
Run the following tests within the context of your execution environment. That is, if your chosen installation method is Kubernetes, run the commands from within the pod; for Docker, run the commands from within the container, and so on.
45
45
:::
46
46
47
-
There are three main components of {{agent}}'s connection with your system:
47
+
There are [three main components](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md#how-your-self-managed-cluster-connects-to-autoops) of {{agent}}'s connection with your system:
48
48
49
-
1. {{agent}} registers your cluster with {{ecloud}}
50
-
2. {{agent}} connects to your cluster
51
-
3. {{agent}} sends metrics from your cluster to {{ecloud}}
52
-
53
-
If there is an issue with the first component, the agent will stop working and your logs might look like:
54
-
55
-
```sh
56
-
... failed to register Cloud Connected Mode: ... Post \"https://api.elastic-cloud.com/api/v1/cloud-connected/clusters\": ...
57
-
```
58
-
59
-
To test if your organization is not allowing the agent to register your cluster with {{ecloud}}, run the following command:
If you do not receive a similar response, configure your HTTP proxy to allow it to reach the URL (with headers and a JSON body):
74
-
75
-
```json
76
-
POST https://api.elastic-cloud.com/api/v1/cloud-connected/clusters
77
-
```
78
-
:::{note}
79
-
If you are using Docker, you may need to complete this configuration directly via the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
If there is an issue with the second component, {{agent}} cannot connect to your cluster. To test if your organization is not allowing this connection, run the following command depending on your chosen authentication method:
52
+
If there is an issue with the first component, {{agent}} cannot connect to your cluster. To test if your organization is not allowing this connection, run the following command depending on your chosen authentication method:
83
53
84
54
:::::{tab-set}
85
55
:group: api-key-or-basic
@@ -138,6 +108,34 @@ $$$firewall$$$**My organization's firewall may be preventing {{agent}} from coll
138
108
| You are using a custom SSL/TLS configuration with {{es}} | Disable SSL/TLS verification so that your system trusts all certificates. We do not recommend disabling verification in production environments. <br><br> If you are using API key authentication, run the following command: <br><br>`curl -XGET --insecure -i $AUTOOPS_ES_URL \ -H "Authorization: ApiKey $AUTOOPS_ES_API_KEY"`. <br><br> If you are using username/password authentication, run the following command: <br><br> `curl -XGET --insecure -i $AUTOOPS_ES_URL \ -u $AUTOOPS_ES_USERNAME` <br><br> If the issue is resolved, you need to configure your custom SSL/TLS settings with {{agent}}. If the issue persists, contact [Elastic support](https://support.elastic.co/).|
139
109
| You are connecting a local development cluster using Docker without specifying `--network host` | - Make sure you are following all the steps to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md#connect-your-local-development-cluster-to-autoops). <br> - In the [Install agent](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#install-agent) step, make sure you are replacing `docker run -d \` with `docker run -d --network host \`. |
140
110
111
+
If there is an issue with the second component, the agent will stop working and your logs might look like:
112
+
113
+
```sh
114
+
... failed to register Cloud Connected Mode: ... Post \"https://api.elastic-cloud.com/api/v1/cloud-connected/clusters\": ...
115
+
```
116
+
117
+
To test if your organization is not allowing the agent to register your cluster with {{ecloud}}, run the following command:
If you do not receive a similar response, configure your HTTP proxy to allow it to reach the URL (with headers and a JSON body):
132
+
133
+
```json
134
+
POST https://api.elastic-cloud.com/api/v1/cloud-connected/clusters
135
+
```
136
+
:::{note}
137
+
If you are using Docker, you may need to complete this configuration directly via the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
138
+
:::
141
139
142
140
If there is an issue with the third component, the agent will attempt to establish the connection and your logs might look like:
Copy file name to clipboardExpand all lines: solutions/observability/observability-ai-assistant.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,25 +18,25 @@ You can [interact with the AI Assistant](#obs-ai-interact) in two ways:
18
18
***Contextual insights**: Embedded assistance throughout Elastic UIs that explains errors and messages with suggested remediation steps.
19
19
***Chat interface**: A conversational experience where you can ask questions and receive answers about your data. The assistant uses function calling to request, analyze, and visualize information based on your needs.
20
20
21
-
The AI Assistant integrates with your large language model (LLM) provider through our supported {{stack}} connectors:
21
+
The AI Assistant integrates with your large language model (LLM) provider through our [supported {{stack}} connectors](kibana://reference/connectors-kibana/gen-ai-connectors.md). Refer to the [{{obs-ai-assistant}} LLM performance matrix](./llm-performance-matrix.md) for supported third-party LLM providers and their performance ratings.
22
22
23
23
## Use cases
24
24
25
25
The {{obs-ai-assistant}} helps you:
26
26
27
-
***Decode error messages**: Interpret stack traces and error logs to pinpoint root causes
28
-
***Identify performance bottlenecks**: Find resource-intensive operations and slow queries in Elasticsearch
29
-
***Generate reports**: Create alert summaries and incident timelines with key metrics
30
-
***Build and execute queries**: Build Elasticsearch queries from natural language, convert Query DSL to ES|QL syntax, and execute queries directly from the chat interface
31
-
***Visualize data**: Create time-series charts and distribution graphs from your Elasticsearch data
27
+
***Decode error messages**: Interpret stack traces and error logs to pinpoint root causes.
28
+
***Identify performance bottlenecks**: Find resource-intensive operations and slow queries in {{es}}.
29
+
***Generate reports**: Create alert summaries and incident timelines with key metrics.
30
+
***Build and execute queries**: Build {{es}} queries from natural language, convert Query DSL to {{esql}} syntax, and execute queries directly from the chat interface.
31
+
***Visualize data**: Create time-series charts and distribution graphs from your {{es}} data.
32
32
33
33
## Requirements [obs-ai-requirements]
34
34
35
35
The AI assistant requires the following:
36
36
37
37
- An **Elastic deployment**:
38
38
39
-
- For **Observability**: {{stack}} version **8.9** or later, or an **{{observability}} serverless project**.
39
+
- For **{{observability}}**: {{stack}} version **8.9** or later, or an **{{observability}} serverless project**.
40
40
41
41
- For **Search**: {{stack}} version **8.16.0** or later, or **{{serverless-short}} {{es}} project**.
42
42
@@ -46,12 +46,12 @@ The AI assistant requires the following:
46
46
47
47
- The free tier offered by third-party generative AI provider may not be sufficient for the proper functioning of the AI assistant. In most cases, a paid subscription to one of the supported providers is required.
48
48
49
-
Refer to the [documentation](/deploy-manage/manage-connectors.md) for your provider to learn about supported and default models.
49
+
Refer to the [documentation](kibana://reference/connectors-kibana/gen-ai-connectors.md) for your provider to learn about supported and default models.
50
50
51
51
* The knowledge base requires a 4 GB {{ml}} node.
52
52
- In {{ecloud}} or {{ece}}, if you have Machine Learning autoscaling enabled, Machine Learning nodes will be started when using the knowledge base and AI Assistant. Therefore using these features will incur additional costs.
53
53
54
-
* A self-deployed connector service if [content connectors](elasticsearch://reference/search-connectors/index.md) are used to populate external data into the knowledge base.
54
+
* A self-deployed connector service if you're using [content connectors](elasticsearch://reference/search-connectors/index.md) to populate external data into the knowledge base.
55
55
56
56
## Manage access to AI Assistant
57
57
@@ -62,9 +62,9 @@ serverless: ga
62
62
63
63
The [**GenAI settings**](/explore-analyze/manage-access-to-ai-assistant.md) page allows you to:
64
64
65
-
- Manage which AI connectors are available in your environment.
65
+
- Manage which AI connectors are available in your environment.
66
66
- Enable or disable AI Assistant and other AI-powered features in your environment.
67
-
- {applies_to}`stack: ga 9.2` {applies_to}`serverless: unavailable` Specify in which Elastic solutions the `AI Assistant for Observability and Search` and the `AI Assistant for Security` appear.
67
+
- {applies_to}`stack: ga 9.2` {applies_to}`serverless: unavailable` Specify in which Elastic solutions the `AI Assistant for {{observability}} and Search` and the `AI Assistant for Security` appear.
68
68
69
69
## Your data and the AI Assistant [data-information]
70
70
@@ -98,11 +98,11 @@ The AI Assistant connects to one of these supported LLM providers:
98
98
99
99
**Setup steps**:
100
100
101
-
1.**Create authentication credentials** with your chosen provider using the links above.
101
+
1.**Create authentication credentials** with your chosen provider using the links in the previous table.
102
102
2.**Create an LLM connector** for your chosen provider by going to the **Connectors** management page in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
103
103
3.**Authenticate the connection** by entering:
104
-
- The provider's API endpoint URL
105
-
- Your authentication key or secret
104
+
- The provider's API endpoint URL.
105
+
- Your authentication key or secret.
106
106
107
107
::::{admonition} Recommended models
108
108
While the {{obs-ai-assistant}} is compatible with many different models, refer to the [Large language model performance matrix](/solutions/observability/llm-performance-matrix.md) to select models that perform well with your desired use cases.
Copy file name to clipboardExpand all lines: solutions/observability/streams/management/significant-events.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
@@ -10,5 +10,5 @@ Significant Events periodically runs a query on your stream to find important ev
10
10
11
11
To define significant events, either:
12
12
13
-
-**Generate significant events with AI:**(requires an [LLM connector](../../../security/ai/set-up-connectors-for-large-language-models-llm.md)) If you don't know what you're looking for, let AI suggest queries based on your data. This works by using the previously identified [features](./advanced.md#streams-advanced-features) in your Stream to create specific queries based on the data you have in your Stream. Then, select the suggestions that make sense to you.
13
+
-**Generate significant events with AI:**Requires a [Generative AI connector](kibana://reference/connectors-kibana/gen-ai-connectors.md). If you don't know what you're looking for, let AI suggest queries based on your data. This works by using the previously identified [features](./advanced.md#streams-advanced-features) in your Stream to create specific queries based on the data you have in your Stream. Then, select the suggestions that make sense to you.
14
14
-**Create significant events from a query:** If you know what you're looking for, write your own query to find important events.
0 commit comments