-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[DOCS] Advise users to migrate from Filebeat to Elastic Agent #36157
[DOCS] Advise users to migrate from Filebeat to Elastic Agent #36157
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @natasha-moore-elastic - I left a small tweak to @jamiehynds' suggestion. Please make sure all the attributes {surrounded in {}
) render properly in the HTML preview. Thanks!
@jamiehynds any idea of how far back you'd like us to backport this? |
@nimarezainia @SubhrataK @amitkanfer can you please review before we go ahead with this PR? The goal is to drive users towards agent integrations over Beats modules and raise awareness/recommend agent integrations. While this PR covers Filebeat, we'll probably have to do similar text for other modules pages for the other Beats too. Want to ensure we're aligned across ingest, security and o11y before proceeding. |
@jamiehynds I am fine with adding the note (with the text, as suggested by you). |
+1 from me. |
is it possible to backport to 8.0 to ensure alignment across all 8.x releases? Also, could we expand this across all the Beats? I can raise issues for each Beat if needed (e.g. Winlogbeat, Packetbeat, Auditbeat). The text will differ slightly across each Beat. |
Hi @jamiehynds yes. Typically, these docs are handled by the Fleet team I believe, but @natasha-moore-elastic is happy to make these changes for the rest of the Beats docs. Can you please open issues for the rest of them in the |
thank you @natasha-moore-elastic adding @kilfoyle for awareness. |
@jamiehynds @jmikell821, if everyone's happy with the updated text, can I get an approval, please? Thanks! |
Co-authored-by: David Kilfoyle <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
Thanks @natasha-moore-elastic!
## 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)
## 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)
## 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)
## 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)
## 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)
## 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)
## 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)
…o Elastic Agent (#36194) Co-authored-by: natasha-moore-elastic <[email protected]>
…o Elastic Agent (#36196) Co-authored-by: natasha-moore-elastic <[email protected]>
…o Elastic Agent (#36197) Co-authored-by: natasha-moore-elastic <[email protected]>
…o Elastic Agent (#36200) This is an automatic backport of pull request #36157 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). 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](https://dashboard.mergify.com) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details> Co-authored-by: natasha-moore-elastic <[email protected]>
…o Elastic Agent (#36199) This is an automatic backport of pull request #36157 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). 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](https://dashboard.mergify.com) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details> Co-authored-by: natasha-moore-elastic <[email protected]>
…o Elastic Agent (#36198) This is an automatic backport of pull request #36157 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). 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](https://dashboard.mergify.com) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details> Co-authored-by: natasha-moore-elastic <[email protected]>
…o Elastic Agent (#36195) This is an automatic backport of pull request #36157 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). 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](https://dashboard.mergify.com) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details> Co-authored-by: natasha-moore-elastic <[email protected]>
…c#36157) ## 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]>
What does this PR do?
Adds a note to Modules to advise users to migrate to Elastic Agent.
Preview: Modules
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
- [ ] I have commented my code, particularly in hard-to-understand areasN/A- [ ] I have made corresponding change to the default configuration filesN/A- [ ] I have added tests that prove my fix is effective or that my feature worksN/A- [ ] I have added an entry inN/ACHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues