Cherry-pick #20273 to 7.x: [Filebeat][Fortinet] Remove pre populated event.timezone#20348
Merged
marc-gr merged 1 commit intoelastic:7.xfrom Jul 30, 2020
Merged
Cherry-pick #20273 to 7.x: [Filebeat][Fortinet] Remove pre populated event.timezone#20348marc-gr merged 1 commit intoelastic:7.xfrom
marc-gr merged 1 commit intoelastic:7.xfrom
Conversation
* Remove pre populated event.timezone * Add changelog entry * Remove processor instead of the field (cherry picked from commit b1b7860)
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
andrewkroh
approved these changes
Jul 30, 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 #20273 to 7.x branch. Original message:
What does this PR do?
Removes the pre populated
event.timezonefield.Why is it important?
Some fortinet logs do not have a
tzfield to set asevent.timezone, for this reason, when this happens, theevent.timezonewas incorrectly set to the system default instead of UTC or none (which represents UTC).With this change
event.timezonewill only be set when the log has a timezone itself.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 filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
cd x-pack/filebeat TESTING_FILEBEAT_MODULES=fortinet mage pythonIntegTest