Update AutoOps docs for VectorDB - #8269
Conversation
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
| - id: cloud-serverless | ||
| --- | ||
|
|
||
| # Indexing Tier view in AutoOps for {{serverless-short}} |
There was a problem hiding this comment.
@consulthys I had to make a bunch of changes on this page because it presented the main goal of the indexing tier as understanding ingest VCU consumption, and that doesn't apply to VectorDB. Can you please have a detailed look to confirm the content is technically accurate?
There was a problem hiding this comment.
Thanks the rewrite looks good 👍
| The **Indexing Tier** view shows you how many ingest 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. | ||
|
|
||
| The consumption of ingest VCUs is directly related to [autoscaling](/deploy-manage/autoscaling.md), which depends on your ingest rate and the complexity of your data. When your project scales up, more VCUs are consumed, and when your project scales down, fewer VCUs are consumed. When no data is being indexed, the indexing tier scales down to zero (with some [exceptions](https://www.elastic.co/search-labs/pt/blog/elasticsearch-serverless-pricing-vcus-ecus#minimum-ingest-vcus)). | ||
| ## Factors affecting indexing performance |
There was a problem hiding this comment.
Related to my earlier comment, please confirm if these context changes work or if I should revert this section's changes and say it only applies to Elasticsearch Serverless (like we did for the Factors affecting search VCU consumption section on the Search Tier page)
There was a problem hiding this comment.
Thanks the rewrite looks good 👍
consulthys
left a comment
consulthys
left a comment
There was a problem hiding this comment.
Looks great overall, just added a few comments
| ## AutoOps for {{serverless-full}} regions [autoops-for-serverless-full-regions] | ||
|
|
||
| [AutoOps for {{serverless-short}}](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md) is set up and enabled automatically in the following regions. The only exception is the [Search AI Lake](/deploy-manage/monitor/autoops/search-ai-lake-view-autoops-serverless.md) view, which is available in all regions across AWS, GCP, and Azure. | ||
| [AutoOps for {{serverless-short}}](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md) is set up and enabled automatically in the following regions. The only exception is the [Storage Tier](/deploy-manage/monitor/autoops/storage-tier-view-autoops-serverless.md) view, which is available in all regions across AWS, GCP, and Azure. |
There was a problem hiding this comment.
AutoOps is now fully rolled out in all Serverless regions. All future regions will have AutoOps enabled from the get go. So we probably need to rephrase this as "The only exception" makes it sound like the other tier views are not available everywhere.
|
|
||
| :::{note} | ||
| AutoOps for {{serverless-full}} is only available in supported [regions](ec-autoops-regions.md#autoops-for-serverless-full-regions), with the exception of the **Search AI Lake** view, which is available in all regions across AWS, GCP, and Azure. | ||
| AutoOps for {{serverless-full}} is only available in supported [regions](ec-autoops-regions.md#autoops-for-serverless-full-regions), with the exception of the **Storage Tier** view, which is available in all regions across AWS, GCP, and Azure. |
There was a problem hiding this comment.
AutoOps is now fully rolled out in all Serverless regions. All future regions will have AutoOps enabled from the get go. So we probably need to rephrase this as "The only exception" makes it sound like the other tier views are not available everywhere.
| The **Storage Tier** 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. | ||
|
|
||
| The **Search AI Lake** view is available in all regions across AWS, Azure, and GCP. | ||
| The **Storage Tier** view is available in all regions across AWS, Azure, and GCP. |
There was a problem hiding this comment.
AutoOps is now fully rolled out in all Serverless regions. All future regions will have AutoOps enabled from the get go. So we probably need to remove this sentence since the Storage tier is no longer an exception.
| applies_to: | ||
| serverless: | ||
| navigation_title: Search AI Lake view | ||
| navigation_title: Storage tier view |
There was a problem hiding this comment.
All the other navigation titles have a capitalized Tier (instead of tier)
|
|
||
| :::{image} /deploy-manage/images/search-tier-project-level-features-vectordb.png | ||
| :screenshot: | ||
| :alt: Screenshot showing the features in the top half of the Search Tier page for an {{es-serverless}} project |
There was a problem hiding this comment.
| :alt: Screenshot showing the features in the top half of the Search Tier page for an {{es-serverless}} project | |
| :alt: Screenshot showing the features in the top half of the Search Tier page for a {{vectordb}} project |
2 participants
Summary
This PR updates the docs for VectorDB in AutoOps + renames the Search AI Lake view to the Storage Tier.
Closes https://github.com/elastic/docs-content-internal/issues/1750
Generative AI disclosure