[7.x](backport #26115) Add new parser to filestream input: container #26221
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
botelastic
bot
added
the
needs_team
|
This pull request doesn't have a |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures
|
| Test | Results |
|---|---|
| Failed | 3 |
| Passed | 47368 |
| Skipped | 4985 |
| Total | 52356 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Extended / metricbeat-windows-7-windows-7 / ExampleWrapper – github.com/elastic/beats/v7/metricbeat/mb/module - Name:
Extended / heartbeat-windows-10-windows-10 / TestQueueRunsInOrder – github.com/elastic/beats/v7/heartbeat/scheduler/timerqueue - Name:
Extended / heartbeat-windows-7-32-windows-7-32-bit / TestQueueRunsInOrder – github.com/elastic/beats/v7/heartbeat/scheduler/timerqueue
|
This pull request is now in conflicts. Could you fix it? 🙏 |
## What does this PR do? This PR adds support for a new parser named `container`. This is the reader that powers the `container` input behind the scenes. Now it is exposed as a parser. Example configuration for reading container logs with the `filesteam` input: ```yaml type: filestream paths: - /path/to/containers/*/*.log parsers: - container: ~ ``` ### Limitations The PR does not provide feature parity with the `container` input because of the lack of support for separating the states of stdout and strerr streams. It is coming in a follow-up PR. ## Why is it important? It is a step toward supporting reading container logs from every input that supports `parsers` option. (cherry picked from commit e2449af)
kvch
force-pushed
the
mergify/bp/7.x/pr-26115
branch
from
3819537 to
a57f4a5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #26115 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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.io/