[8.16](backport #41296) system-logs input ignores folders and add tests #41382
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.
Note fore reviewers
This PR is not labelled as a bug, but it covers a corner case that wasn't covered before and adds tests, hence I believe it can fall into the "bugfix" category and be backported to 8.16 making it into the 8.16.0 release.
Proposed commit message
The system-logs input now does not count folders as an "existing file"
when looking for files to decide between the journald and log inputs.
Unit and integration tests are added for the system-logs input.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.## Disruptive User Impact## Author's ChecklistHow to test this PR locally
Ideally run those tests on Linux so all of them will execute
Related issues
system-logsinput #41259## Use cases## Screenshots## LogsThis is an automatic backport of pull request #41296 done by [Mergify](https://mergify.com).