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/search-ai-lake-view-autoops-serverless.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ navigation_title: Search AI Lake view
6
6
7
7
# Search AI Lake view in AutoOps for {{serverless-short}}
8
8
9
-
The Search AI Lake view in AutoOps for {{serverless-short}} provides visibility into the key [storage billing dimensions](/deploy-manage/monitor/autoops/autoops-for-serverless.md#storage-billing-dimensions) that drive the costs of your {{serverless-short}} projects. This view helps you understand how ingest and storage activities contribute to your storage usage costs with both high-level summaries and detailed index-level and data stream-level breakdowns.
9
+
The **Search AI Lake** view in AutoOps for {{serverless-short}} provides visibility into the key [storage billing dimensions](/deploy-manage/monitor/autoops/autoops-for-serverless.md#storage-billing-dimensions) that drive the costs of your {{serverless-short}} projects. This view helps you understand how ingest and storage activities contribute to your storage usage costs with both high-level summaries and detailed index-level and data stream-level breakdowns.
10
10
11
-
The Search AI Lake view is available in all regions across AWS, Azure, and GCP.
11
+
The **Search AI Lake** view is available in all regions across AWS, Azure, and GCP.
12
12
13
13
To get to this view, [access AutoOps](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md) in your project and then select **Search AI Lake** from the navigation menu.
14
14
@@ -18,7 +18,7 @@ To get to this view, [access AutoOps](/deploy-manage/monitor/autoops/access-auto
:alt: Screenshot showing an expanded row in the table in the bottom half of the Search AI Lake page
36
+
:alt: Screenshot showing an expanded row in the table in the bottom half of the **Search AI Lake** page
37
37
:::
38
38
39
39
Each row of the table represents a single index or data stream, providing the following information:
@@ -53,7 +53,7 @@ Also, this table is interactive and can be:
53
53
54
54
## Factors affecting storage consumption
55
55
56
-
The Search AI Lake view shows you how your project's ingest rate and storage retention changes over time. This section explains what might be causing these changes so you can make adjustments to manage your consumption.
56
+
The **Search AI Lake** view shows you how your project's ingest rate and storage retention changes over time. This section explains what might be causing these changes so you can make adjustments to manage your consumption.
57
57
58
58
The main factor that influences storage consumption is the data retention duration set on your data streams. A longer retention period means more storage space needs to be allocated to accommodate that retention.
# Search Tier view in AutoOps for {{serverless-short}}
8
8
9
-
The Search Tier view in AutoOps for {{serverless-short}} provides visibility into the consumption of search VCUs, which are a type of [compute billing dimension](/deploy-manage/monitor/autoops/autoops-for-serverless.md#compute-billing-dimensions). This view helps you understand how search activities and performance contribute to your search VCU consumption and, as a result, your project's bill.
9
+
The **Search Tier** view in AutoOps for {{serverless-short}} provides visibility into the consumption of search VCUs, which are a type of [compute billing dimension](/deploy-manage/monitor/autoops/autoops-for-serverless.md#compute-billing-dimensions). This view helps you understand how search activities and performance contribute to your search VCU consumption and, as a result, your project's bill.
10
10
11
11
This view provides both high-level project summaries and detailed index-level and data stream-level breakdowns.
12
12
13
-
To get to the Search Tier view, [access AutoOps](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md) in your project and then select **Search Tier** from the navigation menu.
13
+
To get to the **Search Tier** view, [access AutoOps](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md) in your project and then select **Search Tier** from the navigation menu.
14
14
15
15
## Project-level insights
16
16
17
17
On the **Search Tier** page, the top half of the page offers general insights at the project level.
:alt: Screenshot showing an expanded row in the data set table in the bottom half of the Search Tier page
37
+
:alt: Screenshot showing an expanded row in the data set table in the bottom half of the **Search Tier** page
38
38
:::
39
39
40
40
Each row of the table represents a single index or data stream, providing the following information:
@@ -54,7 +54,7 @@ Also, this table is interactive and can be:
54
54
* paginated to handle large sets of indices or data streams.
55
55
56
56
## Factors affecting search VCU consumption
57
-
The Search Tier view shows you how many search VCUs are consumed in your project and how your usage changes over time. This section explains the possible factors behind these changes so you can adjust them to manage your consumption.
57
+
The **Search Tier** view shows you how many search VCUs are consumed in your project and how your usage changes over time. This section explains the possible factors behind these changes so you can adjust them to manage your consumption.
58
58
59
59
The consumption of search VCUs is directly related to autoscaling. When your project is upscaled, more VCUs are consumed, and when your project is downscaled, fewer VCUs are consumed.
60
60
@@ -80,7 +80,7 @@ This could be caused by a number of reasons:
80
80
As a result, the search tier gets slowly saturated and the new search queries get queued up waiting for the long-running ones to terminate. This increase in search latency can trigger upscaling and in turn increase your search VCU consumption. Low search latency means decreased search VCU consumption.
81
81
82
82
:::{admonition} Coming soon to AutoOps
83
-
We plan to display long-running search queries in the Search Tier view so that you can learn which queries are causing increased search latency and improve their performance.
83
+
We plan to display long-running search queries in the **Search Tier** view so that you can learn which queries are causing increased search latency and improve their performance.
0 commit comments