If so, is there a proper way to get around that? Possibly get data as they come in?
If I run a real-time-search for a minute on the Splunk server(localhost) while running the same search using the SDK, I seem to get 30 results in the server while there is almost an infinite number of results being printed in the SDK.
I do not know if it might help my case, but I am using the eventgen app to regulate event generation.
... View more
My task is to create a real-time search, ideally to run 24/7. Now the problem arises when I close my program(not necessarily the search) and maybe start it again after a day and I need all the data I missed in the last 24 hours. There is the option of just running a normal search and get the data that I have missed, but that is the last resort. As a result, I have been trying to get that done and then get realtime events in one search; it should return the missed events and then should just resume like an all-time realtime search. I have tried setting the earliest time to 'rt-1d' but what this does is generate the results over the last 24 hours (multiple times if it falls within that window). It also shows the new events that come in(which will be in the window), but I need a way (if there is one) to get rid of the duplicate results.
Event A - Captured in real time search
Event C-Will be captured
Run Normal Search to get B
Run Real time search to get C and beyond
What I need:
(Real Time) Search to get B and then C and beyond
What I have:
A search that has the potential to return duplicates (because of a very big time window) like
Event C- After it has been indexed
Event C - duplicates from here on
Event D-After being indexed, soon to be duplicated and so on.
... View more