-
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
Deprecate log input in favour of filestream #28623
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:
|
@ruflin I removed the version from the log message and added more details to the PR description. |
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.
2 minor comments, overall LGTM. Approving already.
filebeat/input/log/input.go
Outdated
@@ -82,6 +85,10 @@ func NewInput( | |||
outlet channel.Connector, | |||
context input.Context, | |||
) (input.Input, error) { | |||
deprecatedNotificationOnce.Do(func() { | |||
cfgwarn.Deprecate("8.0.0", "Log input. Use Filestream input instead.") |
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.
Shouldn't this be 7.16.0?
filebeat/input/stdin/input.go
Outdated
@@ -48,6 +54,10 @@ type Input struct { | |||
// NewInput creates a new stdin input | |||
// This input contains one harvester which is reading from stdin | |||
func NewInput(cfg *common.Config, outlet channel.Connector, context input.Context) (input.Input, error) { | |||
deprecatedNotificationOnce.Do(func() { | |||
cfgwarn.Deprecate("", "Stdin input is deprecated.") |
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.
Should we add this to the changelog too?
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.
I accidentally added this file. I wanted to create a separate PR, so I only have to add a single line to the changelog.
(cherry picked from commit 97243e6)
(cherry picked from commit 97243e6)
(cherry picked from commit 97243e6) Co-authored-by: Noémi Ványi <[email protected]>
(cherry picked from commit 97243e6) Co-authored-by: Noémi Ványi <[email protected]>
…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)
Is there anything we have to be aware of when changing a log type filebeat input to a filestream input? Is there a migration or conversion we have to do or is it simply just a matter of changing "log" to "filestream" in filebeat.yml? |
What I'm aware is will the registry can handle the log to filestream migration correctly? Please advice, thanks. |
Is there anything we have to be aware of when changing a log type filebeat input to a filestream input? Is there a migration or conversion we have to do or is it simply just a matter of changing "log" to "filestream" in filebeat.yml? Please advice, thanks. |
…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 marks the log input as deprecated. As we are not in a hurry to remove the input because it possibly impacts lots of users, I omitted the version to remove from the log message. Our goal is to let users who are satisfied with the input use it as long as they would like to. However, if it is no longer working or found any issues in the input, we are asking them to move to filestream input.
Why is it important?
Everyone should move to filestream input because it is a great improvement over the old log input.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.