[9.3] (backport #18595) Doc: Add failure store info to data resiliency section#19294
Open
mergify[bot] wants to merge 1 commit into
Open
[9.3] (backport #18595) Doc: Add failure store info to data resiliency section#19294mergify[bot] wants to merge 1 commit into
mergify[bot] wants to merge 1 commit into
Conversation
* Doc: Add failure store info to data resiliency section * Peer review + fix minor issues + style guide tweaks --------- Co-authored-by: Aleksandra Spilkowska <aleksandra.spilkowska@elastic.co> Co-authored-by: Aleksandra Spilkowska <96738481+alexandra5000@users.noreply.github.com> (cherry picked from commit c6a4a80)
|
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
Contributor
🤖 GitHub commentsJust comment with:
|
Contributor
🔍 Preview links for changed docs |
Contributor
Elastic Docs Style Checker (Vale)Summary: 2 suggestions found 💡 Suggestions (2): Optional style improvements. Apply when helpful.
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. |
Contributor
Author
|
This pull request has not been merged yet. Could you please review and merge it @? 🙏 |
1 similar comment
Contributor
Author
|
This pull request has not been merged yet. Could you please review and merge it @? 🙏 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related: elastic/docs-content#2881
Updates Logstash data resiliency info to include Elasticsearch failure stores, available for data streams.
Design intent: Add MVP content to Logstash to let users know that the Elasticsearch failure store exists, and if data streams are set up to use it, their events might wind up there instead of the dead letter queue (DLQ) as they have in the past.
PREVIEW: https://docs-v3-preview.elastic.dev/elastic/logstash/pull/18595/reference/queues-data-resiliency
This is an automatic backport of pull request #18595 done by Mergify.