Splunk Search

Datamodel autoextractSearch

hank72
Path Finder

Hi community,

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

Labels (1)
Tags (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

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
Path Finder

@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=_*) 

0 Karma

gcusello
SplunkTrust
SplunkTrust

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 😉

0 Karma
Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

New This Month - Observability Updates Give Extended Visibility and Improve User ...

This month is a collection of special news! From Magic Quadrant updates to AppDynamics integrations to ...

Intro to Splunk Synthetic Monitoring

In our last post, we mentioned that the 3 key pieces of observability – metrics, logs, and traces – provide ...