-
Notifications
You must be signed in to change notification settings - Fork 138
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
specs/filebeat.spec.yml - Re-add lumberjack input #2511
Merged
blakerouse
merged 2 commits into
elastic:main
from
andrewkroh:bugfix/re-add-lumberjack-input
Apr 19, 2023
Merged
specs/filebeat.spec.yml - Re-add lumberjack input #2511
blakerouse
merged 2 commits into
elastic:main
from
andrewkroh:bugfix/re-add-lumberjack-input
Apr 19, 2023
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
Between v8.5.3 and v8.6.0 the lumberjack input was lost from the filebeat spec file.
andrewkroh
added
bug
Something isn't working
backport-v8.7.0
Automated backport with mergify
labels
Apr 18, 2023
andrewkroh
requested review from
michalpristas and
michel-laterman
and removed request for
a team
April 18, 2023 17:09
cmacknz
approved these changes
Apr 18, 2023
🌐 Coverage report
|
/test |
Is anything else needed on this? If not, could someone from the Agent team merge this please. |
mergify bot
pushed a commit
that referenced
this pull request
Apr 19, 2023
* specs/filebeat.spec.yml - Re-add lumberjack input Between v8.5.3 and v8.6.0 the lumberjack input was lost from the filebeat spec file. * Add changelog fragment (cherry picked from commit 8da86c6)
cmacknz
pushed a commit
that referenced
this pull request
Apr 20, 2023
* specs/filebeat.spec.yml - Re-add lumberjack input Between v8.5.3 and v8.6.0 the lumberjack input was lost from the filebeat spec file. * Add changelog fragment (cherry picked from commit 8da86c6) Co-authored-by: Andrew Kroh <[email protected]>
This was referenced Apr 20, 2023
Merged
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.
What does this PR do?
Between v8.5.3 and v8.6.0 the lumberjack input was lost from the filebeat spec file.
From v8.5.3:
elastic-agent/internal/spec/filebeat.yml
Line 49 in c0367b9
Why is it important?
The barracuda_cloudgen_firewall integration depends on this input type.
Checklist
./changelog/fragments
using the changelog toolRelated issues
Logs
From v8.6.0 when running https://docs.elastic.co/integrations/barracuda_cloudgen_firewall.