Presentation type mapping #4472
Draft
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
1. Reduce the type variance in data fields via hardcoding possible types decodable from the kernel. 2. Move data field decode types to the types/trace package 3. Make corresponding changes in eBPF and test code
Move some functions around, rename and improve documentation.
(Almost) all event data type field names (post-decode) should now conform to go type names. This will ensure a more consistent and simpler format for event data.
Decode types are now explicitly distinguished from data presentation types. The boundary is set by a translation process, at this point internal to the decoder, which maps the decode strategy to the set presentation type given at the event definiton. Each decode type is mapped to a default presentation type, which is mapped by the identity function.
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.
Continuing #4353