Splunk Search

How to join 2 datamodels searches with different timeranges

fernandopaixao
New Member

Hi everyone,

I need to join two different searches using different time ranges in the alert search.
Normally the earliest parameter would solve it but the following syntax doesn't work

| datamodel dm-evaluation evaluation search earliest=@d

Do you know how to solve it?

Thank you

Tags (1)
0 Karma

woodcock
Esteemed Legend

Fist of all, I wouldn't use | datamodel because it was recently broken and no longer returns all fields (only the ones in the datamodel). Instead use the macro described here (it will need adjustment because it is hard-coded for CIM):

https://answers.splunk.com/answers/716936/splunk-server-field-is-not-available-when-we-searc.html#an...

Then you can use as many time specifier clauses as you can like this:

`SIEMMacro_datamodel(dm-evaluation, dm-evaluation)` evaluation search ((earliest=e1 latest=l1) OR (earliest=e2 latest=l2) OR ... OR (earliest=eZ latest=lZ))
0 Karma

to4kawa
Ultra Champion

How long are the two search periods?
There is the way that

Time range can be covered two data models,
Search by `summariesonly = t` and `timechart` ,
Create flag (e.g. datamodelA or datamodelB)  ,
Combine the two search results by `append`, 
Select time and data model(flag) by `where`

How about this?

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...