Datamodel autoextractSearch

[hank72]

Hi community,

When using datamodels, is it possible to remove/exclude the portion of the autoextractSearch: | search (index=* OR index=_*) 

[jonxilinx]

I have an issue with this (index=* OR index=_*) being added to  the Datamodel autoextractSearch
It breaks the macro when it references a federated index as "*" does not match to a federated index (in nontransparent mode)
(index=* OR index=_*)  AND (index=federated:Indexname)   fails to run
while (index=federated:Indexname)    as a constraint works fine

is there any way to make the constraint only be driven by the macro OR enable a way of defining the  autoextractSearch to be true ?

Many thanks , this would be ever so helpful in building datamodel on enterprise  search heads based on restricted constraints in the splunk cloud 

[gcusello]

Hi @jonxilinx ,

don't attach a new question to another one, open a new one to have more choices to have an answer.

Anyway, open a case to Splunk Support.

Ciao.

Giuseppe

[jonxilinx]

thanks , its effectively the same question though , how to remove the preamble from the autoextractSearch

And since this question did not get an answer , thought it better to post

Regardless, I opened up a support ticket yesterday (Case 3893384) with Splunk ,
and if I get a solution , will post reply as an answer

Many many thanks for the reply 

[gcusello]

Hi @hank72,

sorry but what's the issue?

in this way, you're sure that all the indexes are used to populate Data Models even if they aren't in the the default search path.

Anyway, if you want to limit the indexes used in one or all Data Models (I don't understand why!), you can modify the macro used in the contrains of each Data Model.

Ciao.

Giuseppe

[hank72]

@gcusello, Thank you for your response.  No issue "yet", just trying to think this through. 

If Workload Management's Admission Rules are set to not allow index=*, will this break any/all DMs that use the autoextractSearch (index=* OR index=_*) 

[gcusello]

Hi @hank72.,

As I said, in this way your are sure to load into the Data Models all the data from al indexes even if they aren't in the default search path.

If you want, youculd limit the indexes to read for each Data model, but there's no reason to do this, so my hint is to leave it as it is.

let us know if we can help you more, or, please, accept one answer for the other people of Community.

Ciao and happy splunking

Giuseppe

P.S.: Karma Points are appreciated by all the contributors 😉