Conversation
Relates to #5164
✅ Vale Linting ResultsNo 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. |
| **Management free:** Elastic manages the underlying Elastic cluster, so you can focus on your data. With serverless projects, Elastic is responsible for automatic upgrades, data backups, and business continuity. | ||
|
|
||
| **Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. | ||
| **Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. Some [project-level limits](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits) apply to ensure performance and stability. Certain limits are adjustable by request. |
There was a problem hiding this comment.
@yetanothertw , at the moment, in event of a customer exceeding this limit, they will receive a 400 bad request error for their REST calls. The exception will contain a link to this
/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits
This link is coded in https://github.com/elastic/elasticsearch/blob/main/server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt#L41.
I will follow up with code change to point to this new URL.
There was a problem hiding this comment.
Many thanks!
I think this page is a good place to land on for learn more information about Serverless in case the user needs it.
There was a problem hiding this comment.
@zhubotang-wq, should we wait until the code change is complete before we merge the docs? Or is it okay to merge now?
There was a problem hiding this comment.
@yetanothertw let's please wait - we're still finalizing a decision on the actual number of indices to apply as the limit.
There was a problem hiding this comment.
No worries, @pete-naylor. Please let me know when you're ready 👍
zhubotang-wq
left a comment
zhubotang-wq
left a comment
There was a problem hiding this comment.
LGTM. I have no issues with it.
deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
Outdated
Show resolved
Hide resolved
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
here too? https://www.elastic.co/docs/manage-data/data-store/index-basics
trying to think of where users will look
leemthompo
left a comment
leemthompo
left a comment
There was a problem hiding this comment.
changes to manage-data/data-store/index-basics.md LGTM
Normalize opentelemetry:///reference/motlp.md to opentelemetry://reference/motlp.md for consistency with other opentelemetry crosslinks in the file. Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Claude <noreply@anthropic.com>
deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
Outdated
Show resolved
Hide resolved
kilfoyle
left a comment
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM! 🥕
Just one small suggestion.
…ticsearch-offerings.md Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
7 participants
Summary
Relates to #5164 and proposes an alternative and more integrated way to add index limits details into the Serverless docs.
Generative AI disclosure