Skip to content
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

[8.5](backport #36157) [DOCS] Advise users to migrate from Filebeat to Elastic Agent #36196

Merged
merged 1 commit into from
Aug 3, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 1, 2023

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


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

## What does this PR do?

Adds a note to
[Modules](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-modules.html)
to advise users to migrate to Elastic Agent.

Preview:
[Modules](https://beats_36157.docs-preview.app.elstc.co/guide/en/beats/filebeat/master/filebeat-modules.html)

## Why is it important?

While Filebeat modules are still supported, we do not typically apply
bug fixes or enhancements to these modules, or ship any new modules. Our
focus is now entirely on Elastic Agent integrations.

## Checklist

<!-- Mandatory
Add a checklist of things that are required to be reviewed in order to
have the PR approved

List here all the items you have verified BEFORE sending this PR. Please
DO NOT remove any item, striking through those that do not apply. (Just
in case, strikethrough uses two tildes. ~~Scratch this.~~)
-->

- [x] My code follows the style guidelines of this project
~~- [ ] I have commented my code, particularly in hard-to-understand
areas~~ N/A
- [x] I have made corresponding changes to the documentation
~~- [ ] I have made corresponding change to the default configuration
files~~ N/A
~~- [ ] I have added tests that prove my fix is effective or that my
feature works~~ N/A
~~- [ ] I have added an entry in `CHANGELOG.next.asciidoc` or
`CHANGELOG-developer.next.asciidoc`.~~ N/A

## Related issues

* Resolves elastic/security-docs#3576

---------

Co-authored-by: Janeen Mikell Roberts <[email protected]>
Co-authored-by: David Kilfoyle <[email protected]>
(cherry picked from commit e1267be)
@mergify mergify bot added the backport label Aug 1, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 1, 2023
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-08-01T13:19:48.062+0000

  • Duration: 12 min 31 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@natasha-moore-elastic natasha-moore-elastic added the Team:Docs Label for the Observability docs team label Aug 1, 2023
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Aug 1, 2023
@jrodewig jrodewig merged commit 285eca6 into 8.5 Aug 3, 2023
@jrodewig jrodewig deleted the mergify/bp/8.5/pr-36157 branch August 3, 2023 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Docs Label for the Observability docs team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants