Conversation
|
This pull request does not have a backport label. Could you fix it @kvch? 🙏
NOTE: |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
This pull request is now in conflicts. Could you fix it? 🙏 |
ruflin
left a comment
There was a problem hiding this comment.
LGTM. I think it is important to note that custom beats can still be created with the generator from 7.x branch as this will work with 8.x
jsoriano
left a comment
There was a problem hiding this comment.
Looks good. Added a comment about keeping the documentation for new metricsets in Metricbeat.
Failure in docs build seems related.
| @@ -1,319 +0,0 @@ | |||
| [[creating-metricsets]] | |||
| === Creating a Metricset | |||
There was a problem hiding this comment.
This is developer documentation for Metricbeat. I think we should keep this, new metricsets may still be needed to act as new metric inputs.
jsoriano
left a comment
There was a problem hiding this comment.
LGTM, but there is still some missing reference affecting docs build.
From 8.0.0, we no longer support building custom Beats. This removes the documentation and the code as well. If someone wants to build their custom Beats, they still can based on 7.16. (cherry picked from commit c0f42bd)
…in-the-package-binareis * upstream/master: allows disable pod events enrichment with deployment name (elastic#28521) Remove Docker input from Filebeat (elastic#28817) [breaking] Make default_field: false the default for all fields (elastic#28596) Osquerybeat: Improve osquery client connect code (elastic#28848) Add crawler metrics into the stats metricset for Enterprise Search (elastic#28790) Remove the now deprecated appsearch module from metricbeat (elastic#28850) Remove Beat generators (elastic#28816) chore: upload files to Google Storage when they exist (elastic#28836) Revert "chore(ci): disable E2E tests in Beats (elastic#28715)" (elastic#28812) Deprecate generating custom Beats (elastic#28814) [Metricbeat] upgrade flatbuffers to 1.12.1 (elastic#28094) Osquerybeat: Fix restart flags after previously bad config (elastic#28827) Force ECS and JSON logging for libbeat/logp (elastic#28573) Filebeat: Error on startup for unconfigured module (elastic#28818) Deprecate log input in favour of filestream (elastic#28623) Fix some spelling mistakes (elastic#28080)
From 8.0.0, we no longer support building custom Beats. This removes the documentation and the code as well. If someone wants to build their custom Beats, they still can based on 7.16. (cherry picked from commit c0f42bd) Co-authored-by: Noémi Ványi <kvch@users.noreply.github.com>
…in-the-package-binareis * upstream/master: allows disable pod events enrichment with deployment name (elastic#28521) Remove Docker input from Filebeat (elastic#28817) [breaking] Make default_field: false the default for all fields (elastic#28596) Osquerybeat: Improve osquery client connect code (elastic#28848) Add crawler metrics into the stats metricset for Enterprise Search (elastic#28790) Remove the now deprecated appsearch module from metricbeat (elastic#28850) Remove Beat generators (elastic#28816) chore: upload files to Google Storage when they exist (elastic#28836) Revert "chore(ci): disable E2E tests in Beats (elastic#28715)" (elastic#28812) Deprecate generating custom Beats (elastic#28814) [Metricbeat] upgrade flatbuffers to 1.12.1 (elastic#28094) Osquerybeat: Fix restart flags after previously bad config (elastic#28827) Force ECS and JSON logging for libbeat/logp (elastic#28573) Filebeat: Error on startup for unconfigured module (elastic#28818) Deprecate log input in favour of filestream (elastic#28623) Fix some spelling mistakes (elastic#28080)
What does this PR do?
This PR removes Beat generators.
Why is it important?
From 8.0.0, we no longer support building custom Beats. This removes the documentation and the code as well.
If someone wants to build their custom Beats, they still can based on 7.16.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
Closes #28427