Merge branch 'main' into 2636-add-known-issue

Author: vishaangelova

deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md

@@ -27,9 +27,9 @@ For detailed {{es-serverless}} project rates, see the [{{es-serverless}} pricing
 
 {{es}} uses three VCU types:
 
-* **Indexing:** The VCUs used to index incoming documents.
-* **Search:** The VCUs used to return search results, with the latency and queries per second (QPS) you require.
-* **Machine learning:** The VCUs used to perform inference, NLP tasks, and other ML activities.
+* **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. 
+* **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, but instead 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). 
+* **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.  
 * **Tokens:** The Elastic Managed LLM is charged per 1Mn Input and Output tokens. The LLM powers all AI Search features such as Playground and AI Assistant for Search, and is enabled by default.
 
 

deploy-manage/monitor/autoops.md

@@ -56,9 +56,7 @@ AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment
 In this section, you'll find the following information:
 
 * How to [open AutoOps](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) for your deployment.
-* The contents of [AutoOps events](/deploy-manage/monitor/autoops/ec-autoops-events.md).
-* The [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into facets of your deployment.
-* [Notification settings](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md) that allow you to specify when and how to be notified.
-* [Event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) that allow you to fine-tune when events are triggered, and a method to [dismiss](/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md) certain categories of events.
-* The [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
-* Additional [frequently asked questions](/deploy-manage/monitor/autoops/ec-autoops-faq.md).
+* What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).
+* Which [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into your deployment.
+* [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
+* [Frequently asked questions](/deploy-manage/monitor/autoops/ec-autoops-faq.md) about AutoOps.

deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md

@@ -10,9 +10,4 @@ products:
 
 # Dismiss Events [ec-autoops-dismiss-event]
 
-Some events that are triggered may not require your attention immediately, or at all. Users with the appropriate permissions can choose to dismiss an event, preventing AutoOps from opening it. This action can be reversed using the Dismiss events report.
-
-:::{image} /deploy-manage/images/cloud-autoops-dismiss-events.png
-:alt: Dismiss events
-:::
-
+This page has moved. Refer to [Event actions](/deploy-manage/monitor/autoops/ec-autoops-events.md#event-actions) to learn about what you can do with events, including how to dismiss them.

deploy-manage/monitor/autoops/ec-autoops-event-settings.md

@@ -13,7 +13,7 @@ products:
 AutoOps events are triggered when specific conditions are met and are closed when those conditions are no longer satisfied. An event can be triggered by multiple conditions, and each event comes with a default setting that can be adjusted differently for each connected deployment.
 
 ::::{note}
-Only **Organization owners** can set up notifications.
+Only **Organization owners** can configure these settings.
 ::::
 
 

deploy-manage/monitor/autoops/ec-autoops-events.md

@@ -6,41 +6,63 @@ applies_to:
     ess: all
 products:
   - id: cloud-hosted
+navigation_title: Events
 ---
 
 # AutoOps events [ec-autoops-events]
 
-An AutoOps event provides a detailed analysis of a specific issue, including why it was triggered and the steps needed to resolve it. 
+AutoOps continuously monitors your {{es}} deployments by sampling performance and health metrics at 10-second intervals. This high-frequency data collection allows AutoOps to rapidly detect and diagnose issues so you can get timely notifications and resolve issues faster. 
+
+When AutoOps detects an issue, it creates an event. Events provide detailed analyses of detected issues, including why they were triggered and the steps needed to resolve them. 
+
+## Event insights
+
+You can view events on the **Deployment** page in the **Open Events** and **Events History** sections.
+
+When you select an event, a flyout appears with insights and context for the detected issue.
 
 :::{image} /deploy-manage/images/cloud-autoops-events.png
 :alt: AutoOps events
 :::
 
-The following sections provide you with comprehensive insights and context around issues, the reasons why the event was created, as well as the affected nodes and indices with high indexing activity.
+The following table describes the sections in this flyout:
 
 | Section | Description |
 | --- | --- |
-| What was detected | This section describes the reasons for which the event was created, as well as links to drill down into the issue. |
-| Recommendations | AutoOps provides a set of recommendations. The sequence of their appearance indicates the suggested order of steps to address the issue. |
-| Event duration | The time the event was detected (opened at) and the time AutoOps identified that the issue no longer exists (closed at). The closing of an event does not necessarily indicate that the customer resolved the issue, but rather that AutoOps no longer detects it. |
-| Background and impact | Provides background and context as to why an event is important, and the impact it can have on performance and stability. |
-| Event timeline chart | This chart visually represents metrics related to an issue. It appears only for events with dynamic metrics. For example, load issues will have this section, while settings-related issues will not. The event timeline chart displays just the last 15 minutes. |
-| Event severity | Events are categorized into three levels of severity - high, medium, and low - based on their potential impact on cluster performance and stability: <br><br>- **High**: Events can immediately cause significant usability, performance and stability problems.<br>- **Medium**: Events may lead to severe problems if not addressed.<br>- **Low**: Events have minimal/not urgent impact. |
+| What was detected | Describes why the event was created and provides links to drill down into the detected issue. |
+| Recommendations | Lists recommendations to address the issue and improve your cluster's overall performance. The recommendations are organized according to the suggested order of execution. |
+| Event duration | Shows when the event was opened (when AutoOps detected the issue), and if applicable, when the event was closed (when AutoOps identified that the issue no longer exists). A closed event doesn't necessarily mean that the issue is resolved, just that AutoOps no longer detects it. |
+| Background and impact | Provides background and context about why the event is important and its potential impact on cluster performance and stability. |
+| Event timeline chart | Visually presents metrics related to the issue in the last 15 minutes. This chart appears only for events with dynamic metrics. For example, load issues will have this section, but settings-related issues will not. |
+| Event severity | Categorizes the event into one of three severity levels based on its potential impact on the cluster: <br><br> **High**: Event can immediately cause significant usability, performance, and stability problems.<br> **Medium**: Event may lead to significant problems if not addressed.<br> **Low**: Event has minimal impact and is not urgent. |
+
+## Event actions
 
+In the event flyout, go to the actions menu and select from the following options:
 
-## Event settings [ec-autoops-event-customize]
+### Customize [ec-autoops-event-customize]
 
-AutoOps events are set to `open` and `close` based on triggering mechanisms that have default settings for each event type. You can modify the default settings through the Customize option in the event settings. Be cautious while changing these settings, to avoid situations where alerts fail to trigger.
+AutoOps events are opened and closed based on triggering mechanisms that have default settings for each event type. Select **Customize** to change these settings. Avoid making changes that will cause alert triggers to fail.
 
+Refer to [](ec-autoops-event-settings.md) for more details.
 
-## Notifications [ec-autoops-notifications]
+### Notifications [ec-autoops-notifications]
 
-AutoOps can send notifications to a variety of operation management tools like PagerDuty, Opsgenie, Slack, Teams and custom webhooks. Refer to [Notifications settings](ec-autoops-notifications-settings.md) for more details.
+AutoOps can send event notifications to many operation management tools like PagerDuty, Opsgenie, Slack, Teams, custom webhooks, and more. Select **Notifications** to configure these settings. 
 
+Refer to [](ec-autoops-notifications-settings.md) for more details.
 
-## Sharing events with others [ec-autoops-event-sharing]
+### Dismiss [ec-autoops-dismiss]
 
-You can easily share event information with other users by sending them a direct link to the AutoOps event using the share event link located at the top right of the event window.
+Some events may not require your attention immediately, or at all. If you are an Organization owner, you can dismiss an event to remove all events of its kind from your dashboard and prevent AutoOps from opening other similar events. Select **Dismiss** to dismiss an event.
 
-Only users with access to the AutoOps deployment from which the link was copied can view the event details.
+This action can be reversed using the **Dismiss events** report. 
+
+### Share event link [ec-autoops-event-sharing]
+
+You can share event information with other users by sending them a link to the event in AutoOps. Select **Share event link** to share the event.
+
+:::{note}
+Users can only view the event from the shared link if they have access to the AutoOps deployment from which the link was copied.
+:::
 

deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md

@@ -13,7 +13,7 @@ products:
 AutoOps can notify you of new events opened or closed through various methods and operation management tools. With a customizable mechanism, you can specify which events you want to be notified about, how you wish to receive these notifications, and their frequency.
 
 ::::{note}
-Only organization owners can configure these settings.
+Only **Organization owners** can configure these settings.
 ::::
 
 

deploy-manage/toc.yml

@@ -661,6 +661,9 @@ toc:
         children:
           - file: monitor/autoops/ec-autoops-how-to-access.md
           - file: monitor/autoops/ec-autoops-events.md
+            children:
+              - file: monitor/autoops/ec-autoops-event-settings.md
+              - file: monitor/autoops/ec-autoops-notifications-settings.md
           - file: monitor/autoops/views.md
             children:
               - file: monitor/autoops/ec-autoops-overview-view.md
@@ -669,9 +672,7 @@ toc:
               - file: monitor/autoops/ec-autoops-index-view.md
               - file: monitor/autoops/ec-autoops-shards-view.md
               - file: monitor/autoops/ec-autoops-template-optimizer.md
-          - file: monitor/autoops/ec-autoops-notifications-settings.md
-          - file: monitor/autoops/ec-autoops-event-settings.md
-          - file: monitor/autoops/ec-autoops-dismiss-event.md
+          - hidden: monitor/autoops/ec-autoops-dismiss-event.md
           - file: monitor/autoops/ec-autoops-regions.md
           - file: monitor/autoops/ec-autoops-faq.md
           - hidden: monitor/autoops/cc-autoops-as-cloud-connected.md

explore-analyze/machine-learning/nlp/ml-nlp-model-ref.md

@@ -15,9 +15,7 @@ products:
 The minimum dedicated ML node size for deploying and using the {{nlp}} models is 16 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself.
 ::::
 
-The {{stack-ml-features}} support transformer models that conform to the standard BERT model interface and use the WordPiece tokenization algorithm.
-
-The current list of supported architectures is:
+The {{stack-ml-features}} support transformer models with the following architectures:
 
 * BERT
 * BART