Doc: Add failure store info to data resiliency section#18595
Open
karenzone wants to merge 1 commit intoelastic:mainfrom
Open
Doc: Add failure store info to data resiliency section#18595karenzone wants to merge 1 commit intoelastic:mainfrom
karenzone wants to merge 1 commit intoelastic:mainfrom
Conversation
karenzone
force-pushed
the
failure-store
branch
from
bcceb5a to
727692a
Compare
karenzone
added
backport-9.1
karenzone
force-pushed
the
failure-store
branch
from
727692a to
37c6fc5
Compare
Contributor
🔍 Preview links for changed docs |
karenzone
force-pushed
the
failure-store
branch
from
37c6fc5 to
87272ae
Compare
Contributor
Author
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
1 participant
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