types: add event metadata #2752
Merged
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.
1. Explain what the PR does
This PR adds support to Metadata to
trace.Event
. At first this will be used to addSignatureMetadata
when a signature event is created from a detection. Instead of addingSignatureMetadata
directly, we have a more generic approach allowing for future use by events that are not signatures (eg: derivations, ebpf)The
Metadata
field is a pointer and marked asomitempty
so we only print it if there are metadata.This PR is part of #2355
2. Explain how to test it
Test the PR using this change to add signature metadata to signature events #2753
3. Other comments
The first implementation was using a more dynamic approach, but after discussion we decide to have a structure for the specific fields
Version
,Description
,Tags
,Properties
. This is based onSignatureMetadata
, but different because we don't need name, nor id, as events already have name and id of themselves.