Skip to content

[9.3] (backport #18595) Doc: Add failure store info to data resiliency section#19294

Open
mergify[bot] wants to merge 1 commit into
9.3from
mergify/bp/9.3/pr-18595
Open

[9.3] (backport #18595) Doc: Add failure store info to data resiliency section#19294
mergify[bot] wants to merge 1 commit into
9.3from
mergify/bp/9.3/pr-18595

Conversation

@mergify

@mergify mergify Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

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.

* 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)
@mergify mergify Bot added the backport label Jul 10, 2026
@cla-checker-service

Copy link
Copy Markdown

❌ Author of the following commits did not sign a Contributor Agreement:
0e57d67

Please, read and sign the above mentioned agreement if you want to contribute to this project

@github-actions

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
  • run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

@github-actions github-actions Bot added the docs label Jul 10, 2026
@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 2 suggestions found

💡 Suggestions (2): Optional style improvements. Apply when helpful.
File Line Rule Message
docs/reference/queues-data-resiliency.md 27 Elastic.WordChoice Consider using 'cannot' instead of 'unable', unless the term is in the UI.
docs/reference/queues-data-resiliency.md 27 Elastic.WordChoice Consider using 'efficiently' instead of 'easily', unless the term is in the UI.

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.

@mergify

mergify Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor Author

This pull request has not been merged yet. Could you please review and merge it @? 🙏

1 similar comment
@mergify

mergify Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

This pull request has not been merged yet. Could you please review and merge it @? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant