Output whether events were lost in json - #106
Merged
Merged
Conversation
ngorogiannis
force-pushed
the
json-lost-events
branch
6 times, most recently
from
July 28, 2026 16:02
4b1f9f9 to
df8d17f
Compare
Currently this only reports whether events were lost
ngorogiannis
force-pushed
the
json-lost-events
branch
from
July 29, 2026 16:15
df8d17f to
6984375
Compare
ngorogiannis
marked this pull request as ready for review
July 30, 2026 08:17
tmcgilchrist
approved these changes
Jul 30, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add a boolean field in the json output called
stats-reliable. This currently simply records whether events were lost.