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/cloud-organization/billing/elasticsearch-billing-dimensions.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
@@ -33,7 +33,7 @@ For detailed {{es-serverless}} project rates, refer to the [{{es-serverless}} pr
33
33
***Indexing:** The VCUs used to index incoming documents. Indexing VCUs account for compute resources consumed for ingestion. This is based on ingestion rate and amount of data ingested at any given time. Transforms and ingest pipelines also contribute to ingest VCU consumption.
34
34
***Search:** The VCUs used to return search results with the latency and queries per second (QPS) you require. Search VCUs are calculated as a factor of the compute resources needed to run search queries, search throughput, and latency. Search VCUs are not charged per search request. Instead, they are a factor of the compute resources that scale up and down based on amount of searchable data, search load (QPS), and performance (latency and availability).
35
35
***Machine learning:** The VCUs used to perform inference, NLP tasks, and other ML activities. ML VCUs are a factor of the models deployed and number of ML operations such as inference for search and ingest. ML VCUs are typically consumed for generating embeddings during ingestion and during semantic search or reranking.
36
-
***Tokens:** The Elastic Managed LLM is charged per 1 million input and output tokens. The LLM powers all AI Search features such as Playground and AI Assistant for Searchand is enabled by default.
36
+
***Tokens:**[The Elastic Inference Service](https://www.elastic.co/docs/explore-analyze/elastic-inference/eis) is charged based on tokens used with machine learning models. For embeddings and rerankers, usage is billed per million input tokens sent to the models. For LLMs, this is either per 1 million input or per 1 million output tokens. Elastic Managed LLMs can power all AI Search features (such as Playground and AI Assistant for Search), as well as features in the Security and Observability products, and are enabled by default.
37
37
38
38
## Data storage and billing [elasticsearch-billing-information-about-the-search-ai-lake-dimension-gb]
Copy file name to clipboardExpand all lines: manage-data/data-store/index-basics.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ Investigate your indices and perform operations from the **Indices** view.
110
110
111
111
* Enable **Include hidden indices** to view the full set of indices, including backing indices for [data streams](/manage-data/data-store/data-streams.md).
112
112
113
-
* To filter the list of indices, use the search bar or click a badge. Badges indicate if an index is a [follower index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ccr-follow), a [rollup index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-rollup-get-rollup-index-caps), or [frozen](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-unfreeze).
113
+
* To filter the list of indices, use the search bar or click a badge. Badges indicate if an index is a [follower index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ccr-follow) or a [rollup index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-rollup-get-rollup-index-caps).
114
114
::::
115
115
116
116
::::{tab-item} {{stack}}
@@ -131,7 +131,7 @@ Investigate your indices and perform operations from the **Indices** view.
131
131
132
132
* Enable **Include hidden indices** to view the full set of indices, including backing indices for [data streams](/manage-data/data-store/data-streams.md).
133
133
134
-
* To filter the list of indices, use the search bar or click a badge. Badges indicate if an index is a [follower index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ccr-follow), a [rollup index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-rollup-get-rollup-index-caps), or [frozen](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-unfreeze).
134
+
* To filter the list of indices, use the search bar or click a badge. Badges indicate if an index is a [follower index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ccr-follow) or a [rollup index](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-rollup-get-rollup-index-caps).
Copy file name to clipboardExpand all lines: solutions/observability/observability-ai-assistant.md
+33-5Lines changed: 33 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ To set up or use AI assistant, you need the following:
40
40
41
41
* An [LLM connector](/solutions/security/ai/set-up-connectors-for-large-language-models-llm.md)
42
42
43
-
* (Optional) To use [knowledge base](#obs-ai-add-data):
43
+
* (Optional) To use [knowledge base](#obs-ai-add-data):
44
44
- A 4 GB {{ml}} node
45
45
:::{note}
46
46
In {{ecloud}} or {{ece}}, if you have {{ml}} autoscaling enabled, {{ml}} nodes automatically start when using the knowledge base and AI Assistant. Therefore using these features incurs additional costs.
@@ -360,6 +360,38 @@ Additional functions are available when your cluster has APM data:
360
360
`get_apm_services_list`
361
361
: Get the list of monitored services, their health statuses, and alerts.
362
362
363
+
#### Share conversations
364
+
365
+
Conversations that you start with AI Assistant are private by default and not visible to other users in the space. Sharing conversations lets everyone in the space see what you've already asked or learned, making it easier to collaborate.
366
+
367
+
To change the visibility of a conversation:
368
+
369
+
1. Select the **Private** / **Shared** badge next to the conversation's title
370
+
1. Use the dropdown menu to define the conversation's visibility.
:alt: AI Assistant chat with the sharing status dropdown open
374
+
:screenshot:
375
+
:::
376
+
377
+
After sharing a conversation, you can copy its URL and send the link to your team:
378
+
379
+
1. Open an AI Assistant chat.
380
+
1. Open the **Conversation actions** ({icon}`boxes_vertical`) menu.
381
+
1. Select **Copy URL**.
382
+
383
+
When someone shares a chat with you, you can view it, but you can't edit or continue the conversation. To continue the conversation where your colleague left off, duplicate the conversation.
384
+
385
+
To duplicate a conversation:
386
+
387
+
1. Open an AI Assistant chat.
388
+
1. Open the **Conversation actions** ({icon}`boxes_vertical`) menu.
389
+
1. Select **Duplicate**.
390
+
391
+
#### Archive conversations
392
+
393
+
The owner of a conversation can archive it by selecting **Archive** from the **Conversation actions** ({icon}`boxes_vertical`) menu. Once archived, a conversation can't be continued or edited unless it is unarchived. Unarchive a conversation by selecting **Unarchive** from the **Conversation actions** ({icon}`boxes_vertical`) menu.
394
+
363
395
### Use contextual prompts [obs-ai-prompts]
364
396
365
397
AI Assistant contextual prompts throughout {{observability}} provide the following information:
@@ -413,10 +445,6 @@ When the alert fires, contextual details about the event—such as when the aler
413
445
:screenshot:
414
446
:::
415
447
416
-
::::{important}
417
-
Conversations created by the AI Assistant are public and accessible to every user with permissions to use the assistant.
418
-
::::
419
-
420
448
It might take a minute or two for the AI Assistant to process the message and create the conversation.
421
449
422
450
Note that overly broad prompts may result in the request exceeding token limits. For more information, refer to [Token limits](#obs-ai-token-limits). Also, attempting to analyze several alerts in a single connector execution may cause you to exceed the function call limit. If this happens, modify the message specified in the connector configuration to avoid exceeding limits.
0 commit comments