Cherry-pick #19998 to 7.x: Filebeat system tests: Ignore timestamp in fortinet and netscout#20002
Merged
adriansr merged 1 commit intoelastic:7.xfrom Jul 17, 2020
Merged
Conversation
…lastic#19998) This is because logs don't contain the year in them. (cherry picked from commit 6a9ac6f)
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
andrewkroh
approved these changes
Jul 16, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry-pick of PR #19998 to 7.x branch. Original message:
What does this PR do?
Updates Filebeat's modules test to ignore
@timestampfrom fortinet.clientendpoint and netscout.sightlineWhy is it important?
So that tests doesn't keep failing every other day, due to this datasets logs having only Day and Month fields, but no Year.
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.