-
Notifications
You must be signed in to change notification settings - Fork 415
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
[RFC] Stge 0 - New fieldset for volume device #2201
Conversation
* volume.mount_name | ||
* volume.device_name | ||
* volume.dos_name | ||
* volume.nt_name |
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.
above 2 fields are Windows specific
This RFC propose adding the volume device fieldset to describe volume storage devices that are removable disks such as USB, mountable virtual disks such as ISO. | ||
|
||
* volume.mount_name | ||
* volume.device_name |
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.
above 2 fields are posix specific
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.
Thanks for the proposal, @Trinity2019.
The motivation of describing alerts and event associated with volumes makes sense as an addition to ECS.
* volume.vendor_name | ||
* volume.serial_number | ||
* volume.volume_device_type | ||
* volume.action |
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.
volume.action
will be like "attach", "detach", "mount", "unmount". I'm hesitating to place it here. Seems event.action
is a better place to save such information. Because these volumes fields will be part of a device event, similar to process events whose event.action
can be "start"/"end".
thoughts?
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'd also prefer to use the existing event.action
field over introducing an additional *.action
field, if we can avoid it.
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.
Should anyone else give another review before we merge this RFC as stage 0?
I reviewed this as well, I think we can go ahead with merging |
make test
? - N/Amake
and committed those changes? - N/A