adding support for epoch in seconds #19512
Merged
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
|
Pinging @elastic/siem (Team:SIEM) |
botelastic
bot
added
needs_team
6 tasks
marc-gr
approved these changes
Jun 30, 2020
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
Seems like a small issue for the date formatter to compare between UNIX and UNIX_MS in the same processor, so trying to fix that, let's wait for all tests to complete first now, last one failed because one date field changed |
P1llus
force-pushed
the
filebeat_fortinet_module_dateformat_fix
branch
from
73c6c22 to
1062936
Compare
|
jenkins run tests |
1 similar comment
|
jenkins run tests |
adriansr
pushed a commit
to adriansr/beats
that referenced
this pull request
Jul 14, 2020
What does this PR do? Certain versions of fortinet handles the eventtime field in seconds instead of milliseconds, added support for that datetime format Why is it important? Adds support for certain fields that can be calculated incorrectly on certain versions. (cherry picked from commit f367f79)
5 tasks
adriansr
added a commit
that referenced
this pull request
Jul 14, 2020
What does this PR do? Certain versions of fortinet handles the eventtime field in seconds instead of milliseconds, added support for that datetime format Why is it important? Adds support for certain fields that can be calculated incorrectly on certain versions. (cherry picked from commit f367f79) Co-authored-by: Marius Iversen <[email protected]>
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this pull request
Oct 14, 2020
What does this PR do? Certain versions of fortinet handles the eventtime field in seconds instead of milliseconds, added support for that datetime format Why is it important? Adds support for certain fields that can be calculated incorrectly on certain versions.
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?
Certain versions of fortinet handles the eventtime field in seconds instead of milliseconds, added support for that datetime format
Why is it important?
Adds support for certain fields that can be calculated incorrectly on certain versions.
Checklist
- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.