Getting Data In

Eval recently collected events between indexes

strangelaw
Explorer

Here is the thing:

I have 2 indexes: index_original and index_collected.

The plan is to compare/evaluate index_original events within selected timespan (say last 2 minutes) with index_collected events to see if there's any NEW EVENTS (e.g. not aleady collected to index_collected, that is) on index_original. I do not want to make one2one copy, but I want to compare with event (_time) or other unique identifier on that index if there's event available to be collected.

The target is that I have only fresh, newly collected events on index_collected - not whole stack again and then doing filtering/dedupping. Goal is to reduce index data amounts per each collection.

I have some other searches/table lookups to be done within same query, but this is the primary selector.

Any idea? Would be great help!

0 Karma
1 Solution

sundareshr
Legend

Will this work?

index=original OR index=collected | timechart list(_raw) as _raw by index | mvexpand _raw | where isnull(original) OR isnull(collected)

View solution in original post

0 Karma

sundareshr
Legend

Will this work?

index=original OR index=collected | timechart list(_raw) as _raw by index | mvexpand _raw | where isnull(original) OR isnull(collected)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...