-
Notifications
You must be signed in to change notification settings - Fork 431
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
Add event.start and event.end #185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a changelog entry?
fields.yml
Outdated
@@ -491,6 +494,20 @@ | |||
|
|||
In case the two timestamps are identical, @timestamp should be used. | |||
|
|||
- name: start | |||
level: core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest to put both these values in extended for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but agree that they should be introduced as extended first.
`event.start` and `event.end` are date fields that demarcate the beginning and end, respectively, of an activity. For example in a network flow the event.start is time time of the first packet in the flow and `event.end` time the time of the last observed packet in the flow. The `event.duration` value is then computed as the difference between end and start times.
30627c1
to
614dd7b
Compare
Updated with:
|
`event.start` and `event.end` are date fields that demarcate the beginning and end, respectively, of an activity. For example in a network flow the event.start is time time of the first packet in the flow and `event.end` time the time of the last observed packet in the flow. The `event.duration` value is then computed as the difference between end and start times.
event.start
andevent.end
are date fields that demarcate the beginning and end, respectively,of an activity. For example in a network flow the event.start is the time of the first packet in the
flow and
event.end
time the time of the last observed packet in the flow.The
event.duration
value is then computed as the difference between end and start times.