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: explore-analyze/elastic-inference/eis.md
+8-24Lines changed: 8 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,64 +9,48 @@ applies_to:
9
9
10
10
# Elastic {{infer-cap}} Service [elastic-inference-service-eis]
11
11
12
-
The Elastic {{infer-cap}} Service (EIS) enables you to leverage AI-powered search as a service without deploying a model in your cluster.
12
+
The Elastic {{infer-cap}} Service (EIS) enables you to leverage AI-powered search as a service without deploying a model in your environment.
13
13
With EIS, you don't need to manage the infrastructure and resources required for {{ml}} {{infer}} by adding, configuring, and scaling {{ml}} nodes.
14
14
Instead, you can use {{ml}} models for ingest, search, and chat independently of your {{es}} infrastructure.
15
15
16
16
## AI features powered by EIS [ai-features-powered-by-eis]
17
17
18
18
* Your Elastic deployment or project comes with a default [`Elastic Managed LLM` connector](https://www.elastic.co/docs/reference/kibana/connectors-kibana/elastic-managed-llm). This connector is used in the AI Assistant, Attack Discovery, Automatic Import and Search Playground.
19
19
20
-
* You can use [ELSER](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md) to perform semantic search as a service (ELSER on EIS). {applies_to}`stack: preview 9.1` {applies_to}`serverless: preview`
20
+
* You can use [ELSER](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md) to perform semantic search as a service (ELSER on EIS). {applies_to}`stack: preview 9.1, ga 9.2` {applies_to}`serverless: ga`
21
21
22
22
## Region and hosting [eis-regions]
23
23
24
24
Requests through the `Elastic Managed LLM` are currently proxying to AWS Bedrock in AWS US regions, beginning with `us-east-1`.
25
25
The request routing does not restrict the location of your deployments.
26
26
27
-
ELSER requests are managed by Elastic's own EIS infrastructure and are also hosted in AWS US regions, beginning with `us-east-1`. All Elastic Cloud hosted deployments and serverless projects in any CSP and region can access the endpoint. As we expand the service to Azure and GCP and more regions, we will automatically route requests to the same CSP and closest region the Elaticsearch cluster is hosted on.
28
27
28
+
ELSER requests are managed by Elastic's own EIS infrastructure and are also hosted in AWS US regions, beginning with `us-east-1`. All Elastic Cloud hosted deployments and serverless projects in any CSP and region can access the endpoint. As we expand the service to Azure and GCP and more regions, we will automatically route requests to the same CSP and closest region the Elaticsearch cluster is hosted on.
29
29
30
30
## ELSER via Elastic {{infer-cap}} Service (ELSER on EIS) [elser-on-eis]
31
31
32
32
```{applies_to}
33
-
stack: preview 9.1
34
-
serverless: preview
33
+
stack: preview 9.1, ga 9.2
34
+
serverless: ga
35
35
```
36
36
37
-
ELSER on EIS enables you to use the ELSER model on GPUs, without having to manage your own ML nodes. We expect significantly better performance for throughput and consistent search latency as compared to ML nodes, and will continue to benchmark, remove limitations and address concerns as we move towards General Availability.
37
+
ELSER on EIS enables you to use the ELSER model on GPUs, without having to manage your own ML nodes. We expect better performance for ingest throughput than ML nodes and equivalent performance for search latency. We will continue to benchmark, remove limitations and address concerns.
38
38
39
39
### Using the ELSER on EIS endpoint
40
40
41
41
You can now use `semantic_text` with the new ELSER endpoint on EIS. To learn how to use the `.elser-2-elastic` inference endpoint, refer to [Using ELSER on EIS](elasticsearch://reference/elasticsearch/mapping-reference/semantic-text.md#using-elser-on-eis).
42
42
43
43
#### Get started with semantic search with ELSER on EIS
44
-
[Semantic Search with `semantic_text`](/solutions/search/semantic-search/semantic-search-semantic-text.md) has a detailed tutorial on using the `semantic_text` field and using the ELSER endpoint on EIS instead of the default endpoint. This is a great way to get started and try the new endpoint.
45
-
46
-
### Limitations
47
-
48
-
While we do encourage experimentation, we do not recommend implementing production use cases on top of this feature while it is in Technical Preview.
49
44
50
-
#### Uptime
51
-
52
-
There are no uptime guarantees during the Technical Preview.
53
-
While Elastic will address issues promptly, the feature may be unavailable for extended periods.
54
-
55
-
#### Throughput and latency
45
+
[Semantic Search with `semantic_text`](/solutions/search/semantic-search/semantic-search-semantic-text.md) has a detailed tutorial on using the `semantic_text` field and using the ELSER endpoint on EIS instead of the default endpoint. This is a great way to get started and try the new endpoint.
56
46
57
-
{{infer-cap}} throughput via this endpoint is expected to exceed that of {{infer}} operations on an ML node.
58
-
However, throughput and latency are not guaranteed.
59
-
Performance may vary during the Technical Preview.
47
+
### Limitations
60
48
61
49
#### Batch size
62
50
63
51
Batches are limited to a maximum of 16 documents.
64
52
This is particularly relevant when using the [_bulk API](https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-bulk) for data ingestion.
65
53
66
-
#### Rate limits
67
-
68
-
Rate limit for search and ingest is currently at 500 requests per minute. This allows you to ingest approximately 8000 documents per minute at 16 documents per request.
69
-
70
54
## Pricing
71
55
72
56
All models on EIS incur a charge per million tokens. The pricing details are at our [Pricing page](https://www.elastic.co/pricing/serverless-search) for the Elastic Managed LLM and ELSER.
When you install or upgrade {{agent}}, new alert rules are created automatically. You can configure and customize out-of-the-box alerts to get them up and running quickly.
18
+
19
+
::::{note}
20
+
The built-in alerts feature for {{agent}} is available only for some subscription levels. The license (or a trial license) must be in place before you install or upgrade {{agent}} before this feature is available.
21
+
22
+
Refer [Elastic subscriptions](https://www.elastic.co/subscriptions) for more information.
23
+
::::
24
+
25
+
In {{kib}}, you can enable out-of-the-box rules pre-configured with reasonable defaults to provide immediate value for managing agents.
26
+
You can use [ES|QL](/explore-analyze/discover/try-esql.md) to author conditions for each rule.
27
+
28
+
Connectors are not added to rules automatically, but you can attach a connector to route alerts to your platform of choice -- Slack or email, for example.
29
+
In addition, you can add filters for policies, tags, or hostnames to scope alerts to specific sets of agents
30
+
31
+
You can find these rules in **Stack Management** > **Alerts and Insights** > **Rules**.
32
+
33
+
34
+
## Alert templates assets for integrations [alert-templates]
35
+
36
+
Some integration packages include alerting rule template assets that provide pre-made definitions of alerting rules. You can use the templates to create your own custom alerting rules that you can enable and fine tune.
37
+
38
+
When you click a template, you get a pre-filled rule creation form. You can define and adjust values, set up connectors, and define rule actions to create your custom alerting rule.
39
+
40
+
You can see available templates in the **integrations/detail/<package>/assets** view.
Copy file name to clipboardExpand all lines: reference/fleet/manage-integrations.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,26 +12,28 @@ products:
12
12
13
13
# Manage {{agent}} integrations [integrations]
14
14
15
-
{{agent}} integrations provide a unified way to collect data from apps and services and to protect systems from security threats.
16
-
17
-
Integrations are available for a wide array of services and platforms. To browse the full list of available integrations, go to the **Integrations** page in {{kib}}, or visit [Elastic Integrations](integration-docs://reference/index.md).
15
+
{{agent}} integrations provide a simple, unified way to collect data from popular apps and services, and protect systems from security threats.
16
+
Integrations are available for a wide array of popular services and platforms. To see the full list, go to the **Integrations** page in {{kib}}, or visit [Elastic Integrations](integration-docs://reference/index.md).
18
17
19
18
{{agent}} integrations based on the [Elastic Common Schema](ecs://reference/index.md) (ECS) come prepackaged with assets that support your observability needs:
20
19
21
20
* Data ingestion, storage, and transformation rules
22
21
* Configuration options
22
+
* Alert templates to enable users to quickly set up custom alerting rules (available in some integrations) {applies_to}`stack: ga 9.2`
23
23
* Pre-built, custom dashboards and visualizations
24
24
* Documentation
25
25
26
26
{applies_to}`stack: preview 9.2.0` {{fleet}} also supports installing {{agent}} integration packages for collecting and visualizing OpenTelemetry data. For more information, refer to [Collect OpenTelemetry data with {{agent}} integrations](/reference/fleet/otel-integrations.md).
27
27
28
+
Note that the **Integrations** app in {{kib}} needs access to the public {{package-registry}} to discover integrations. If your deployment has network restrictions, you can [deploy your own self-managed {{package-registry}}](/reference/fleet/air-gapped.md#air-gapped-diy-epr).
29
+
28
30
::::{note}
29
-
Some integrations may function differently across different spaces, and some might only work in the default space. For any space-related considerations, review the documentation for the specific integration.
31
+
Some integrations may function differently across different spaces, with some working only in the default space. Review the documentation specific to your integration for any space-related considerations.
30
32
::::
31
33
32
-
## Integration actions [integration-actions]
34
+
## Work with integrations [work-with-integrations]
33
35
34
-
The following table shows the main actions you can perform in the **Integrations** app in {{kib}}. You can perform some of these actions from other places in {{kib}}, too.
36
+
You can perform a variety of actions in the **Integrations** app in {{kib}}. Some of these actions are also available from other places in {{kib}}.
35
37
36
38
| User action | Result |
37
39
| --- | --- |
@@ -42,10 +44,6 @@ The following table shows the main actions you can perform in the **Integrations
42
44
|[View integration assets](/reference/fleet/view-integration-assets.md)| View the {{kib}} assets installed for a specific integration. |
43
45
|[Upgrade an integration](/reference/fleet/upgrade-integration.md)| Upgrade an integration to the latest version. |
44
46
45
-
::::{note}
46
-
The **Integrations** app in {{kib}} needs access to the public {{package-registry}} to discover integrations. If your deployment has network restrictions, you can [deploy your own self-managed {{package-registry}}](/reference/fleet/air-gapped.md#air-gapped-diy-epr).
Once you've started using integrations to ingest data, you can customize how that data is managed over time. Refer to [Index lifecycle management](/reference/fleet/data-streams.md#data-streams-ilm) to learn more.
51
-
:::
49
+
After you've started using integrations to ingest data, you can customize how the data is managed over time. Refer to [Index lifecycle management](/reference/fleet/data-streams.md#data-streams-ilm) to learn more.
0 commit comments