Repository navigation
splunk: fix pagination query that caused certain events to be skipped. - #114
Merged
xvaier merged 1 commit intoOct 21, 2026
Conversation
ankushy-metron
approved these changes
Oct 21, 2026
ankushy-metron
left a comment
ankushy-metron
left a comment
Collaborator
There was a problem hiding this comment.
We tested it, and it worked; we will now replicate this across all other integrations.
xvaier
deleted the
xavierlavallee/dd-1207-investigate-splunk-and-flare-event-count-mismatch
branch
October 21, 2026 12:47
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
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.
I realized while debugging a separate issue, that by filtering by
estimated_created_atand scrolling bymatched_at(the default value) in descending order, then setting theestimated_created_atto the start of the previous run while starting the next run would miss any newly matched events that were in the past.This can be triggered when we backfill new identifiers or when an event that happed a couple of hours ago was not crawled in real time.