Cherry-pick #20386 to 7.x: Add event.ingested to all Filebeat modules#20483
Merged
andrewkroh merged 2 commits intoelastic:7.xfrom Aug 11, 2020
Merged
Cherry-pick #20386 to 7.x: Add event.ingested to all Filebeat modules#20483andrewkroh merged 2 commits intoelastic:7.xfrom
andrewkroh merged 2 commits intoelastic:7.xfrom
Conversation
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
The event.ingested field defines time at which the event was ingested to Elasticsearch and it added by the Ingest Node pipeline. This field is important when trying to build alerts for activities that may have been reported long after they occurred (@timestamp is much older than event.ingested). This might happen if an agent was offline for a period of time or the processing was delayed. This adds a test to ensure all modules create event.ingested. Use Filebeat read time instead of ingest time as event.created in Zeek. Closes elastic#20073 (cherry picked from commit 829c3b7)
0d94954 to
288b7c3
Compare
kaiyan-sheng
approved these changes
Aug 10, 2020
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
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 #20386 to 7.x branch. Original message:
What does this PR do?
The event.ingested field defines time at which the event was ingested to Elasticsearch
and it added by the Ingest Node pipeline.
This adds a test to ensure all modules create event.ingested.
Why is it important?
This field is important when trying to build
alerts for activities that may have been reported long after they occurred (@timestamp is
much older than event.ingested). This might happen if an agent was offline for a period
of time or the processing was delayed.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
setprocessors for event.ingestedRelated issues