(Doc+) Link intro doc to parent objects - part3 #113545
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stefnestor
added
>bug
>enhancement
>docs
|
Documentation preview: |
elasticsearchmachine
added
external-contributor
|
Pinging @elastic/es-docs (Team:Docs) |
mark-vieira
added
auto-backport
|
hey stef - this page was recently rewritten. take a look at the new one and let us know if it needs additional links. note that the intent is that this is the core conceptual documentation for a lot of these items, so I suspect we wouldn't want to link deeper into the docs in most cases. |
shainaraskas
requested changes
Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 howdy, team!
(Enhancement) Follow-up to (#111951, #113541), links the Elasticsearch intro pages to their parent objects.
(Bug) Also updates the shard section which is outdated for 8.0+, related https://github.com/elastic/support-analyzer-alerts/issues/213. Vs current guidelines are 10-50GB and 3000 shards per 1GB master heap.