Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Dec 3, 2025

Proposed commit message

Adds a warning to the Elasticsearch output docs stating that all hosts must be part of the same cluster.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Screenshot

Screenshot 2025-11-26 at 2 39 20 PM
This is an automatic backport of pull request #47791 done by [Mergify](https://mergify.com).

(cherry picked from commit 56a35a9)

# Conflicts:
#	docs/reference/auditbeat/elasticsearch-output.md
#	docs/reference/filebeat/elasticsearch-output.md
#	docs/reference/heartbeat/elasticsearch-output.md
#	docs/reference/metricbeat/elasticsearch-output.md
#	docs/reference/packetbeat/elasticsearch-output.md
#	docs/reference/winlogbeat/elasticsearch-output.md
@mergify mergify bot requested a review from a team as a code owner December 3, 2025 18:42
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Dec 3, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 3, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Dec 3, 2025

Cherry-pick of 56a35a9 has failed:

On branch mergify/bp/8.19/pr-47791
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit 56a35a93f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/reference/auditbeat/elasticsearch-output.md
	deleted by us:   docs/reference/filebeat/elasticsearch-output.md
	deleted by us:   docs/reference/heartbeat/elasticsearch-output.md
	deleted by us:   docs/reference/metricbeat/elasticsearch-output.md
	deleted by us:   docs/reference/packetbeat/elasticsearch-output.md
	deleted by us:   docs/reference/winlogbeat/elasticsearch-output.md

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@github-actions github-actions bot added docs Team:Docs Label for the Observability docs team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team skip-changelog labels Dec 3, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Dec 3, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

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

Labels

backport conflicts There is a conflict in the backported pull request docs skip-changelog Team:Docs Label for the Observability docs team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants