feat(filter): Callstack filter fields #234
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.
To leverage callstack enrichment, a plethora of new filter fields are implemented. They allow accessing specific callstack attributes such as symbols, modules, or private allocation sizes. In addition to simple filter fields, a callstack map field permits fine-grained access to callstack frames, either by frame index, keywords, or module name. It is worth mentioning callsite filter fields which yield the assembly instructions for the leading/trailing callsite bytes.