feat: add event-counting filtering layer for spans #228
+245
−1
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.
Motivation
Applications can generate a large amount of logs which may be handled independently from tracing span events.
Simply filtering with a per-layer-filter will however lose the information that there may be more data regarding the spans elsewhere in the system.
Solution
Add a layer that filters out events but keeps a running count of them. This can then be used when viewing a trace to identify which spans have more contextual information in other systems.