Getting Data In

Datamodels with Smartstore

7aurelius
Loves-to-Learn

I have an environment where I'm using a datamodel with the _internal index. My datamodel_summary is created in the path where my _internaldb is. Here is my index definition:

 

 

 

[_internal]
homePath   = /opt/splunk/var/lib/splunk/_internaldb/db
coldPath   = /opt/splunk/var/lib/splunk/_internaldb/colddb
thawedPath = /opt/splunk/var/lib/splunk/_internaldb/thaweddb
tstatsHomePath = /opt/splunk/var/lib/splunk/_internaldb/datamodel_summary

 

 

The documentation suggests that the tstatshomepath value cannot be used with smartstore. How do I define a datamodel with Smartstore otherwise?

Labels (2)
0 Karma

nickhills
Ultra Champion

I think the wording is a little confusing, but "tstatsHomePath" allows you to dictate where this data is stored if you wanted to separate it from the rest of your index data, but importantly you do not have to specify a "tstatsHomePath"!

The wording in the spec file says that you should not configure this value for an index with remote storage, so this just means for a Smartstore index do not define "tstatsHomePath"  - the cachemanager will handle this for you.

 

 

If my comment helps, please give it a thumbs up!

7aurelius
Loves-to-Learn

@nickhills  so how would I define the internal _index above in smartstore with a datamodel?

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 ...