Skip to content

[9.0](backport #43641) Update the log to filestream migration guide #43788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: 9.0
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 8, 2025

To better reflect the current state of the migration flow and give more details and context.

Also, all the steps are listed on the same page now which improves the navigation.

The preview of the migration guide is here https://docs-v3-preview.elastic.dev/elastic/beats/pull/43641/reference/filebeat/migrate-to-filestream

I'm going to follow the migration steps myself once again to make sure it still works as I describe it in this PR. Reviewers, feel free to try it out too.


This is an automatic backport of pull request #43641 done by Mergify.

To better reflect the current state of the migration flow and give
more details and context.

Also, all the steps are listed on the same page now which improves the navigation.

(cherry picked from commit 8d25694)

# Conflicts:
#	docs/reference/filebeat/_debugging_on_kibana.md
#	docs/reference/filebeat/_step_1_set_an_identifier_for_each_filestream_input.md
#	docs/reference/filebeat/_step_2_enable_the_take_over_mode.md
#	docs/reference/filebeat/_step_3_use_new_option_names.md
#	docs/reference/filebeat/_step_4.md
#	docs/reference/filebeat/howto-guides.md
#	docs/reference/toc.yml
@mergify mergify bot requested a review from a team as a code owner April 8, 2025 15:30
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Apr 8, 2025
@mergify mergify bot requested review from mauri870 and faec and removed request for a team April 8, 2025 15:30
@mergify mergify bot assigned rdner Apr 8, 2025
Copy link
Contributor Author

mergify bot commented Apr 8, 2025

Cherry-pick of 8d25694 has failed:

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

You are currently cherry-picking commit 8d256941b.
  (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)

Changes to be committed:
	modified:   docs/reference/filebeat/configuration-autodiscover-advanced.md
	modified:   docs/reference/filebeat/configuration-autodiscover-hints.md
	modified:   docs/reference/filebeat/configuration-autodiscover.md
	modified:   docs/reference/filebeat/filebeat-input-container.md
	modified:   docs/reference/filebeat/filebeat-input-log.md
	modified:   docs/reference/filebeat/migrate-to-filestream.md

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: docs/reference/filebeat/_debugging_on_kibana.md
	deleted by them: docs/reference/filebeat/_step_1_set_an_identifier_for_each_filestream_input.md
	deleted by them: docs/reference/filebeat/_step_2_enable_the_take_over_mode.md
	deleted by them: docs/reference/filebeat/_step_3_use_new_option_names.md
	deleted by them: docs/reference/filebeat/_step_4.md
	both modified:   docs/reference/filebeat/howto-guides.md
	both modified:   docs/reference/toc.yml

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

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 8, 2025
@github-actions github-actions bot added docs Team:Elastic-Agent Label for the Agent team Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Apr 8, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 8, 2025
@elasticmachine
Copy link
Collaborator

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

@rdner rdner removed request for mauri870 and faec April 9, 2025 08:37
Copy link
Contributor Author

mergify bot commented Apr 14, 2025

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

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 Team:Elastic-Agent Label for the Agent 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.

2 participants